-
Notifications
You must be signed in to change notification settings - Fork 434
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
NOCOMMIT: log peak mem usage and swapouts to debug test-llava-runner #8192
Conversation
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8192
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 2 New FailuresAs of commit f3ec03c with merge base a3455d9 (): NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
initial run inconclusive (did not demonstrate swapping, but can't rule it out yet); there was a timestamp gap in the middle of the added log messages, but they were demonstrably all generated with a timestamp before the end of the gap. Adding another log message at what seems to be a better place and retrying. |
OK I think I'm satisfied that we're not swapping. https://github.com/pytorch/executorch/actions/runs/13144066347/job/36677928636?pr=8192 |
Attempting to test my theory that the timestamp gaps in #8180 are caused by swapping.