Skip to content

Conversation

@clee2000
Copy link
Contributor

@clee2000 clee2000 commented Oct 8, 2024

The branch hasn't been updated in 8 months, and it's using a weird version of the viable strict update that I want to get rid of

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 8, 2024

🔗 Helpful Links

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

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

❌ 7 New Failures, 1 Unrelated Failure

As of commit 9c6d14e with merge base f0ed07d (image):

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following job failed but were 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.

@clee2000 clee2000 requested review from a team and NicolasHug October 8, 2024 21:46
clee2000 added a commit to pytorch/test-infra that referenced this pull request Oct 9, 2024
I discovered that you don't actually have to check out the test-infra
repository because it's already there?

Docs:
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables#default-environment-variables

Only available for composite actions unfortunately

Testing:
https://github.com/pytorch/pytorch/actions/runs/11225822033?pr=137454
(actual pushing is commented out)

There are also two fetch_latest_green_commit.py scripts in test-infra so
I merged them and chose the location in tools/scripts. The logic between
the two is pretty much the same. gitutils was copied from
.github/scripts (but we don't need much of it)

There's also a reusable workflow update-viablestrict and a composite
action update-viablestrict. The composite action is usually used, but
there are some differences between the two, and vision uses the reusable
workflow so I can't get rid of it just yet. (idk how much they care tho,
I don't vision has succeeded updating viable/strict in a while). I also
can't just make the reusable action call the composite action since the
workflow uses an ssh key to check out but the action uses a token

---

If pytorch/vision#8676 gets merged, I'll remove
the reusable workflow
Copy link
Member

@NicolasHug NicolasHug left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trusting you on this @clee2000

@NicolasHug NicolasHug merged commit 0534b6e into main Oct 11, 2024
70 of 84 checks passed
@NicolasHug NicolasHug deleted the csl/remove_viable_strict branch October 11, 2024 11:19
@github-actions
Copy link

Hey @NicolasHug!

You merged this PR, but no labels were added.
The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

@clee2000 clee2000 added the other if you have no clue or if you will manually handle the PR in the release notes label Oct 11, 2024
clee2000 added a commit to pytorch/test-infra that referenced this pull request Oct 17, 2024
Only used in pytorch/vision, which was removed in
pytorch/vision#8676

The composite action version still exists
facebook-github-bot pushed a commit that referenced this pull request Jan 13, 2025
Reviewed By: vmoens

Differential Revision: D68021981

fbshipit-source-id: 41fb238fc098c76a4ddd4c76cf49bda37bb93ce6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed other if you have no clue or if you will manually handle the PR in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants