Repository navigation
Nightly tests / release workflows failing on forks #1061
Description
I have been getting emails about CI failure from the autorelease tool every day since I forked this repository. I think I finally figured out that it was because my fork's stable branch wasn't up to date, but I'm still not sure (I tried updating the tags on my fork earlier, but that didn't fix it). Regardless of the cause, I would advocate for the nightly CI checks to be skipped on all forks except openpathsampling/openpathsampling in the interest of conserving energy (the Python 2.7 tests take about 90 minutes from what I can tell) and reducing notification noise.
Example failure: https://github.com/bdice/openpathsampling/runs/3448877047?check_suite_focus=true
I'm going to open a PR that I hope will address the problem.
Activity
bdice commentedon Aug 28, 2021
This also affects releases -- I pushed to the
stablebranch of my fork in order to stop the nightly tests from failing. In the nightly tests, autorelease saw that mystablebranch pointed to 1.3.0 and was out of date with the current 1.5.2 release. But after pushing tostable, that triggered a workflow for releases, which I also did not want. CI logs here: https://github.com/bdice/openpathsampling/actions/runs/1177536916This is also addressed in PR #1062.
[-]Nightly tests failing on forks[/-][+]Nightly tests / release workflows failing on forks[/+]