-
-
Notifications
You must be signed in to change notification settings - Fork 32k
gh-113440: Windows CI: Raise exception with stderr if ver
call fails
#113392
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
Conversation
Ah interesting: I ran this about 25 times on my fork, they passed every time. First time with this PR it failed :) Running Debug|Win32 interpreter...
ERROR: collect_windows() failed
Traceback (most recent call last):
File "D:\a\cpython\cpython\Lib\test\pythoninfo.py", line 1025, in collect_info
collect_func(info_add)
~~~~~~~~~~~~^^^^^^^^^^
File "D:\a\cpython\cpython\Lib\test\pythoninfo.py", line 929, in collect_windows
raise ValueError(
...<2 lines>...
)
ValueError: Command 'ver' failed with exit code 3221225794: stdout='' stderr='' https://github.com/python/cpython/actions/runs/7298627675/job/19889972821?pr=113392#step:4:17
|
Co-authored-by: Steve Dower <steve.dower@microsoft.com>
Looks like it's actually a problem with PATH then. I don't have a problem with leaving that |
Would you like to suggest a comment? |
|
Looks like it's gotten stuck this time, which is very interesting. Perhaps the previous run was on the successful side of the 50/50? |
I ran about 20 times on my fork, but it passed each time. I'll restart it. But getting stuck is worse than stopping with an error... |
I won't restart it as it's already been restarted twice.
ERROR: collect_windows() failed
Traceback (most recent call last):
File "D:\a\cpython\cpython\Lib\test\pythoninfo.py", line 1027, in collect_info
collect_func(info_add)
~~~~~~~~~~~~^^^^^^^^^^
File "D:\a\cpython\cpython\Lib\test\pythoninfo.py", line 931, in collect_windows
raise ValueError(
...<2 lines>...
)
ValueError: Command 'ver' failed with exit code 3221225794: stdout='' stderr='' |
Okay, guess we can assume that PATH isn't the culprit (and revert that change). I've been able to find some (private) discussion about a possible issue that looks like this. It suggests that Currently it's A simpler fix might be to pass |
I compared successful and failing logs, and they are identical to this point, ignoring time, commit hash, git pull progress indicator and the order of compiling files. |
Is there an open issue? I'm trying to ignore this error, if it can help, because it blocks our work. See #113435. |
I don't think there's an issue. Your PR looks good to unblock, perhaps combine with this to log the error rather than raising an exception? |
@hugovk Then could you please open an issue and copy your description to it? We will link both PRs to this issue, unblock the workflow, and then continue investigation of the problem. |
Certainly, I've opened issue #113440. |
ver
call failsver
call fails
Do we still need this or can we close it (and #113440)? |
Do you still need this? The |
Fixes gh-113440.
We've had build failures on "Windows / build and test (x86)", after some unknown problem calling the
ver
command.For example:
https://github.com/python/cpython/actions/runs/7286334537/job/19854864684
More examples:
Sometimes it fails on re-run, sometimes it passes.
Let's output the exit code and error message when it happens, and fail fast, to help debug.
ver
command #113440