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
The healthcheck Dev job failed due to an un-handled network error requests.exceptions.ConnectionError which prevented the blocks json file from being created
this lead the next step to fail before sending the slack message
the completed job ran correctly, but it had malformed data so sent a weird looking slack notification
What did you expect to happen?
In this case we would expect the network error to be caught and handled, or that the completed job could run from a missing json file it seems to be sending incorrect data, maybe from running on a fork?
What happened?
The workflow was run from the "schedule" event, but linked to a bunch of obscure Pull requests in different repositories https://api.github.com/repos/mozilla/addons-server/actions/runs/13907783652
requests.exceptions.ConnectionError
which prevented the blocks json file from being createdWhat did you expect to happen?
In this case we would expect the network error to be caught and handled, or that the completed job could run from a missing json file it seems to be sending incorrect data, maybe from running on a fork?
Is there an existing issue for this?
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: