This repository was archived by the owner on Feb 13, 2025. It is now read-only.
Undefined behaviour of the C-Python tests caused by lazy initialisation of stackless #126
Labels
Milestone
Comments
akruis
pushed a commit
that referenced
this issue
Oct 29, 2017
Load the module "stackless" early in all C-Python tests. This ensures a defined behaviour of the tests even, if the execution order gets randomised. https://bitbucket.org/stackless-dev/stackless/issues/126
akruis
pushed a commit
that referenced
this issue
Oct 29, 2017
akruis
pushed a commit
that referenced
this issue
Oct 29, 2017
akruis
pushed a commit
that referenced
this issue
Oct 29, 2017
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Originally reported by: Anselm Kruis (Bitbucket: akruis, GitHub: akruis)
Problem
Since change e5a2ecca2b08 Stackless initializes the stackless subsystem only if application code loads the module stackless. This causes undefined behaviour in the C-Python test suite, if the execution order of the tests gets randomized. Especially some pickling tests are sensitive, because the initialisation of Stackless enables the pickling of additional types.
I observed failures especially with 3.5-slp, but the problem exists in all 3.x branches.
Proposed Solution
I'll import stackless in the module test.support. Nearly every test-module imports this module very early. While I'm at it, I'll also unify the tests for stackless being available.
The text was updated successfully, but these errors were encountered: