-
Notifications
You must be signed in to change notification settings - Fork 33
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
Consider breaking out build/test summaries #290
Comments
@mrbazzan, would you be interested in taking this one on? |
Yes. I'll get right on it. |
Hi @spbnick, |
No problem, Abdulwasiu! I'm still struggling with post-COVID symptoms and only have energy for pushing work on known issues/incidents for now. Sorry for being quiet. Good luck with the exams! |
Hello Nick,
Thanks. It was quite an exam.
I hope you are all better now? I started working on this issue again. I pushed an update to #320. Please check when you can |
Hi Abdulwasiu! Feeling generally better, but might be having less immunity against everything as a COVID consequence. Have been having all kinds of smaller colds this autumn/winter. Sorry for another slow response, the pre-Christmas period was tough (as usual), and then I was away for two weeks for the holidays. Back now and looking at your updated PR! |
Sorry about that :(. Perhaps the cold is because of the weather?
Nice! |
At the beginning of each notification we have a summary of checkout/build/test status. E.g.:
Later in the message we break those down by status. E.g.:
and
However, since we have so many failures, a lot of which are false positives, we should consider duplicating the breakout at the introductory overview as well. I.e.:
This would let the readers get a feeling for the results faster.
Suggested by @broonie.
The text was updated successfully, but these errors were encountered: