You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the workflow fails, the failure is posted in the aiida-core-dev Slack channel.
There are several issues with this:
The Slack channel is not public and easy to miss (as we discussed with @GeigerJ2 during coding week, people were generally not aware of it).
It's hard to track, discuss and resolve the failures in a consistent manner.
Instead of posting to a Slack channel, I would propose that failing workflow would automatically create Github issue. That might be noisy at fist, but it would force us to deal with the issues transparently.
We're running nightly tests periodically once per day:
aiida-core/.github/workflows/nightly.yml
Line 5 in 0eb77b8
When the workflow fails, the failure is posted in the
aiida-core-dev
Slack channel.There are several issues with this:
Instead of posting to a Slack channel, I would propose that failing workflow would automatically create Github issue. That might be noisy at fist, but it would force us to deal with the issues transparently.
The implementation of this is actually quite simple, I took this idea from the ruff repository:
https://github.com/astral-sh/ruff/blob/d0b2bbd55ee6435bc3dad8db2898aec216d85121/.github/workflows/daily_fuzz.yaml#L60
CC @unkcpz @agoscinski
The text was updated successfully, but these errors were encountered: