Description

furkanonder

opened on Apr 22, 2025

Issue body actions

Bug report

Bug description:

When running the test__opcode test with a build that uses --enable-pystats, there is a mismatch between the expected specialized opcodes and the actual ones. The test is expecting jump_backward in the specialized opcodes list, but it's not present in the actual stats.

Configuration

./configure --with-pydebug --enable-pystats

Test Output

╰─$ ./python -m test test__opcode                                                                                                                                                                           82595ms
Using random seed: 2739258338
0:00:00 load avg: 0.97 Run 1 test sequentially in a single process
0:00:00 load avg: 0.97 [1/1] test__opcode
test test__opcode failed -- Traceback (most recent call last):
  File "/home/arf/Desktop/cpython/Lib/test/test__opcode.py", line 131, in test_specialization_stats
    self.assertCountEqual(stats.keys(), specialized_opcodes)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: Element counts were not equal:
First has 0, Second has 1:  'jump_backward'

0:00:00 load avg: 0.97 [1/1/1] test__opcode failed (1 failure)

== Tests result: FAILURE ==

1 test failed:
    test__opcode

Total duration: 52 ms
Total tests: run=7 failures=1
Total test files: run=1/1 failed=1
Result: FAILURE

Environment

• OS: Arch Linux (Linux 6.14.2-arch1-1)

CPython versions tested on:

CPython main branch, 3.14

Operating systems tested on:

Linux

Linked PRs

• gh-132815: Add support for JUMP_BACKWARD in specialization stats #135606
• [3.14] gh-132815: Add support for JUMP_BACKWARD in specialization stats (GH-135606) #135612

Activity

1. furkanonder

   added

   testsTests in the Lib/test dirTests in the Lib/test dir

   type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error

   3.14bugs and security fixesbugs and security fixes

   on Apr 22, 2025
2. furkanonder commented on Apr 22, 2025

   

   furkanonder

   on Apr 22, 2025

   ContributorAuthor

   More actions

   bisect to #128918

   @colesbury @markshannon
3. AndPuQing commented on Jun 17, 2025

   

   AndPuQing

   on Jun 17, 2025

   Contributor

   More actions

   In my bisect testing, it identified PR #129194 as the source of the issue. This PR added JUMP_BACKWARD to _specializations in Lib/_opcode_metadata.py.

   I've created a fix in PR #135606 to address this problem.

   Reacted by Furkan Onder
4. vstinner

   added a commit that references this issue on Jun 17, 2025

   gh-132815: Add support for JUMP_BACKWARD in specialization stats (#13…

   a9e66a7
5. miss-islington

   added a commit that references this issue on Jun 17, 2025

   pythongh-132815: Add support for JUMP_BACKWARD in specialization stats (

   f2f5e06
6. vstinner

   closed this as completedon Jun 17, 2025
7. vstinner commented on Jun 17, 2025

   

   vstinner

   on Jun 17, 2025

   Member

   More actions

   Fixed. Thanks for the bug report.

   Reacted by Furkan Onder
8. vstinner

   added a commit that references this issue on Jun 17, 2025

   [3.14] gh-132815: Add support for JUMP_BACKWARD in specialization sta…

   c1735c5
9. lkollar

   added a commit that references this issue on Jun 19, 2025

   pythongh-132815: Add support for JUMP_BACKWARD in specialization stats (

   74063fd
10. Pranjal095

    added a commit that references this issue on Jul 12, 2025

    pythongh-132815: Add support for JUMP_BACKWARD in specialization stats (

    eb5c506
11. taegyunkim

    added a commit that references this issue on Aug 4, 2025

    pythongh-132815: Add support for JUMP_BACKWARD in specialization stats (

    4f93909
12. Agent-Hellboy

    added a commit that references this issue on Aug 19, 2025

    pythongh-132815: Add support for JUMP_BACKWARD in specialization stats (

    e0e5bb2

Issue actions