Repository navigation
ci(bench): erd_open_200 diagnoses itself; an aborted bench run fails the job (#1546) - #1714
Merged
Merged
Conversation
…ls the job and says why (#1546)
github-actions
Bot
added
bug
… is outside the window with seven tabs (#1546)
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.
Refs #1546
The
erd_open_200scenario timed out waiting for a diagram of 200 tables and the bench still exited 0, so everything after it went unchecked.session.error, status line printed asBENCH erd_ddl), waits for the Diagram tab first and then for the cards, and on a timeout printsBENCH erd_state(active tab, whether it is the diagram, number oferd_table_*cards). This tells the two causes in the issue apart (script did not create the tables vs. the diagram never opened).BENCH FAILED: ...and the app exits 1.flutter runreports 0 whatever the app does, so theapp-benchjob has a step that fails on that line;app_bench_report.pynames the reason in the summary (tests added). The job stayscontinue-on-error.The cause of the original timeout is not fixed here: the benchmark workflow on this PR runs the scenario and shows which of the two it is. The issue stays open until
erd_open_200prints numbers.