-
Notifications
You must be signed in to change notification settings - Fork 483
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
[BUG] Vale workflow randomly fail after check starts #6721
Comments
More info: https://github.com/opensearch-project/documentation-website/blob/main/.github/workflows/vale.yml#L19 https://github.com/opensearch-project/documentation-website/blob/main/.github/workflows/vale.yml#L22 |
More info:
|
When green:
|
Seems like legit failure as vale indeed find errors. |
The Vale GitHub action is unstable. It always comments on the PR with the errors, but it randomly fails some PRs and passes others, even though we have specified for it not to fail in 2 places (--no-exit flag and fail_on_error). We're OK with setting it to pass by default because it still leaves comments and we can direct contributors to those comments when reviewing the PR. Thanks! |
This bug should be fixed by Jan 16, 2023 or around, but for version 2.28.0 in Jul 4, 2023 it seems still not fixed, thus it seems better to mute the return status: At the moment we will just let reviewers inform the contributors on style changes based on the code comments. |
This is the vale github action workflow file we use: https://github.com/opensearch-project/documentation-website/blob/077f613230f332b86d880e929c7d8a52786e90c6/.github/workflows/vale.yml
Sometimes the checks are randomly failing like this:
https://github.com/opensearch-project/documentation-website/actions/runs/8350082188/job/22855709741?pr=6720
It was supposed to be running and ignore errors, but seems like the error is not caused by the action itself, need investigation.
Thanks.
The text was updated successfully, but these errors were encountered: