Skip to content
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

Make GitHub notify when an eval error has occoured? #652

Open
doronbehar opened this issue Sep 20, 2023 · 5 comments
Open

Make GitHub notify when an eval error has occoured? #652

doronbehar opened this issue Sep 20, 2023 · 5 comments

Comments

@doronbehar
Copy link
Contributor

doronbehar commented Sep 20, 2023

Rather often, when you rename a package attribute or alike, another package you were not aware of has used the attribute name you deleted, and you forgot to change it accordingly.

It'd be nice if ofborg had sent via GitHub an email notifying of the eval failure - just like the EditorConfig job for example. This is helpful in slow evaluation which happen in e.g treewide: like PRs.

@pbsds
Copy link
Member

pbsds commented Dec 20, 2023

You do get a red X in the https://github.com/pulls view when CI fails. Sending messages every time eval fails would cause a storm everytime master fails eval.

@doronbehar
Copy link
Contributor Author

You do get a red X in the github.com/pulls view when CI fails. Sending messages every time eval fails would cause a storm everytime master fails eval.

Correct, but I don't think it is bad. Eval errors on master happen rarely, and when they do, I think it wouldn't hurt to notify many people about it, as it is a severe mistake. Also, even if the error is not due to merges you personally performed, it will also give you the hint to comment @ofborg eval to retrigger evaluation after the eval error is fixed.

@pbsds
Copy link
Member

pbsds commented Dec 20, 2023

Doesn't this work?
image

@doronbehar
Copy link
Contributor Author

@pbsds this seems worth checking, but I don't understand how did you get to that interface? I also wonder, why is EditorConfig's workflow notifying me upon emails and ofborg doesn't? The interface you screenshot doesn't look like it has different settings for the above 2 workflows...

@pbsds
Copy link
Member

pbsds commented Dec 22, 2023

It may be because the editor config checks run in a github action runner, while the ofborg CI checkmarks are set using some other API by the ofborg runners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants