-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Add debugging print to check aarch64 repl test #46931
Conversation
|
|
The first call to note how old this folder was when last modified (1 minute), last accessed (14 s), and how many hard links it has (probably folders inside) |
So for some reason |
What were you trying to test in the last commit @vtjnash ? |
I am trying to isolate which lines are important and which don't change the result |
|
Yeah, the expansion of |
@@ -150,1440 +98,21 @@ fake_repl(options = REPL.Options(confirm_exit=false,hascolor=true)) do stdin_wri | |||
readuntil(stdout_read, tmpdir_pwd) | |||
readuntil(stdout_read, "\n") | |||
readuntil(stdout_read, "\n") |
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.
A little part of me wonders if the path on aarch64 is just a little bit too long, and causes tmpdir_pwd to be printed several times here. e.g. the same as #44972. The order of these reads is a bit nonsensical. Thus the actual cd
might not have happened yet, until the added @show
cause a context switch.
(you can prove this theory by checking when get(ENV, "OLDPWD", "")
gets set here)
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, it's as you expected. A context switch is what triggers it to change. Not sure what the fix for this is. The paths don't look too too long
76efc33
to
fd7615c
Compare
Fixed by #47160 |
No description provided.