Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

gh-128231: Useruncode() return value for failing early#129488

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
encukou merged 2 commits intopython:mainfrombswck:make-prompts-fail-early-in-repl
Feb 24, 2025

Conversation

@bswck
Copy link
Contributor

@bswckbswck commentedJan 30, 2025•
edited
Loading

Closesgh-128231.

Any potential downstream subclasses (which are hard to imagine, but who knows, Python is big) that overrideruncode() can introduce this protocol gradually, with the old behavior preserved until then (backward compatibility).

@bswck
Copy link
ContributorAuthor

bswck commentedJan 30, 2025•
edited
Loading

Should we document the new sentinel? It seems theInteractiveColoredConsole class isn't documented anywhere.

@bswckbswckforce-pushed themake-prompts-fail-early-in-repl branch from1004941 to71c4a5fCompareJanuary 30, 2025 23:13
@ZeroIntensityZeroIntensity added the topic-replRelated to the interactive shell labelJan 31, 2025
@Eclips4
Copy link
Member

Should we document the new sentinel? It seems theInteractiveColoredConsole class isn't documented anywhere.

I don't think that we should document it.

Copy link
Member

@Eclips4Eclips4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM. Thank you

@Eclips4Eclips4 added the needs backport to 3.13bugs and security fixes labelJan 31, 2025
@bswck
Copy link
ContributorAuthor

@encukou (Pinging as discussed on stream)

Copy link
Member

@ZeroIntensityZeroIntensity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Might as well throw my approval on here too. I think this makes sense.

@bswck
Copy link
ContributorAuthor

bswck commentedFeb 13, 2025•
edited
Loading

Will also ping@asvetlov as he had reviewed my first PR, relevant to the (asyncio) REPL.

@encukou
Copy link
Member

This makes sense to me!
PerhapsSTATEMENT_FAILED is not the ideal API, but it's contained to private subclasses.

I'll give a chance to the REPL experts to review, but if there are no objections next week I plan to merge this.

ZeroIntensity, bswck, and Eclips4 reacted with hooray emoji

@encukouencukou merged commit7ed3dc6 intopython:mainFeb 24, 2025
66 checks passed
@miss-islington-app
Copy link

Thanks@bswck for the PR, and@encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull requestFeb 24, 2025
…onGH-129488)(cherry picked from commit7ed3dc6)Co-authored-by: Bartosz Sławecki <bartoszpiotrslawecki@gmail.com>
@bedevere-app
Copy link

GH-130513 is a backport of this pull request to the3.13 branch.

@bedevere-appbedevere-appbot removed the needs backport to 3.13bugs and security fixes labelFeb 24, 2025
hugovk pushed a commit that referenced this pull requestMar 28, 2025
…129488) (#130513)gh-128231: Use `runcode()` return value for failing early (GH-129488)(cherry picked from commit7ed3dc6)Co-authored-by: Bartosz Sławecki <bartoszpiotrslawecki@gmail.com>
@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 CentOS9 NoGIL 3.13 (tier-1) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1608/builds/601) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1608/builds/601

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:15:04) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.itamaro-centos-aws.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotARM64 MacOS M1 NoGIL 3.13 (tier-2) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1408/builds/1023) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1408/builds/1023

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:16:47) [Clang 15.0.0 (clang-1500.0.40.1)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-arm64-aws.macos-with-brew.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@ZeroIntensity
Copy link
Member

Uh oh, that looks related. Should we revert the 3.13 PR@hugovk?

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 FreeBSD 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1491/builds/1057) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1491/builds/1057

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/buildbot/buildarea/3.13.ware-freebsd/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 06:23:23) [Clang 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2 on freebsd13\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/buildbot/buildarea/3.13.ware-freebsd/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotARM64 macOS 3.13 (tier-2) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1404/builds/828) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1404/builds/828

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:28:40) [Clang 16.0.0 (clang-1600.0.26.4)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/Users/buildbot/buildarea/3.13.pablogsal-macos-m1.macos-with-brew/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 Windows Server 2022 NoGIL 3.13 (tier-1) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1488/builds/1128) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1488/builds/1128

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"C:\Users\Administrator\buildarea\3.13.itamaro-win64-srv-22-aws.x64.nogil\build\Lib\test\test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:25:43) [MSC v.1943 64 bit (AMD64)] on win32\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\concurrent\\futures\\_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\concurrent\\futures\\_base.py", line 401, in __get_result\n    raise self._exception\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\asyncio\\__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "C:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\asyncio\\__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \nC:\\Users\\Administrator\\buildarea\\3.13.itamaro-win64-srv-22-aws.x64.nogil\\build\\Lib\\asyncio\\base_events.py:758: ResourceWarning: unclosed event loop <ProactorEventLoop running=False closed=False debug=False>\n'

@bedevere-bot
Copy link

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

