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
Kicking the can on this, I can't currently figure this out.
These two bioconda integration tests seem to cause the GitHub runner to lock-up with a yellow spinning wheel. The tests are marked as failed, without completing the post-run stages. The timeout checks for rattler-build don't seem to trigger.
This seems to have been unintentionally fixed in #26. I have a few baseless theories:
GitHub had an issue on its end with the CI runner
There was a change in rattler-build
Moving the integration test data into another repo that we sparsely pull from meant there were more resources freed on the runner(?). It looks like the runners get 25gb by default and the test data was only about 10mb so this theory seems a little far-fetched.
Kicking the can on this, I can't currently figure this out.
These two bioconda integration tests seem to cause the GitHub runner to lock-up with a yellow spinning wheel. The tests are marked as failed, without completing the post-run stages. The timeout checks for rattler-build don't seem to trigger.
Here is an example run:
https://github.com/conda-incubator/conda-recipe-manager/actions/runs/8482951360/job/23243473204?pr=15
Work on these unit tests is still on-going in #15
These tests appear to work fine on my Mac locally.
The text was updated successfully, but these errors were encountered: