-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable stable-rt
email report
#565
Conversation
c4b268a
to
81e78da
Compare
81e78da
to
2aaf2f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good start, thank you. However, could you please rename common.j2
to stable.j2
. It's only "common" to stable templates, not to everything.
Ah, I see you're using it for "fluster" reports too. Could you name it |
I wanted to use it for codec summary report as well. That's why I named it |
We are taking into account results from |
Here is the sample
Cc: @helen-fornazier |
@JenySadadia the sample is looking good to me, thanks! |
5510a1b
to
16df8cf
Compare
As per suggestion from @spbnick , created common templates for |
Here is the updated sample report with test links:
|
Add templates for generating `stable-rt` report. Signed-off-by: Jeny Sadadia <[email protected]>
Add a subscription script for generating notifications for Linux `stable-rt` tree. Signed-off-by: Jeny Sadadia <[email protected]>
Use common templates such as `stable_build.j2`, `stable_revision.j2`, `stable_revision_summary.j2`, and `common.j2` to avoid duplication in `stable-rc` and `stable-rt` report templates. Signed-off-by: Jeny Sadadia <[email protected]>
16df8cf
to
c403609
Compare
The template looks good to me! Thanks! |
@spbnick Can we merge this? |
Sure! |
For starters,
stable-rt
email reports will list down build, boot, and rt-tests failures.