Closed JoeyBF closed 5 months ago
As an example, here's a snippet from the nightly test of the latest CI run for this PR (ext test #602):
Finished dev [unoptimized + debuginfo] target(s) in 0.05s
Running `target/debug/examples/yoneda 'S_2@adem' '' 30 6 '[1]'`
Module (default: S_2): S_2@adem
Module save directory (optional):
n of Ext class: 30
s of Ext class: 6
Input Ext class: [1]
Timeout occurred, but treating as success.
Any updates on this one? It's a bit tedious babying the CI runs and making sure nothing hangs
No problem at all! I hope things are going well for you 🙂
It's a bit of an ugly fix, but it makes sure that we don't waste hours of CI for no reason. Assuming that at least one of {stable, beta, nightly} doesn't deadlock, I feel it's acceptable to treat timeouts as successes. It technically fixes #142, but I look forward to resolving the underlying issue and being able to remove the timeouts.