Skip to content

Conversation

@metascroy
Copy link
Contributor

@metascroy metascroy commented Jul 2, 2025

Reverts #11357

This job is causing CI to fail because it takes too long and preventing viable/strict from updating. @winskuo-quic please re-land with higher timeout.

@metascroy metascroy requested a review from cccclai as a code owner July 2, 2025 16:11
@pytorch-bot pytorch-bot bot added the ci-no-td label Jul 2, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Jul 2, 2025

🔗 Helpful Links

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

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

❌ 2 New Failures, 1 Cancelled Job, 1 Pending, 2 Unrelated Failures

As of commit 0100df6 with merge base 5a4ef46 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOB - The following job was cancelled. Please retry:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

BROKEN TRUNK - The following job failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 2, 2025
@github-actions
Copy link

github-actions bot commented Jul 2, 2025

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@metascroy metascroy requested a review from winskuo-quic July 2, 2025 16:12
@metascroy metascroy merged commit 9554826 into main Jul 2, 2025
188 of 196 checks passed
@metascroy metascroy deleted the revert-11357-dev1/winskuo/ci_for_non_llm_ga branch July 2, 2025 17:45
@cccclai
Copy link
Contributor

cccclai commented Jul 2, 2025

Checked with @metascroy,

I think the operation gets canceled because it hits the timeout, which counts as a failure for the purpose of updating viabl/strict

@winskuo-quic maybe let's keep the original timeout config and see if it passes

BujSet pushed a commit to BujSet/executorch that referenced this pull request Jul 2, 2025
…#12166)

Reverts pytorch#11357

This job is causing CI to fail because it takes too long and preventing
viable/strict from updating. @winskuo-quic please re-land with higher
timeout.
Tanish2101 pushed a commit to Tanish2101/executorch that referenced this pull request Jul 9, 2025
…#12166)

Reverts pytorch#11357

This job is causing CI to fail because it takes too long and preventing
viable/strict from updating. @winskuo-quic please re-land with higher
timeout.
winskuo-quic added a commit to CodeLinaro/executorch that referenced this pull request Jul 16, 2025
winskuo-quic added a commit to CodeLinaro/executorch that referenced this pull request Jul 29, 2025
winskuo-quic added a commit to CodeLinaro/executorch that referenced this pull request Jul 29, 2025
cccclai pushed a commit that referenced this pull request Jul 29, 2025
#12536)

…(#12166)"

This reverts commit 9554826.

### Summary
[PLEASE REMOVE] See [CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests)
for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a `Fixes
#<issue-id>` line.

[PLEASE REMOVE] If this PR introduces a fix or feature that should be
the upcoming release notes, please add a "Release notes: <area>" label.
For a list of available release notes labels, check out
[CONTRIBUTING.md's Pull
Requests](https://github.com/pytorch/executorch/blob/main/CONTRIBUTING.md#pull-requests).

### Test plan
[PLEASE REMOVE] How did you test this PR? Please write down any manual
commands you used and note down tests that you have written if
applicable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants