-
Notifications
You must be signed in to change notification settings - Fork 145
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
[BUG]: TrainAEStage fails with a Segmentation fault #1641
Labels
bug
Something isn't working
Comments
This same bug exists for the pipelines documented in |
rapids-bot bot
pushed a commit
that referenced
this issue
Apr 19, 2024
* Ensure that both `pe_count` & `engines_per_pe` are both set to `1` for the C++ impl of the `TritonInferenceStage` * Remove hard-coded `--num_threads=1` from validation scripts * Disable hammah validation script until #1641 can be resolved * Back-port of #1636 Closes #1639 ## By Submitting this PR I confirm: - I am familiar with the [Contributing Guidelines](https://github.com/nv-morpheus/Morpheus/blob/main/docs/source/developer_guide/contributing.md). - When the PR is ready for review, new or existing tests cover these changes. - When the PR is ready for review, the documentation is up to date with these changes. Authors: - David Gardner (https://github.com/dagardner-nv) - Eli Fajardo (https://github.com/efajardo-nv) Approvers: - Michael Demoret (https://github.com/mdemoret-nv) URL: #1640
dagardner-nv
changed the title
[BUG]: hammah validation script failing with a Segmentation fault
[BUG]: TrainAEStage fails with a Segmentation fault
Apr 22, 2024
morpheus-bot-test
bot
moved this from Todo
to Review - Ready for Review
in Morpheus Boards
Sep 20, 2024
github-project-automation
bot
moved this from Review - Ready for Review
to Done
in Morpheus Boards
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
24.03
Which installation method(s) does this occur on?
Source
Describe the bug.
The validation script is failing, even though the equivalent unittest is passing.
Minimum reproducible example
Relevant log output
Click here to see error details
Full env printout
Click here to see environment details
Other/Misc.
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: