Skip to content

test_dtrace fails on Windows Server 2025 #138744

Closed
Closed
test_dtrace fails on Windows Server 2025#138744
Labels
OS-windowsinfraCI, GitHub Actions, buildbots, Dependabot, etc.testsTests in the Lib/test dirtype-bugAn unexpected behavior, bug, or error

Description

@picnixz
picnixz
opened on Sep 10, 2025

Bug report

Bug description:

GitHub Actions is in the process of migrating windows-latest from windows-2022 to windows-2025:

This change will be rolled out over a period of several weeks beginning 2025-09-02 and will complete on 2025-09-30

actions/runner-images#12677

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

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-2022 so we can separately investigate and fix for 2025, and then pin to windows-2025.

(Copied verbatim from #138743)

Linked PRs

Activity

  1. picnixz
    added
    type-bugAn unexpected behavior, bug, or error
    testsTests in the Lib/test dir
    OS-windows
    infraCI, GitHub Actions, buildbots, Dependabot, etc.
    on Sep 10, 2025
  2. hugovk
    added a commit that references this issue on Sep 10, 2025

    gh-138744: GitHub Actions: pin to `windows-2022` (#138743)

    6e78a53
  3. miss-islington
    added a commit that references this issue on Sep 10, 2025

    pythongh-138744: GitHub Actions: pin to `windows-2022` (pythonGH-138743)

    5123233
  4. hugovk
    added 6 commits that reference this issue on Sep 10, 2025

    [3.13] pythongh-138744: GitHub Actions: pin to `windows-2022` (python…

    d0f84ea

    [3.12] pythongh-138744: GitHub Actions: pin to `windows-2022` (python…

    7dad0d0

    [3.11] pythongh-138744: GitHub Actions: pin to `windows-2022` (python…

    a318138

    [3.10] pythongh-138744: GitHub Actions: pin to `windows-2022` (python…

    9aeb39d

    [3.9] pythongh-138744: GitHub Actions: pin to `windows-2022` (pythonG…

    d5134df

    [3.14] gh-138744: GitHub Actions: pin to `windows-2022` (GH-138743) (#…

    a963843

  5. vstinner commented on Sep 10, 2025

    @vstinner
    vstinner
    on Sep 10, 2025
    Member

    https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/dtrace

    Beginning with Windows Server 2025, dtrace is included as a built-in tool.

    Before, test_dtrace was skipped since the dtrace command was missing.

  6. hugovk
    added a commit that references this issue on Sep 10, 2025

    [3.13] gh-138744: GitHub Actions: pin to `windows-2022` (GH-138743) (#…

    443d4af
  7. ambv
    added a commit that references this issue on Sep 13, 2025

    [3.9] gh-138744: GitHub Actions: pin to `windows-2022` (GH-138743) (G…

    220e677

  8. 4 remaining items

  9. vstinner commented on Feb 10, 2026

    @vstinner
    vstinner
    on Feb 10, 2026
    Member

    Good idea, I wrote #144657 to skip test_dtrace on Windows in the 3.14 branch.

  10. vstinner
    added 2 commits that reference this issue on Feb 10, 2026

    pythongh-138744: Skip test_dtrace on Windows

    03fd199

    [3.14] gh-138744: Skip test_dtrace on Windows (#144657)

    8b4210c
  11. miss-islington
    added a commit that references this issue on Feb 10, 2026

    [3.14] pythongh-138744: Skip test_dtrace on Windows (pythonGH-144657)

    553bb20
  12. vstinner
    added 2 commits that reference this issue on Feb 10, 2026

    pythongh-138744: Upgrade Windows to 2025 in GitHub Actions

    9d53eaa

    [3.13] gh-138744: Skip test_dtrace on Windows (GH-144657) (#144668)

    36aa081

  13. chris-eibl commented on Feb 10, 2026

    @chris-eibl
    chris-eibl
    on Feb 10, 2026
    Member

    Thanks for doing this @vstinner. Having those tests pass skipped on Windows 2025 Servers is great.

    Regarding upgrading the GitHub Actions I have a question:
    Looking at https://github.com/python/release-tools/blob/main/windows-release/stage-build.yml, windows-2022 is taken to build the official release binaries. AFAIU @zooba, this should be kept for 3.13 and 3.14.
    But for 3.15 we'd like to parameterize it to be able to use windows-2025-vs2026 (until windows-2025 gets VS 2026 in May) to be able to build with tailcalling support for Windows. See also #144679.

    Shouldn't we use the same version to build in CI, that is stay on windows-2022 for the 3.13 and 3.14 branches?

  14. vstinner
    added a commit that references this issue on Feb 10, 2026

    pythongh-138744: Upgrade Windows to 2025 in GitHub Actions

    9881c60

  15. zooba commented on Feb 11, 2026

    @zooba
    zooba
    on Feb 11, 2026
    Member

    Realistically, the OS is going to have no impact on the produced binaries, so I'm not worried about that.

    Changing VS version implies different compilers being available, and different Windows SDK install being available. Generally, WinSDK updates are irrelevant (I'm only aware of one exception to this in the last ~decade), and MSVC updates are usually worth it. Nothing in the C ABI is going to change with a new compiler (the C++ ABI would, which is why we don't use it), but more importantly we may need to change the files that are distributed (e.g. the addition of vcruntime140_1.dll).

    If the test suites all pass on VS 2026, either because toolset v143 is available on all the machines or v145 doesn't cause any breakage, and no additional files need to be redistributed, then I see no harm in updating them all.

  16. vstinner
    added a commit that references this issue on Feb 12, 2026

    gh-138744: Upgrade Windows to 2025 in GitHub Actions (#144682)

    eb6ebdb
  17. thunder-coding
    added a commit that references this issue on Feb 15, 2026

    pythongh-138744: Upgrade Windows to 2025 in GitHub Actions (python#14…

    a0e280b

  18. vstinner commented on Feb 16, 2026

    @vstinner
    vstinner
    on Feb 16, 2026
    Member

    test_dtrace is now skipped on Windows in 3.13, 3.14 and main branches.

    The main branch now uses windows-2025 CI image in GitHub Action.

    The initial issue (test_dtrace fails on Windows Server 2025) has been fixed. I close the issue.

    Changing VS version implies different compilers being available, and different Windows SDK install being available.

    #144680 prepares Python 3.15 for Visual Studio 2026.

  19. vstinner
    closed this as completedon Feb 16, 2026
  20. brijkapadia
    added a commit that references this issue on Feb 28, 2026

    pythongh-138744: Upgrade Windows to 2025 in GitHub Actions (python#14…

    8eaeb52
  21. ljfp
    added a commit that references this issue on Apr 25, 2026

    pythongh-138744: Upgrade Windows to 2025 in GitHub Actions (python#14…

    3546a2e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    OS-windowsinfraCI, GitHub Actions, buildbots, Dependabot, etc.testsTests in the Lib/test dirtype-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions