Fix DYNAMIC_KERNEL_END tracer environment variable #324
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.
It looks like we added a python option to
run_hw_trace.py
to set limit to the number of kernels traced when mlperf was added. This option was overwriting any set DYNAMIC_KERNEL_END environment variable by default and setting it to 0. This PR allows the environment variable to be overwritten only if the-l
option is specified in the script (and does not overwrite by default).