Skip to content

Conversation

huydhn
Copy link
Contributor

@huydhn huydhn commented Jun 22, 2024

The first shard is very close to 3.5h and timeout sometimes now https://hud.pytorch.org/pytorch/pytorch/commit/1c75ddff3576a0bd7ed664476c49020c35875ab5#26540310592

@huydhn huydhn requested a review from clee2000 June 22, 2024 05:21
@huydhn huydhn requested a review from a team as a code owner June 22, 2024 05:21
Copy link

pytorch-bot bot commented Jun 22, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/129299

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 0ce71a0 with merge base 7373492 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Jun 22, 2024
@huydhn huydhn changed the title Add one more shards for CPU jobs Add one more shard for CPU jobs Jun 22, 2024
@huydhn
Copy link
Contributor Author

huydhn commented Jun 26, 2024

@pytorchbot merge -f 'Lint has passed, no need to run trunk jobs with this CI-only tweak'

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@huydhn huydhn deleted the add-more-cpu-shards branch December 4, 2024 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants