-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
build: don't run test workflow on doc dir #37999
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might help a lot with the way test-macos gets very backed up.
I thought some add-on tests were constructed from the docs. Am I wrong? |
They are. Perhaps we can remove the change here from test-linux so they still run there, but keep the change to test-macos since that is frequently a bottleneck. |
Sgtm |
ci may take a little too long. |
Leaving it in the Linux workflow because addons tests are affected by changes to addons.md example code. So we need to keep that running somewhere for docs changes, but one platform seems sufficient. PR-URL: nodejs#37999 Reviewed-By: Rich Trott <rtrott@gmail.com>
Landed in f5eea17. I only landed the macOS change and left the current Linux workflow as-is based on the discussion above. We can always add an ignore paths directive for the Linux workflow at a later date. (I imagine it's possible to ignore-paths on everything except |
Leaving it in the Linux workflow because addons tests are affected by changes to addons.md example code. So we need to keep that running somewhere for docs changes, but one platform seems sufficient. PR-URL: #37999 Reviewed-By: Rich Trott <rtrott@gmail.com>
Leaving it in the Linux workflow because addons tests are affected by changes to addons.md example code. So we need to keep that running somewhere for docs changes, but one platform seems sufficient. PR-URL: #37999 Reviewed-By: Rich Trott <rtrott@gmail.com>
Ignore the
doc
directory when running test workflow.Checklist