-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed test failure. #3522
Fixed test failure. #3522
Conversation
ff69c6e
to
49ca52a
Compare
The solver is getting faster!
49ca52a
to
bcd3f82
Compare
cp.Expect("Resolving Dependencies") | ||
cp.ExpectRe(`[^.]+?✔ Done`, e2e.RuntimeSolvingTimeoutOpt) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This first checkout seems to specifically be about asserting that it does NOT use dot progress, but these changes seem to make it so that it is asserting that it DOES use dot progress.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is expecting that there are no dots between "Resolving Dependencies" and "✔ Done", so it's asserting that it does NOT use dot progress.
I had to do a few iterations of this test, and during these iterations I found that cp.Output()
gave me all the escape sequences of the \, |, and / interactive progress between "Resolving Dependencies" and "✔ Done". I am confident this test is working as intended.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh.. the way the regex is written I had assumed it was checking for ... ✔ Done
. I had interpreted the dot as a literal dot rather than a regex rule. Might be worth adding a comment for clarity.
The solver is getting faster!