Skip to content

Revert the rocprofiler-sdk finalize warning workaround - #516

Open
magaonka-amd wants to merge 1 commit into
ROCm:rocm-jax-infrafrom
magaonka-amd:cleanup/remove-rocprofiler-log-level-workaround
Open

magaonka-amd wants to merge 1 commit into
ROCm:rocm-jax-infrafrom
magaonka-amd:cleanup/remove-rocprofiler-log-level-workaround

Conversation

@magaonka-amd

@magaonka-amd magaonka-amd commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Reverts #514 (commit 431083f).

What

Removes ROCPROFILER_LOG_LEVEL=error and its TODO comment from
docker/Dockerfile.base-therock-ubu24. issue is fixed in rocprof-sdk and we no longer need it.

This reverts commit 431083f.

ROCPROFILER_LOG_LEVEL=error was set in the TheRock base image so that the
rocprofiler-sdk finalize warning stayed below the stderr threshold. Without
it, that warning broke upstream JAX tests which assert a subprocess wrote
nothing to stderr, e.g.
tests/logging_test.py::LoggingTest::test_subprocess_toggling_logging_level.

The SDK-side fix has since landed in ROCm, so the image no longer needs to
override the log level. Drop the override and the associated TODO so the
base image keeps the rocprofiler-sdk default logging behaviour.
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.

1 participant