Skip to content

Conversation

apostasie
Copy link
Contributor

A lot of work has improved stability since I last tried this.
Though we still have some flaky tests in the "non-retry" bucket, we need more info at this point on the state of the "retry" bucket that is likely hiding more issues.

This is a debugging PR at this point, not meant to be merged.

@apostasie
Copy link
Contributor Author

Ok... this is not a pleasing sight...

@apostasie
Copy link
Contributor Author

@apostasie
Copy link
Contributor Author

Second run brings:

@apostasie apostasie closed this Apr 20, 2025
@apostasie apostasie reopened this Apr 20, 2025
@apostasie
Copy link
Contributor Author

apostasie commented Apr 20, 2025

Third run brings:

@apostasie apostasie closed this Apr 20, 2025
@apostasie apostasie reopened this Apr 20, 2025
@apostasie apostasie closed this Apr 21, 2025
@apostasie apostasie reopened this Apr 21, 2025
@apostasie
Copy link
Contributor Author

Pausing this for now.
There is no point in poking this more - we have enough issues to fix from the first few runs...

@apostasie apostasie closed this Apr 21, 2025
@apostasie apostasie changed the title [DEBUGGING]: evaluate what happens if we disable gotestsum retries [CI]: blank PR disabling test retries May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant