Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: always run aggregate unit test check #34903

Merged
merged 2 commits into from
Jun 4, 2024

Conversation

kdmccormick
Copy link
Member

@kdmccormick kdmccormick commented Jun 3, 2024

When a shard of unit-tests.yml fails, we want the success job to bemaked "Failed" (not "Skipped"). That's because "Failed" blocks the PR from merging, whereas "Skipped" does not. This change ensures thatsuccess always runs to completion rather than being cancelled as soon as a unit test shard fails or is cancelled.

From https://github.com/marketplace/actions/alls-green#options:

Important: For this to work properly, it is a must to have the job always run,
otherwise GitHub will make it skipped when any of the dependencies fail. In
some contexts, skipped is interpreted as success which may lead to undersired,
unobvious and even dangerous (as in security breach "dangerous") side-effects.

Closes #34789

When a shard of unit-tests.yml fails, we want the `success` job to be
maked "Failed" (not "Skipped"). That's because "Failed" blocks the PR
from merging, whereas "Skipped" does not. This change ensures that
`success` always runs to completion rather than being cancelled as soon
as a unit test shard fails or is cancelled.

From https://github.com/marketplace/actions/alls-green#options:

> Important: For this to work properly, it is a must to have the job always run,
> otherwise GitHub will make it skipped when any of the dependencies fail. In
> some contexts, skipped is interpreted as success which may lead to undersired,
> unobvious and even dangerous (as in security breach "dangerous") side-effects.

Closes #34789
@kdmccormick kdmccormick merged commit b063dfc into master Jun 4, 2024
40 checks passed
@kdmccormick kdmccormick deleted the kdmccormick/aggregate-always branch June 4, 2024 14:15
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix edx-platform required checks
3 participants