fix: respect OSS_FUZZ_CONTAINER_ORG environment variable #269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes a bug in the common module where the
OSS_FUZZ_CONTAINER_ORG
environment variable was not being respected, causing test failures when using alternative container registries.Problem
The
oss_fuzz_container_org
property inchallenge_task.py
was hardcoded to always parse the organization from the helper_path file, ignoring theOSS_FUZZ_CONTAINER_ORG
environment variable that should take precedence.Solution
Added a check to respect the
OSS_FUZZ_CONTAINER_ORG
environment variable before falling back to parsing the helper_path file:Impact
This fix allows tests and development environments to use alternative container registries (e.g., for testing with local or private registries) by setting the
OSS_FUZZ_CONTAINER_ORG
environment variable.Testing
Related
See #270 for separate issue tracking the patcher integration test redesign needs.