Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
Closed
Description
Bug report
Bug description:
We have had a number of issues reported over the years where a test included in the subset of tests run for PGO profiling fails.#135424 is a recent example of one such failure.
$ ./configure--enable-optimizations$make[...]# Next, run the profile task to generate the profile information.LLVM_PROFILE_FILE="/Users/sysadmin/cpython/code-%p.profclangr" ./python.exe-mtest--pgo--timeout=Usingrandomseed:4213059023RaisedRLIMIT_NOFILE:256->10240:00:00loadavg:1.95Run43testssequentiallyinasingleprocess0:00:00loadavg:1.95 [1/43]test_array[...]0:00:23loadavg:1.69 [40/43]test_tabnannypassed0:00:23loadavg:1.69 [41/43]test_timetesttest_timefailed0:00:26loadavg:1.69 [41/43]test_timefailed (1error)0:00:26loadavg:1.69 [42/43]test_xml_etree0:00:26loadavg:1.69 [42/43]test_xml_etreepassed0:00:26loadavg:1.69 [43/43]test_xml_etree_c0:00:26loadavg:1.69 [43/43]test_xml_etree_cpassedTotalduration:26.6secTotaltests:run=9,234skipped=194Totaltestfiles:run=43/43failed=1skipped=1Result:FAILUREmake:*** [profile-run-stamp]Error2
Unfortunately, this isn't enough information to know why a particular test failed and a downstream builder of Python may not know how to proceed to obtain that information. During a normal run of the test suite,regrtest will helpfully provide the details of why the test failed, i.e.:
$ ./configure$ make$ ./python.exe -m test test_timeUsing random seed: 3687295663Raised RLIMIT_NOFILE: 256 -> 10240:00:00 load avg: 0.74 Run 1 test sequentially in a single process0:00:00 load avg: 0.74 [1/1] test_timetest test_time failed -- Traceback (most recent call last): File "/Users/sysadmin/cpython/Lib/test/test_time.py", line 146, in test_clock_settime time.clock_settime(time.CLOCK_REALTIME, t) ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^FileNotFoundError: [Errno 2] No such file or directory0:00:03 load avg: 0.74 [1/1/1] test_time failed (1 error)== Tests result: FAILURE ==1 test failed: test_timeTotal duration: 3.1 secTotal tests: run=63 skipped=2Total test files: run=1/1 failed=1Result: FAILUREThe PGO test run step should provide the same error traceback info on failures.
CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
- gh-135489: Allow verbose output for PGO runs in _runtest function #135512
- [3.14] gh-135489: Show verbose output for failing tests during PGO profiling step with
--enable-optimizations(GH-135512) #135599 - [3.13] gh-135489: Show verbose output for failing tests during PGO profiling step with
--enable-optimizations(GH-135512) #135600