[fr] change back vlog(2) to LOG(INFO) #142441
Conversation
Summary: Change log message for future execution back from VLOG(2) to LOG(INFO). This message is useful for Flight Recorder to verify that flight recorder dumps completed successfully (or not). Test Plan: Tested manually on a mast job and noted that the INFO message was as expected. Differential Revision: D66996439
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/142441
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (4 Unrelated Failures)As of commit 867391a with merge base 0f6bfc5 ( BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
pytorch-bot
bot
added
oncall: distributed
|
This pull request was exported from Phabricator. Differential Revision: D66996439 |
|
@c-p-i-o has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 jobs have failed, first few of them are: pull / linux-jammy-py3-clang12-executorch / build Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge -i |
Merge startedYour change will be merged while ignoring the following 4 checks: pull / linux-jammy-py3-clang12-executorch / build, pull / linux-focal-cuda11.8-py3.10-gcc9 / test (distributed, 2, 3, lf.linux.g4dn.12xlarge.nvidia.gpu), trunk / macos-py3-arm64 / test (default, 2, 3, macos-m1-stable, unstable), trunk / macos-py3-arm64 / test (default, 3, 3, macos-m1-stable, unstable) Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Summary: Change log message for future execution back from VLOG(2) to LOG(INFO). This message is useful for Flight Recorder to verify that flight recorder dumps completed successfully (or not). Test Plan: Tested manually on a mast job and noted that the INFO message was as expected. (meta only link: https://fburl.com/mlhub/iui2tpc9) ``` [trainer5]:I1208 10:21:00.772841 7528 ProcessGroupNCCL.cpp:1294] [PG ID 0 PG GUID 0(precheck) Rank 21] future is successfully executed for: Flight recorder dump in heartbeatMonitor ``` Differential Revision: D66996439 Pull Request resolved: pytorch#142441 Approved by: https://github.com/fduwjj
4 participants
Summary:
Change log message for future execution back from VLOG(2) to LOG(INFO).
This message is useful for Flight Recorder to verify that flight recorder dumps completed successfully (or not).
Test Plan: Tested manually on a mast job and noted that the INFO message was as expected.
(meta only link: https://fburl.com/mlhub/iui2tpc9)
Differential Revision: D66996439
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k