Activity

1. itamaro

   added

   type-featureA feature request or enhancementA feature request or enhancement

   buildThe build process and cross-buildThe build process and cross-build

   topic-free-threading

   on Nov 18, 2023
2. itamaro

   added a commit that references this issue on Nov 18, 2023

   pythonGH-112245: Promote free threaded CI

   8d14e3b
3. terryjreedy commented on Nov 18, 2023

   

   terryjreedy

   on Nov 18, 2023

   Member

   More actions

   I presume it would always fail and would have to be ignored. Given that, why waste the resources? Anyone interested in checking how much failure should run as desired -- and this should be an option, say with a comment.
4. itamaro commented on Nov 18, 2023

   

   itamaro

   on Nov 18, 2023

   ContributorAuthor

   More actions

   I presume it would always fail and would have to be ignored. Given that, why waste the resources?

   why would it always fail?
   it is being used for opt-in testing on free-threaded-related PRs (using the label), and has been passing quite consistently.
   also the buildbot Linux & MacOS builders have been very stable over the last few weeks (I proposed to mark them as stable). only the Windows buildbot is unstable, and that's a known issue that's pending on some packaging-related changes.
5. terryjreedy commented on Nov 18, 2023

   

   terryjreedy

   on Nov 18, 2023

   Member

   More actions

   I just added 'topic: free-threading' to a PR I expect to update today, triggering a test. I am curious what happens with test_idle. If it passes, I will do a local FT rebuild and run IDLE itself.

   Reacted by Itamar Oren
6. colesbury commented on Nov 19, 2023

   

   colesbury

   on Nov 19, 2023

   Contributor

   More actions

   The "free-threaded" builds run with the GIL. They are not actually "free-threaded" and won't be until all the pieces are in place. We are basically doing the following for --disable-gil builds for 3.13:

   1. Integrate the pieces of PEP 703, but with the GIL enabled. There's still a lot of value in the building and testing because many bugs from new code show up even with the GIL enabled and we want to make sure the #ifdef Py_NOGIL code paths work. At this point (now), both the CI and local --disable-gil builds always run with the GIL enabled.
   2. After most of the pieces are integrated, we start testing locally with the GIL disable via an environment variable switch and fix the inevitable bugs. At this point the --disable-gil CI still runs with the GIL enabled, but increasingly the local testing of --disable-gil builds will be with the GIL disabled.
   3. Once the local builds and tests are stable, we switch the --disable-gil CI to run with the GIL disabled.

   Reacted by Itamar Oren and Kirill Podoprigora
7. itamaro

   added a commit that references this issue on Nov 19, 2023

   Mark NoGIL Linux & MacOS builders as stable (#444)

   6c3e0d8
8. carljm

   added a commit that references this issue on Nov 28, 2023

   GH-112245: Promote free threaded CI (#112246)

   48dfd74
9. itamaro

   closed this as completedon Nov 28, 2023
10. aisk

    added a commit that references this issue on Feb 11, 2024

    pythonGH-112245: Promote free threaded CI (python#112246)

    dfec5c1
11. JokoZulkarnain99

    added a commit that references this issue on Aug 5, 2024

    Mark NoGIL Linux & MacOS builders as stable (#444)

    82bd89b
12. Glyphack

    added a commit that references this issue on Sep 2, 2024

    pythonGH-112245: Promote free threaded CI (python#112246)

    2fb7fe7