Skip to content

Conversation

@zooba
Copy link
Member

@zoobazooba commented Nov 16, 2022

@bedevere-bot
Copy link

🤖 New build scheduled with the buildbot fleet by @zooba for commit fd6f008 🤖

If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again.

@bedevere-botbedevere-bot removed the 🔨 test-with-buildbots Test PR w/ buildbots; report in status section label Nov 16, 2022
@zooba
Copy link
MemberAuthor

The buildbot failures all seem to be because of another change that will be fixed by #99543

@zoobazooba merged commit 7c57857 into python:mainNov 16, 2022
@miss-islington
Copy link
Contributor

Thanks @zooba for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11.
🐍🍒⛏🤖

@zoobazooba deleted the gh-99370 branch November 16, 2022 21:41
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Nov 16, 2022
…for test (pythonGH-99523) (cherry picked from commit 7c57857) Co-authored-by: Steve Dower <steve.dower@python.org>
@bedevere-bot
Copy link

GH-99550 is a backport of this pull request to the 3.11 branch.

@bedevere-botbedevere-bot removed the needs backport to 3.11 only security fixes label Nov 16, 2022
@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot AMD64 Windows10 3.x has failed when building commit 7c57857.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/all/#builders/146/builds/3990) and take a look at the build logs.
  4. Check if the failure is related to this commit (7c57857) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/all/#builders/146/builds/3990

Failed tests:

  • test_threading

Summary of the results of the build (if available):

==

Click to see traceback logs
remote: Enumerating objects: 9, done. remote: Counting objects: 11% (1/9) remote: Counting objects: 22% (2/9) remote: Counting objects: 33% (3/9) remote: Counting objects: 44% (4/9) remote: Counting objects: 55% (5/9) remote: Counting objects: 66% (6/9) remote: Counting objects: 77% (7/9) remote: Counting objects: 88% (8/9) remote: Counting objects: 100% (9/9) remote: Counting objects: 100% (9/9), done. remote: Compressing objects: 25% (1/4) remote: Compressing objects: 50% (2/4) remote: Compressing objects: 75% (3/4) remote: Compressing objects: 100% (4/4) remote: Compressing objects: 100% (4/4), done. remote: Total 5 (delta 4), reused 1 (delta 1), pack-reused 0  From https://github.com/python/cpython * branch main -> FETCH_HEAD Note: checking out '7c57857340befcb90394bc347c904ca62049b684'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> HEAD is now at 7c57857... gh-99370: Prefer LIBDIR from sysconfig when locating libpython for test (GH-99523) Switched to and reset branch 'main' Could Not Find D:\buildarea\3.x.bolen-windows10\build\Lib\*.pyc The system cannot find the file specified. Could Not Find D:\buildarea\3.x.bolen-windows10\build\PCbuild\python*.zip Fatal Python error: _PyInterpreterState_GET: the function must be called with the GIL held, after Python initialization and before Python finalization, but the GIL is released (the current Python thread state is NULL) Python runtime state: initialized Current thread 0x00002dcc (most recent call first): <no Python frame> Thread 0x00003164 (most recent call first): File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\test_threading.py", line 847 in test_frame_tstate_tracing File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\case.py", line 579 in _callTestMethod File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\case.py", line 623 in run File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\case.py", line 678 in __call__ File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\suite.py", line 122 in run File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\suite.py", line 84 in __call__ File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\suite.py", line 122 in run File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\suite.py", line 84 in __call__ File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\suite.py", line 122 in run File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\suite.py", line 84 in __call__ File "D:\buildarea\3.x.bolen-windows10\build\Lib\unittest\runner.py", line 208 in run File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\__init__.py", line 1100 in _run_suite File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\__init__.py", line 1226 in run_unittest File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\runtest.py", line 281 in _test_module File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\runtest.py", line 317 in _runtest_inner2 File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\runtest.py", line 360 in _runtest_inner File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\runtest.py", line 235 in _runtest File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\runtest.py", line 265 in runtest File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line 352 in rerun_failed_tests File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line 754 in _main File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line 709 in main File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line 773 in main File "D:\buildarea\3.x.bolen-windows10\build\Lib\test\__main__.py", line 2 in <module> File "D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line 88 in _run_code File "D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line 198 in _run_module_as_main Extension modules: _testcapi, _wmi (total: 2) Cannot open file 'D:\buildarea\3.x.bolen-windows10\build\test-results.xml' for upload Could Not Find D:\buildarea\3.x.bolen-windows10\build\PCbuild\python*.zip

miss-islington added a commit that referenced this pull request Nov 16, 2022
…st (GH-99523) (cherry picked from commit 7c57857) Co-authored-by: Steve Dower <steve.dower@python.org>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@zooba@bedevere-bot@miss-islington