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-104584: Fix assert in DEOPT macro -- should fix buildbot#106131

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
gvanrossum merged 1 commit intopython:mainfromgvanrossum:fix-deopt
Jun 27, 2023

Conversation

gvanrossum
Copy link
Member

@gvanrossumgvanrossum commentedJun 27, 2023
edited by bedevere-bot
Loading

That's what I get for not running all buildbots forgh-105924.

@markshannon
Copy link
Member

There are a lot of warnings, asopcode is auint8_t in the tier1 interpreter, soopcode >= 256 is always false.
Maybe redefineDEOPT_IF for the uop interpreter, with a different assert?

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 Windows10 3.x has failed when building commitbb578a0.

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/all/#builders/146/builds/5583) and take a look at the build logs.
  4. Check if the failure is related to this commit (bb578a0) 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/5583

Failed tests:

  • test_concurrent_futures

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

== Tests result: FAILURE then SUCCESS ==

415 tests OK.

10 slowest tests:

  • test_math: 5 min 7 sec
  • test_multiprocessing_spawn: 4 min 29 sec
  • test_capi: 2 min 24 sec
  • test_wmi: 2 min 14 sec
  • test_mmap: 2 min 4 sec
  • test_peg_generator: 2 min 4 sec
  • test_tokenize: 1 min 58 sec
  • test_io: 1 min 51 sec
  • test_unparse: 1 min 49 sec
  • test_unicodedata: 1 min 35 sec

31 tests skipped:
test.test_asyncio.test_unix_events test_curses test_dbm_gnu
test_dbm_ndbm test_devpoll test_epoll test_fcntl test_fork1
test_gdb test_grp test_ioctl test_kqueue test_multiprocessing_fork
test_multiprocessing_forkserver test_openpty test_perf_profiler
test_perfmaps test_poll test_posix test_pty test_pwd test_readline
test_resource test_syslog test_threadsignals test_wait3 test_wait4
test_xxlimited test_xxtestfuzz test_zipfile64 test_zoneinfo

1 re-run test:
test_concurrent_futures

Total duration: 22 min 12 sec

Click to see traceback logs
Traceback (most recent call last):  File"D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line198, in_run_module_as_mainreturn _run_code(code, main_globals,None,^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"D:\buildarea\3.x.bolen-windows10\build\Lib\runpy.py", line88, in_run_codeexec(code, run_globals)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\__main__.py", line2, in<module>    main()  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line822, inmain    Regrtest().main(tests=tests,**kwargs)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line752, inmainwith os_helper.temp_cwd(test_cwd,quiet=True):  File"D:\buildarea\3.x.bolen-windows10\build\Lib\contextlib.py", line155, in__exit__self.gen.throw(value)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line531, intemp_cwdwith temp_dir(path=name,quiet=quiet)as temp_path:  File"D:\buildarea\3.x.bolen-windows10\build\Lib\contextlib.py", line155, in__exit__self.gen.throw(value)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line485, intemp_dir    rmtree(path)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line442, inrmtree    _rmtree(path)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line385, in_rmtreeTraceback (most recent call last):  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\__init__.py", line207, in_force_runreturn func(*args)^^^^^^^^^^^PermissionError:[WinError 32] The process cannot access the file because it is being used by another process: 'D:\\buildarea\\3.x.bolen-windows10\\build\\build\\test_python_4948�\\test_python_worker_3704�'Traceback (most recent call last):  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line480, intemp_diryield path  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\support\os_helper.py", line533, intemp_cwdyield cwd_dir  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line758, inmainself._main(tests, kwargs)  File"D:\buildarea\3.x.bolen-windows10\build\Lib\test\libregrtest\main.py", line817, in_main    sys.exit(0)SystemExit:0

@gvanrossum
Copy link
MemberAuthor

There are a lot of warnings, asopcode is auint8_t in the tier1 interpreter, soopcode >= 256 is always false. Maybe redefineDEOPT_IF for the uop interpreter, with a different assert?

Oh dang. Of course it is. On it.

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

@markshannonmarkshannonAwaiting requested review from markshannonmarkshannon is a code owner

Assignees
No one assigned
Labels
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@gvanrossum@markshannon@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp