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 notice that the macos tests often (say >20% for sure) time out after 40 minutes. This is highly annoying.
Maybe allow them to fail?
For gitlab we have a https://github.com/testmoapp/junitxml based test reporting to the server, where we can analyse failed tests and see there individual execution time. I would assume that this will not generate results in a time out, but maybe one could gain some simpler insight from non-failed runs into bottlenecks?
The text was updated successfully, but these errors were encountered:
I notice that the macos tests often (say >20% for sure) time out after 40 minutes. This is highly annoying.
Maybe allow them to fail?
For gitlab we have a https://github.com/testmoapp/junitxml based test reporting to the server, where we can analyse failed tests and see there individual execution time. I would assume that this will not generate results in a time out, but maybe one could gain some simpler insight from non-failed runs into bottlenecks?
The text was updated successfully, but these errors were encountered: