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
I've observed this a number of times; when a test is flaky and the PR is closed and re-opened to re-trigger CI, azure-pipelines tests are restarted (and so were travis and circle back in the days IIRC), but not builds.sr.ht: freebsd.yml (at least a lot of times it doesn't), so you end up with wasted CI cycles because the test still fails
Example
in #13546 (same problem with other recent PR's I've just restarted after the feb 29 bug, eg #13537)
[#160965] 2020/02/29 22:25:38 Booting image freebsd/latest (default) on port 22021
[#160965] 2020/02/29 22:25:41 Waiting for guest to settle
[#160965] 2020/02/29 22:26:02 Sending tasks
Expected Output
freebsd test restarts
workaround
do a dummy edit and force-push (not great)
The text was updated successfully, but these errors were encountered:
timotheecour
changed the title
builds.sr.ht: freebsd.yml does not restart when a PR is closed/re-opened
[CI] builds.sr.ht: freebsd.yml does not restart when a PR is closed/re-opened
Mar 1, 2020
This is not something we can solve. You can open a ticket on sr.ht (dispatch.sr.ht handles github integration). But from their docs this is expected, as builds gets triggered on a push to a branch.
I've observed this a number of times; when a test is flaky and the PR is closed and re-opened to re-trigger CI, azure-pipelines tests are restarted (and so were travis and circle back in the days IIRC), but not
builds.sr.ht: freebsd.yml
(at least a lot of times it doesn't), so you end up with wasted CI cycles because the test still failsExample
in #13546 (same problem with other recent PR's I've just restarted after the feb 29 bug, eg #13537)
Current Output
also, 1st few lines of https://builds.sr.ht/~araq/job/160965#task-test show the test wasn't restarted and was from yesterday:
Expected Output
freebsd test restarts
workaround
do a dummy edit and force-push (not great)
The text was updated successfully, but these errors were encountered: