Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/140614
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 1 Unrelated FailureAs of commit 8f911c4 with merge base e52a534 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot merge -r |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
2acb323 to
7084e46
Compare
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: trunk / libtorch-linux-focal-cuda12.4-py3.7-gcc9-debug / build Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
7084e46 to
81f8824
Compare
81f8824 to
8085be3
Compare
removes sccache from bazel builds. Will move bazel builds to periodic if build succeed CUDA bazel test succeeded, moving to periodic Pull Request resolved: #142241 Approved by: https://github.com/malfet
|
@pytorchbot rebase |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
8085be3 to
dd31785
Compare
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
8986e22 to
e4f4f36
Compare
|
@pytorchbot merge -f "All builds are green" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Follow up of TODO in #140614 It was found experimentally, that for one GPU architecture, `sccache` passes `-E` as 1st, 2nd or 3rd argument, but it's much better to do this if `-E` is passed as any argument No need to worry about exit or elif chains, as `exec` aborts script execution Pull Request resolved: #142813 Approved by: https://github.com/malfet Co-authored-by: Nikita Shulga <nshulga@meta.com>
|
Does this mean that for |
|
@pytorchmergebot revert -c nosignal -m "Some build jobs are timing out, I'm guessing because they aren't using the cache. GH job link HUD commit link" |
|
@pytorchbot successfully started a revert job. Check the current status here. |
Reverting PR 140614 failedReason: Command Details for Dev Infra teamRaised by workflow job |
|
@ZainRizvi yes, but that was already like that, sccache doesn't play nicely with the preprocessor. |
Those timeouts have resolved itself.. |
Instead of an ancient prebuilt binary
This is a followup from #121323
For some reason, newer
sccachedoes not work whengccis invoked with-Eoption, so one have to special-case-Ecase in/opt/ccache/bin/gccwrapper, which had to be special cased to work withnvccby checking whether-Eis passed not only as first or second, but as 3rd argument as well(to be followed up by a generic #142813 ), i.e. to generate following wrapper:Without it
sccache nvcc hello.cufailed with no-descriptive