Skip to content

Add dtrace worker tag support - #754

Merged
encukou merged 3 commits into
python:mainfrom
stratakis:even_more_minimal_dtrace
Aug 20, 2026
Merged

Add dtrace worker tag support#754
encukou merged 3 commits into
python:mainfrom
stratakis:even_more_minimal_dtrace

Conversation

@stratakis

Copy link
Copy Markdown
Contributor

No description provided.

stratakis and others added 2 commits July 2, 2026 16:09
Co-authored-by: Petr Viktorin <encukou@gmail.com>
Co-authored-by: Petr Viktorin <encukou@gmail.com>

@encukou encukou left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is how I'd do it. Maybe the branch logic could be elsewhere, but "dtrace is installed" is a feature of the worker, and I think tags are great for such features.

@encukou

encukou commented Jul 2, 2026

Copy link
Copy Markdown
Member

I generally want to move to using tags for configure options -- but mostly builder tags: e.g. having separate factories for Windows64PGONoGilTailcallBuild and all the other combinations of PGO/NoGil/Tailcall aren't a good use of subclassing.

Does that look like a good direction?

@encukou
encukou requested a review from zware July 2, 2026 17:08
@stratakis

stratakis commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

I generally want to move to using tags for configure options -- but mostly builder tags: e.g. having separate factories for Windows64PGONoGilTailcallBuild and all the other combinations of PGO/NoGil/Tailcall aren't a good use of subclassing.

Does that look like a good direction?

For me it does sound that it;s a proper direction as it would reduce a lot of subclassing, given of course that an option to do extra customizations without much hassle will be there.

@vstinner vstinner left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

So dtrace is not enabled on RHEL8 workers. DTrace doesn't work on RHEL8?

@stratakis

Copy link
Copy Markdown
Contributor Author

LGTM.

So dtrace is not enabled on RHEL8 workers. DTrace doesn't work on RHEL8?

It should but the upstream fix is on 3.15+, RHEL8 workers test up to 3.12.

@stratakis
stratakis marked this pull request as draft July 3, 2026 12:56
@stratakis

Copy link
Copy Markdown
Contributor Author

Converted to a draft, there is an issue with the probes on shared builds when running the tests. Granted the test needs sudo or systemtap permission but I'd rather have this fixed first than risk buildbots failing unexpectedly.

@zware zware left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is exactly the direction I've been hoping we would move, thank you!

@stratakis

stratakis commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

Converted to a draft, there is an issue with the probes on shared builds when running the tests. Granted the test needs sudo or systemtap permission but I'd rather have this fixed first than risk buildbots failing unexpectedly.

The test failures should be resolved by python/cpython#153372. After hopefully merging this I'll un-draft this PR.

@stratakis
stratakis marked this pull request as ready for review August 20, 2026 11:21
@stratakis

Copy link
Copy Markdown
Contributor Author

Undrafting, the PRs have been merged. Could you re-review?

@encukou
encukou merged commit 62f8557 into python:main Aug 20, 2026
1 check passed
@encukou

encukou commented Aug 20, 2026

Copy link
Copy Markdown
Member

Thanks!

I applied the config temporarily, and a build passed with it!

@encukou

encukou commented Aug 21, 2026

Copy link
Copy Markdown
Member

@cstratak: The PPC64LE build is failing, though. Is that set up correctly?

Edit: aarch64 too

@stratakis

Copy link
Copy Markdown
Contributor Author

@cstratak: The PPC64LE build is failing, though. Is that set up correctly?

Edit: aarch64 too

The ppc64le build was due to D-processes, rebooted to clean them up, let's see, if it appears again that would be an issue for the kernel/systemtap.

The issue on aarch64 is a separate one, could please file an issue? I believe it needs some code changes/hardening on the tests.

(PS, I'll be on PTO next week so I'll be able to get to it after that).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants