Let retry.py flush stdout after each log message#19754
Conversation
|
https://github.com/web-platform-tests/wpt/pull/19750/checks?check_run_id=263749188 shows the order being wrong before this change. |
|
In https://github.com/web-platform-tests/wpt/pull/19754/checks?check_run_id=263770797 the order is correct. |
1bf622e to
8ab5b37
Compare
|
@jgraham should I update the docker image too? |
|
Yes. |
|
@jgraham done! |
9a45e85 to
3cb58e9
Compare
|
I've triggered full Chrome and Firefox runs to check that the new docker image doesn't break everything: |
|
Ping @jgraham |
This is to avoid the subprocess output appearing before the "Running %s [try %d/%d]" message.
|
@stephenmcgruer @Hexcles I'd like to get this landed and I see you updated the image in #23190. Can either of you help generate and upload the new image that would make this PR work? https://github.com/web-platform-tests/wpt/runs/637380261#step:4:1001 shows how this is still a problem, makes it hard to see what happened in which try. |
Absolutely :). I have checked out this PR, built |
|
Also, ahem, thanks @stephenmcgruer for updating the image for me!! |
This is to avoid the subprocess output appearing before the
"Running %s [try %d/%d]" message.