Skip to content

Added edge case checking in isGreen#79565

Closed
swang392 wants to merge 5 commits intopytorch:masterfrom
swang392:isgreen-edgecase
Closed

Added edge case checking in isGreen#79565
swang392 wants to merge 5 commits intopytorch:masterfrom
swang392:isgreen-edgecase

Conversation

@swang392
Copy link
Copy Markdown
Contributor

@swang392 swang392 commented Jun 14, 2022

Relates to #76700

Overview: One edge case not accounted for in the original logic of isGreen was for commits with no workflow checks. Similarly, if any of the required checks are not present (ex: if all of the pull checks are skipped), the workflow should not be promoteble. A commit should only be promoteable if there is it least one workflow check from each required group present (i.e. none of them are skipped)

Test Plan: Verify that commits on the HUD with no workflow checks are not considered promote-able. Added a test case with no workflows in test_print_latest_commits.py

@swang392 swang392 requested a review from a team as a code owner June 14, 2022 21:26
@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Jun 14, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit d97717c (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

Comment thread .github/scripts/print_latest_commits.py Outdated
@swang392
Copy link
Copy Markdown
Contributor Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot successfully started a rebase job. Check the current status here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Successfully rebased isgreen-edgecase onto refs/remotes/origin/master, please pull locally before adding more changes (for example, via git checkout isgreen-edgecase && git pull --rebase)

@swang392
Copy link
Copy Markdown
Contributor Author

@pytorchbot merge -f

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link
Copy Markdown
Contributor

Hey @swang392.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

Comment thread .github/scripts/print_latest_commits.py Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The move may be to move this back to a local variable under isGreen as this dictionary changes now.

Comment thread .github/scripts/print_latest_commits.py Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Once you move the dictionary in here, this should no longer be necessary

Comment thread .github/scripts/print_latest_commits.py Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Would be good to print a join of the regexes here for better debugging

@swang392 swang392 reopened this Jun 15, 2022
@swang392 swang392 closed this Jun 15, 2022
facebook-github-bot pushed a commit that referenced this pull request Jun 20, 2022
Summary:
Relates to #76700

**Overview**: One edge case not accounted for in the original logic of `isGreen` was for commits with no workflow checks. Similarly, if any of the required checks are not present (ex: if all of the pull checks are skipped), the workflow should not be promoteble. A commit should only be promoteable if there is it least one workflow check from each required group present (i.e. none of them are skipped)

**Test Plan:** Verify that commits on the HUD with no workflow checks are not considered promote-able. Added a test case with no workflows in `test_print_latest_commits.py`

Pull Request resolved: #79565
Approved by: https://github.com/seemethere

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/6015987dc387b3703c0e148fe67230f258125ed4

Reviewed By: malfet

Differential Revision: D37208283

Pulled By: swang392

fbshipit-source-id: 9b6b5006f576e3a6ad9696143c2e685e5f48c7c5
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 25, 2026
Relates to pytorch#76700

**Overview**: One edge case not accounted for in the original logic of `isGreen` was for commits with no workflow checks. Similarly, if any of the required checks are not present (ex: if all of the pull checks are skipped), the workflow should not be promoteble. A commit should only be promoteable if there is it least one workflow check from each required group present (i.e. none of them are skipped)

**Test Plan:** Verify that commits on the HUD with no workflow checks are not considered promote-able. Added a test case with no workflows in `test_print_latest_commits.py`
Pull Request resolved: pytorch#79565
Approved by: https://github.com/seemethere
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.

5 participants