Results from running CPython test suite in a sub interpreter #112677
Labels
tests
Tests in the Lib/test dir
topic-subinterpreters
type-bug
An unexpected behavior, bug, or error
Test suite in sub interpreters
This issue is about running the CPython test suite in sub interpreters. On the current HEAD there are lots of failures, crashes and related issues.
I'm raising this issue to share the approach I used and discuss how we could automate this into CI somehow, also I want to discuss some of these tests and whether we've tracked issues to the related failures (the XML test failures are a good example)
Approach
Initially I wrote this script to iterate over the list of tests, but soon found that crashes often occur during finalize, so it made more sense to initiate them one at a time so I could capture which test suites cause a finalize crash.
All tests require
faulthandler
, which is not compatible with sub interpreters so I made a fake module that patches all the methods and load that intosys.modules
to force the suite to execute.Test Script
Test Results
The Detail will just be 1 error message captured, for those tests there are often multiple.
Test Results
[1] CPython process crashes on finalise operation, most of the cases I've debugged are because of datetime's global state already being destroyed and then CPython trying to iterate the items of a tuple in the module that has already been freed (see #112140).
To loop over a test plan (made by using
-m test --list-tests
) and write the results to a folder, use this scriptAnd finally to make this Markdown table I wrote this script:
Test Results parser
CPython versions tested on:
CPython main branch
Operating systems tested on:
macOS
The text was updated successfully, but these errors were encountered: