Repository navigation
ci: the simulator's e2e suite runs nightly and on PRs that change the simulator - #276
Merged
Merged
Conversation
…and takes the chat line from any of the lineup's players; a failed run keeps every container's log
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs every scenario in
apps/simulator/e2eagainst the api's published image, nightly, by hand, and on PRs that touch the simulator or the shared entities. Run only by hand, the no-show tournament scenario broke unnoticed from Oct 14 until #275. A failed run prints the failing scenarios' logs and keeps every container's whole log as an artifact.Its first CI runs also fixed two scenarios that only failed on the slower runner: ready-admin waited for a server's "waiting for force_ready" line that an earlier no-show scenario had already logged (it now looks only at lines since its match started), and chat expected the line from the lineup's first player, but the roster the api sends has no set order (any of the lineup's players now counts). All 23 pass. resume timed out once (996 s) and passed on the next run; the kept logs will say why if it happens again.