Skip to content

[rocprofiler-systems] Make lib artifact include versioned python<VER> folder when project is configured with a single python version#4454

Open
kcossett-amd wants to merge 1 commit intomainfrom
users/kcossett-amd/add-missing-asterix-in-rocprofiler-artifacts
Open

[rocprofiler-systems] Make lib artifact include versioned python<VER> folder when project is configured with a single python version#4454
kcossett-amd wants to merge 1 commit intomainfrom
users/kcossett-amd/add-missing-asterix-in-rocprofiler-artifacts

Conversation

@kcossett-amd
Copy link
Copy Markdown
Contributor

@kcossett-amd kcossett-amd commented Apr 10, 2026

Motivation

When testing a testing improvement PR, the python tests would fail when I configured + build TheRock locally with only a single python version being used.

The lib artifact does not include the python<ver>/ folder, but does include python/ (which is generated when multiple python versions are used during configure + build).

This was most likely not caught in CI as the runs usually use multiple python versions.

Technical Details

Make "lib/python/**" -> "lib/python*/**",inartifact-rocprofiler-systems.toml`

Test Plan

Tested locally using new tests that will be introduced in a future PR.
Also built locally and checked manually that it is present in output-linux-portable/build/dist/rocm/lib

Test Result

Future python tests pass.

When built locally so that only python3.12 is used, I now see that the rocprofsys package, located within our generated python3.12 folder is present in output-linux-portable/build/dist/rocm/lib.

Submission Checklist

@kcossett-amd kcossett-amd marked this pull request as ready for review April 10, 2026 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: TODO

Development

Successfully merging this pull request may close these issues.

1 participant