Hi! The buildbotx86 Debian Installed with X 3.13 (no tier) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1398/builds/1056) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1398/builds/1056

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 06:34:22) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/buildbot/buildarea/3.13.ware-debian-x86.installed/build/target/lib/python3.13/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 FreeBSD14 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1481/builds/1086) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1481/builds/1086

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 12:33:55) [Clang 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2 on freebsd14\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.opsec-fbsd14/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotx86 Debian Non-Debug with X 3.13 (no tier) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1389/builds/1066) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1389/builds/1066

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 06:40:14) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/buildbot/buildarea/3.13.ware-debian-x86.nondebug/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotx86-64 MacOS Intel ASAN NoGIL 3.13 (tier-1) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1460/builds/1024) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1460/builds/1024

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:37:17) [Clang 14.0.3 (clang-1403.0.22.14.1)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.macos-with-brew.asan.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 Debian root 3.13 (tier-1) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1441/builds/1025) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1441/builds/1025

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/root/buildarea/3.13.angelico-debian-amd64/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 22:41:51) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'Traceback (most recent call last):  File"/root/buildarea/3.13.angelico-debian-amd64/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 22:41:51) [GCC 12.2.0] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 449, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/root/buildarea/3.13.angelico-debian-amd64/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbotx86-64 MacOS Intel NoGIL 3.13 (tier-1) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1449/builds/1031) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1449/builds/1031

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ experimental free-threading build (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 11:51:41) [Clang 14.0.3 (clang-1403.0.22.14.1)] on darwin\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/Users/ec2-user/buildbot/buildarea/3.13.itamaro-macos-intel-aws.nogil/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL8 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1469/builds/847) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1469/builds/847

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:58:39) [GCC 8.5.0 20210514 (Red Hat 8.5.0-24)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@hugovk
Copy link
Member

hugovk commentedMar 28, 2025•
edited
Loading

The 3.13 backport is failing GHA and buildbots, it must have gotten out of sync between last CI run and merge.

Let's revert the 3.13 backport to get the CI back to green.

Edit: revert PR#131834

@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL8 LTO + PGO 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1436/builds/849) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1436/builds/849

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 08:09:27) [GCC 8.5.0 20210514 (Red Hat 8.5.0-24)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

hugovk added a commit to hugovk/cpython that referenced this pull requestMar 28, 2025
@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL9 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1584/builds/566) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1584/builds/566

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:16:03) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/runpy.py", line 198, in _run_module_as_main\n    return _run_code(code, main_globals, None,\n                     "__main__", mod_spec)\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/runpy.py", line 88, in _run_code\n    exec(code, run_globals)\n    ~~~~^^^^^^^^^^^^^^^^^^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL8 LTO 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1458/builds/853) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1458/builds/853

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 08:15:50) [GCC 8.5.0 20210514 (Red Hat 8.5.0-24)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel8-s390x.lto/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL9 LTO + PGO 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1574/builds/566) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1574/builds/566

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:28:25) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto-pgo/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL9 LTO 3.13 (tier-3) has failed when building commit8f6a9aa.

What do you need to do:

  1. Don't panic.
  2. Checkthe 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/#/builders/1577/builds/569) and take a look at the build logs.
  4. Check if the failure is related to this commit (8f6a9aa) 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/#/builders/1577/builds/569

Failed tests:

  • test_repl

Failed subtests:

  • test_multiple_statements_fail_early - test.test_repl.TestAsyncioREPL.test_multiple_statements_fail_early

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/test/test_repl.py", line304, intest_multiple_statements_fail_earlyself.assertNotIn("afterwards", output)~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^AssertionError: 'afterwards' unexpectedly found in 'asyncio REPL 3.13.2+ (heads/3.13:8f6a9aa6aeb, Mar 28 2025, 07:34:29) [GCC 11.5.0 20240719 (Red Hat 11.5.0-5)] on linux\nUse "await" directly instead of "asyncio.run()".\nType "help", "copyright", "credits" or "license" for more information.\n>>> import asyncio\n>>> Traceback (most recent call last):\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/concurrent/futures/_base.py", line 456, in result\n    return self.__get_result()\n           ~~~~~~~~~~~~~~~~~^^\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/concurrent/futures/_base.py", line 401, in __get_result\n    raise self._exception\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/asyncio/__main__.py", line 42, in callback\n    coro = func()\n  File "<stdin>", line 1, in <module>\n    1 / 0; print(\'afterwards\')\n    ~~^~~\nZeroDivisionError: division by zero\n>>> \nexiting asyncio REPL...\nTraceback (most recent call last):\n  File "<frozen runpy>", line 198, in _run_module_as_main\n  File "<frozen runpy>", line 88, in _run_code\n  File "/home/buildbot/buildarea/3.13.cstratak-rhel9-s390x.lto/build/Lib/asyncio/__main__.py", line 204, in <module>\n    sys.exit(return_code)\n    ~~~~~~~~^^^^^^^^^^^^^\nSystemExit: 0\n>>> \n'

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

Reviewers

@ZeroIntensityZeroIntensityZeroIntensity approved these changes

@Eclips4Eclips4Eclips4 approved these changes

@pablogsalpablogsalAwaiting requested review from pablogsalpablogsal is a code owner

@lysnikolaoulysnikolaouAwaiting requested review from lysnikolaoulysnikolaou is a code owner

@ambvambvAwaiting requested review from ambvambv is a code owner

@1st11st1Awaiting requested review from 1st11st1 is a code owner

@asvetlovasvetlovAwaiting requested review from asvetlovasvetlov is a code owner

@kumaraditya303kumaraditya303Awaiting requested review from kumaraditya303kumaraditya303 is a code owner

@willingcwillingcAwaiting requested review from willingcwillingc is a code owner

Assignees

No one assigned

Labels

topic-replRelated to the interactive shell

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

In the new REPL, multiline input execution should fail fast

6 participants

@bswck@Eclips4@encukou@bedevere-bot@ZeroIntensity@hugovk
[8]ページ先頭
©2009-2025 Movatter.jp