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

Add --inline-caches flag to dis command line#110249

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 4 commits intopython:mainfromgvanrossum:dis-show-caches
Oct 3, 2023

Conversation

@gvanrossum
Copy link
Member

@gvanrossumgvanrossum commentedOct 2, 2023•
edited
Loading

Thedis command line is undocumented (apart fromhttps://docs.python.org/3.13/library/cmdline.html) but darn handy. I've wanted to be able to to pass theinline_caches=True flag many times. This PR fulfills my wish.

I will merge this once CI passes.

@gvanrossumgvanrossumenabled auto-merge (squash)October 3, 2023 00:05
@gvanrossumgvanrossum merged commit6678ef4 intopython:mainOct 3, 2023
@bedevere-bot
Copy link

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

Hi! The buildbots390x RHEL7 LTO 3.x has failed when building commit6678ef4.

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/402/builds/5544) and take a look at the build logs.
  4. Check if the failure is related to this commit (6678ef4) 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/402/builds/5544

Failed tests:

  • test_embed

Failed subtests:

  • test_init_pybuilddir - test.test_embed.InitConfigTests.test_init_pybuilddir

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/test/test_embed.py", line1405, intest_init_pybuilddirwithself.tmpdir_with_python()as tmpdir:  File"/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/contextlib.py", line141, in__enter__returnnext(self.gen)^^^^^^^^^^^^^^  File"/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/test/test_embed.py", line1286, intmpdir_with_python    shutil.copyfile(self.test_exe, exec_copy)  File"/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/shutil.py", line273, incopyfile    _fastcopy_sendfile(fsrc, fdst)  File"/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/shutil.py", line164, in_fastcopy_sendfileraise errfromNone  File"/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Lib/shutil.py", line150, in_fastcopy_sendfile    sent= os.sendfile(outfd, infd, offset, blocksize)^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^OSError:[Errno 28] No space left on device: '/home/dje/cpython-buildarea/3.x.edelsohn-rhel-z.lto/build/Programs/_testembed' -> '/tmp/test_python_0a9adkog/tmpc3kc7qmk/_testembed'

@bedevere-bot
Copy link

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

Hi! The buildbotAMD64 Windows11 Non-Debug 3.x has failed when building commit6678ef4.

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/914/builds/2912) and take a look at the build logs.
  4. Check if the failure is related to this commit (6678ef4) 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/914/builds/2912

Failed tests:

  • test_int

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

==

Click to see traceback logs
Traceback (most recent call last):  File"b:\uildarea\3.x.ware-win11.nondebug\build\Lib\test\test_int.py", line743, intest_denial_of_service_prevented_str_to_intself.assertLessEqual(seconds_to_fail_extra_huge, seconds_to_convert/2)AssertionError:0.015625 not less than or equal to 0.0078125

@bedevere-bot
Copy link

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

Hi! The buildbotPPC64LE RHEL7 3.x has failed when building commit6678ef4.

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/446/builds/3984) and take a look at the build logs.
  4. Check if the failure is related to this commit (6678ef4) 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/446/builds/3984

Failed tests:

  • test.test_multiprocessing_forkserver.test_processes

Failed subtests:

  • test_kill - test.test_multiprocessing_forkserver.test_processes.WithProcessesTestProcess.test_kill

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

==

Click to see traceback logs
Traceback (most recent call last):  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/test/_test_multiprocessing.py", line563, intest_kill    exitcode=self._kill_process(multiprocessing.Process.kill)^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/test/_test_multiprocessing.py", line542, in_kill_processself.assertEqual(join(),None)^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/test/_test_multiprocessing.py", line242, in__call__returnself.func(*args,**kwds)^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/multiprocessing/process.py", line149, injoin    res=self._popen.wait(timeout)^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/multiprocessing/popen_fork.py", line43, inwaitreturnself.poll(os.WNOHANGif timeout==0.0else0)^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/multiprocessing/popen_forkserver.py", line65, inpollifnot wait([self.sentinel], timeout):^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/multiprocessing/connection.py", line1135, inwait    ready= selector.select(timeout)^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/selectors.py", line398, inselect    fd_event_list=self._selector.poll(timeout)^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File"/home/buildbot/buildarea/3.x.cstratak-RHEL7-ppc64le/build/Lib/test/_test_multiprocessing.py", line538, inhandlerraiseRuntimeError('join took too long:%s'% p)RuntimeError:join took too long: <Process name='Process-151' pid=18128 parent=16441 started daemon>

@bedevere-bot
Copy link

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

Hi! The buildbotPPC64LE RHEL7 LTO + PGO 3.x has failed when building commit6678ef4.

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/43/builds/4333) and take a look at the build logs.
  4. Check if the failure is related to this commit (6678ef4) 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/43/builds/4333

Failed tests:

  • test_socket

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:  50% (1/2)remote:Compressing objects: 100% (2/2)remote:Compressing objects: 100% (2/2), done.remote:Total 9 (delta 7), reused 9 (delta 7), pack-reused 0From https://github.com/python/cpython * branch            main       -> FETCH_HEADNote:checking out '6678ef41d2a188a92c7ac5249d716e942b5114a6'.You are in 'detached HEAD' state. You can look around, make experimentalchanges and commit them, and you can discard any commits you make in thisstate without impacting any branches by performing another checkout.If you want to create a new branch to retain commits you create, you maydo so (now or later) by using -b with the checkout command again. Example:  git checkout -b new_branch_nameHEAD is now at 6678ef4... Add --inline-caches flag to dis command line (#110249)Switched to and reset branch 'main'find:‘build’: No such file or directoryfind:‘build’: No such file or directoryfind:‘build’: No such file or directoryfind:‘build’: No such file or directorymake[2]:[Makefile:2789: clean-retain-profile] Error 1 (ignored)./Modules/_xxinterpchannelsmodule.c:104:1: warning: ‘get_module_from_owned_type’ defined but not used [-Wunused-function] get_module_from_owned_type(PyTypeObject *cls) ^~~~~~~~~~~~~~~~~~~~~~~~~~./Modules/_testcapi/unicode.c:In function ‘test_string_from_format’:./Modules/_testcapi/unicode.c:1538:1: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without test_string_from_format(PyObject *self, PyObject *Py_UNUSED(ignored)) ^~~~~~~~~~~~~~~~~~~~~~~./Modules/_testcapi/unicode.c:In function ‘test_string_from_format’:./Modules/_testcapi/unicode.c:1538:1: note: variable tracking size limit exceeded with -fvar-tracking-assignments, retrying without test_string_from_format(PyObject *self, PyObject *Py_UNUSED(ignored)) ^./Modules/_decimal/libmpdec/context.c:57: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time./Modules/_decimal/libmpdec/context.c:57: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time./Modules/_xxinterpchannelsmodule.c:104:1: warning: ‘get_module_from_owned_type’ defined but not used [-Wunused-function] get_module_from_owned_type(PyTypeObject *cls) ^~~~~~~~~~~~~~~~~~~~~~~~~~make:*** [Makefile:2012: buildbottest] Error 5

@gvanrossumgvanrossum deleted the dis-show-caches branchOctober 3, 2023 17:30
Glyphack pushed a commit to Glyphack/cpython that referenced this pull requestSep 2, 2024
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@brandtbucherbrandtbucherAwaiting requested review from brandtbucher

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@gvanrossum@bedevere-bot
[8]ページ先頭
©2009-2025 Movatter.jp