ci: Move linter task to cirrus#20658
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
52b724e to
01b652a
Compare
dhruv
left a comment
There was a problem hiding this comment.
Comments addressed. Ready for re-review.
01b652a to
38baea1
Compare
38baea1 to
739d390
Compare
|
Concept ACK. |
|
ACK 739d390 |
|
Ready for re-review. |
| << : *BASE_TEMPLATE | ||
| container: | ||
| image: ubuntu:bionic # For python 3.6, oldest supported version according to doc/dependencies.md | ||
| cpu: 1 # Cut bill in half for linting |
There was a problem hiding this comment.
No need for that comment. Can remove or just say 1 is sufficient
| cpu: 1 # Cut bill in half for linting | |
| cpu: 1 |
| cpu: 1 # Cut bill in half for linting | |
| cpu: 1 # No need for more CPUs |
There was a problem hiding this comment.
btw, based on this plot https://cirrus-ci.com/task/4624095184683008
memory can also be set to 1
|
ACK 4045a67 |
|
On my personal account having some "fatal: Not a valid object name master" warnings: |
|
Also in the merge commit, https://cirrus-ci.com/task/6086189209878528?command=lint#L50: |
|
Missing packages are installed in #20682 |
|
Thanks for catching those, @hebasto. I should've looked closer. |
3c2478c ci: Print COMMIT_RANGE to the log as it was in Travis CI (Hennadii Stepanov) c123892 ci: Drop Travis-specific workaround for shellcheck (Hennadii Stepanov) 10af252 ci: Drop Travis-specific way to set COMMIT_RANGE variable (Hennadii Stepanov) 93504da ci: Fix COMMIT_RANGE variable value for PRs (Hennadii Stepanov) Pull request description: This PR: - is a #20658 and #20682 followup - set the `COMMIT_RANGE` variable correctly for PRs - cleans up Travis-specific code - prints COMMIT_RANGE value to the log for convenience as it was in Travis CI ACKs for top commit: MarcoFalke: ACK 3c2478c Tree-SHA512: beb933352b10fd5eb3e66373ddb62439e4f3a03b50fb037ee89fa92c0706cec41d05f2d307f15bb18d1e634e6464f4e123b7e2f88703c8edfd145d8d6eff0b1a
3c2478c ci: Print COMMIT_RANGE to the log as it was in Travis CI (Hennadii Stepanov) c123892 ci: Drop Travis-specific workaround for shellcheck (Hennadii Stepanov) 10af252 ci: Drop Travis-specific way to set COMMIT_RANGE variable (Hennadii Stepanov) 93504da ci: Fix COMMIT_RANGE variable value for PRs (Hennadii Stepanov) Pull request description: This PR: - is a bitcoin#20658 and bitcoin#20682 followup - set the `COMMIT_RANGE` variable correctly for PRs - cleans up Travis-specific code - prints COMMIT_RANGE value to the log for convenience as it was in Travis CI ACKs for top commit: MarcoFalke: ACK 3c2478c Tree-SHA512: beb933352b10fd5eb3e66373ddb62439e4f3a03b50fb037ee89fa92c0706cec41d05f2d307f15bb18d1e634e6464f4e123b7e2f88703c8edfd145d8d6eff0b1a
Solves #20467: Move linter to Cirrus-CI as Travis-CI.org is shutting down