-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Return custom exit code to indicate known shm leak failure in L0_backend_python bls test #7485
Conversation
@@ -151,7 +151,7 @@ apt-get update && apt-get -y install \ | |||
libboost-dev | |||
rm -f /usr/bin/python3 && \ | |||
ln -s "/usr/bin/python3.${PYTHON_ENV_VERSION}" /usr/bin/python3 | |||
pip3 install --upgrade install requests numpy virtualenv protobuf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice find 🚀
qa/common/shm_util.py
Outdated
@@ -441,6 +441,9 @@ def __exit__(self, type, value, traceback): | |||
print( | |||
f"Shared memory leak detected [{shm_region}]: {curr_shm_free_size} (curr free) < {prev_shm_free_size} (prev free)." | |||
) | |||
# Known shared memory leak of 480 bytes in BLS test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have any ticket to eventually find/resolve this issue all together? Would be good to leave the FIXME DLIS-XXXX
here if so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call, added the ticket reference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a minor comment on ticket reference
What does the PR do?
Return custom exit code
123
to indicate known shm leak failure in L0_backend_python bls test. CI will catch the custom exit code and allow the L0_backend_python test to fail if the known issues occur.In order to propagate the exit code correctly, Python unittest and Pytest can not be used at the same time. In this PR, the
python_unittest.py
is replaced withtest_infer_shm_leak.py
which uses Pytest directly.Checklist
<commit_type>: <Title>
Commit Type:
Check the conventional commit type
box here and add the label to the github PR.
Related PRs:
tritonserver MR !236.
Where should the reviewer start?
Test plan:
L0_backend_python should fail with
allowed to fail
if it's failing due to the known shm leak from bls sub test.Caveats:
Background
Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)