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: FAILUREEnvironment
- 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
Bug report
Bug description:
When running the
test__opcodetest with a build that uses--enable-pystats, there is a mismatch between the expected specialized opcodes and the actual ones. The test is expectingjump_backwardin the specialized opcodes list, but it's not present in the actual stats.Configuration
Test Output
Environment
CPython versions tested on:
CPython main branch, 3.14
Operating systems tested on:
Linux
Linked PRs