gh-actions: release-tests: do not run linters for release tests [backport 2021.04] #16380
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #16379
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)