This is causing failures for forks which have already been migrated, for example:
======================================================================
FAIL: test_function_entry_return (test.test_dtrace.DTraceNormalTests.test_function_entry_return)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\a\cpython\cpython\Lib\test\test_dtrace.py", line 38, in normalize_trace_output
result.sort(key=lambda row: int(row[0]))
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\a\cpython\cpython\Lib\test\test_dtrace.py", line 38, in <lambda>
result.sort(key=lambda row: int(row[0]))
~~~^^^^^^^^
ValueError: invalid literal for int() with base 10: 'dtrace: failed to compile script D:\\a\\cpython\\cpython\\Lib\\test\\dtracedata\\call_stack.d: line 3: pid provider is not installed on this system'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\a\cpython\cpython\Lib\test\test_dtrace.py", line 124, in test_function_entry_return
self.run_case("call_stack")
~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "D:\a\cpython\cpython\Lib\test\test_dtrace.py", line 119, in run_case
actual_output, expected_output = self.backend.run_case(
~~~~~~~~~~~~~~~~~~~~~^
name, optimize_python=self.optimize_python)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\a\cpython\cpython\Lib\test\test_dtrace.py", line 53, in run_case
actual_output = normalize_trace_output(self.trace_python(
script_file=abspath(name + self.EXTENSION),
python_file=abspath(name + ".py"),
optimize_python=optimize_python))
File "D:\a\cpython\cpython\Lib\test\test_dtrace.py", line 42, in normalize_trace_output
raise AssertionError(
"tracer produced unparsable output:\n{}".format(output)
)
AssertionError: tracer produced unparsable output:
dtrace: failed to compile script D:\a\cpython\cpython\Lib\test\dtracedata\call_stack.d: line 3: pid provider is not installed on this system
Bug report
Bug description:
GitHub Actions is in the process of migrating
windows-latestfromwindows-2022towindows-2025:actions/runner-images#12677
This is causing failures for forks which have already been migrated, for example:
https://github.com/picnixz/cpython/actions/runs/17610564159/job/50031376950#step:1:9
Upstream and my fork are still on 2022, but let's pin to
windows-2022so we can separately investigate and fix for 2025, and then pin towindows-2025.(Copied verbatim from #138743)
Linked PRs
windows-2022#138743windows-2022(GH-138743) #138752windows-2022(GH-138743) #138753windows-2022(GH-138743) #138754windows-2022(GH-138743) #138755windows-2022(GH-138743) #138757windows-2022(GH-138743) #138758