Skip to content

Test suite fails on AMD64 Windows11 Non-Debug 3.x: Python fails with STATUS_VIRUS_INFECTED #144652

Closed

Description

@vstinner

Extract of: https://buildbot.python.org/#/builders/914/builds/5450

0:29:46 load avg: 1.07 [ 1/38/1] test_filecmp worker non-zero exit code (Exit code 3221227782)
0:29:46 load avg: 1.07 [ 2/38/2] test.test_concurrent_futures.test_thread_pool worker non-zero exit code (Exit code 3221227782)
0:29:46 load avg: 1.07 [ 3/38/3] test_contextlib worker non-zero exit code (Exit code 3221227782)
0:29:46 load avg: 1.07 [ 4/38/4] test_coroutines worker non-zero exit code (Exit code 3221227782)
0:29:46 load avg: 1.07 [ 5/38/5] test_zipimport_support worker non-zero exit code (Exit code 3221227782)
0:29:46 load avg: 1.07 [ 6/38/6] test_contextlib_async worker non-zero exit code (Exit code 3221227782)
0:29:46 load avg: 1.07 [ 7/38/7] test.test_io.test_univnewlines worker non-zero exit code (Exit code 3221227782)

3221227782 is 0xc0000906 or STATUS_VIRUS_INFECTED: "The operation did not complete successfully because the file contains a virus".

@zware: Would you mind to look at your buildbot worker to check if an antivirus application detects freshly built Python binaries as virus?

Linked PRs

Activity

  1. added 2 commits that reference this issue on Feb 10, 2026
  2. encukou commented on Feb 10, 2026

    @encukou
    Member

    3221227782 is 0xc0000906 or STATUS_VIRUS_INFECTED: "The operation did not complete successfully because the file contains a virus"

    Oh!
    For reference, do you know where this is documented?

  3. vstinner commented on Feb 10, 2026

    @vstinner
    MemberAuthor

    For reference, do you know where this is documented?

    I found for example this long table of NTSTATUS Values:
    https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55

  4. added a commit that references this issue on Feb 10, 2026
  5. added a commit that references this issue on Feb 10, 2026
  6. added a commit that references this issue on Feb 10, 2026
  7. zware commented on Feb 10, 2026

    @zware
    Member

    Looking at the Windows Security "Protection history" it looks like it started finding Trojan:Win32/Bearfoos.A!ml in B:\uildarea\3.x.ware-win11.nondebug\build\PCbuild\amd64\python315.dll a few days ago. I've added an exclusion for the B:\uildarea directory.

  8. vstinner commented on Feb 10, 2026

    @vstinner
    MemberAuthor

    I've added an exclusion for the B:\uildarea directory.

    Thanks. I close the issue. Reopen it if the issue comes back.

  9. zooba commented on Feb 10, 2026

    @zooba
    Member

    Yeah, there's some false positives going around - breaking a lot of my private CI too...

    Excluding the build area should be good enough. Probably a reasonable speed improvement, too

  10. added a commit that references this issue on Feb 15, 2026
  11. added a commit that references this issue on Feb 28, 2026
  12. added a commit that references this issue on Apr 25, 2026
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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions