-
Notifications
You must be signed in to change notification settings - Fork 2k
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
gh-actions: release-tests: do not run linters for release tests #16379
gh-actions: release-tests: do not run linters for release tests #16379
Conversation
See https://github.com/miri64/RIOT/actions/runs/777070704 |
Oops, |
that's what we want, right? |
Yepp, sorry for not being clear on that :-). |
Then please squash! :) |
9a27c77
to
14d3cba
Compare
Squashed |
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.
ACK.
Backport provided in #16380 |
Contribution description
The release tests are marked as failing currenty since there is a bug in
pylint
(or one of its libraries). There is not much sense to run the linter for the release tests on the test scripts, as this is already done in the CI of the release tests. As such, we only need to run the test environment oftox
, which executes the release tests.Testing procedure
I'll run the workflow in my fork, just to see if everything works (to shorten the runtime a REMOVE ME commit is included).
Issues/PRs references
See RIOT-OS/Release-Specs#213 (comment)