-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Fail early if output engine file path is unwritable in trtexec #4449
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
base: main
Are you sure you want to change the base?
Conversation
/blossom-ci |
/blossom-ci |
1 similar comment
/blossom-ci |
Hello @PierreMarieCurie thanks for your contribution! Can you target the main branch and have your commits rebase on that? |
7010618
to
0cd927d
Compare
Hello @poweiw, thanks for your feedback. I've rebased my branch onto main and updated the PR to target it. Let me know if there's anything else you'd like adjusted. |
Thanks Pierre for the fast response! I lost my permission to trigger the pipeline but should be able to run next week. Will lyk with the pipeline results. |
/blossom-ci |
…X parsing Signed-off-by: Paul Pacheco <[email protected]>
74de927
to
0392688
Compare
Hello @poweiw and @kevinch-nv, I messed up my rebase, sorry about that. The target branch was correct, but it was based on an old commit, so the pipeline failed. It should be fixed now. |
Hi NVIDIA team,
This PR adds an early check in trtexec to ensure the --saveEngine path is writable before starting ONNX parsing. It avoids unnecessary compute when the path is invalid. This a proposition to solve issue #4448.
It has only been tested on the following environment: Ubuntu 24.04 running as a Dev Container within WSL2.
Thanks!