-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Fix next prompt detector in generate_precompile_statements
#44196
Fix next prompt detector in generate_precompile_statements
#44196
Conversation
Judging by the previous commit it seems precompile statements were being missed off.. On the MacOS buildbot Previous commit:
This PR:
|
Nice |
occursin(PKG_PROMPT, strbuf) && break | ||
occursin(SHELL_PROMPT, strbuf) && break | ||
occursin(HELP_PROMPT, strbuf) && break | ||
sleep(0.1) |
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.
Why is this sleep
needed?
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.
Oh, I assume that readavailable
blocks on no data but that might not be the case?
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.
Maybe it isn't, I didn't test it without. I just thought spinning without wait if the terminal is stalling output wasn't necessary
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.
Maybe we need a readuntil
function that takes a regex
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.
yeah, I looked for that while doing this
(cherry picked from commit c839221)
(cherry picked from commit c839221)
(cherry picked from commit c839221)
(cherry picked from commit c839221)
In
generate_precompile_statements
it turns out the repeatedly overprinted>
chars from thePkg.precompile
progress bar were being interpreted as the next prompts.. making the precompile statement generator process race to the end and crashing the end of the process. I'm not sure whether that means the scripts afterwards failed to get precompile statements generated.This was confirmed by setting
debug_output = stdout