Skip to content
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

ci: Install missing lint packages #20682

Merged
merged 1 commit into from
Dec 18, 2020
Merged

Conversation

maflcko
Copy link
Member

@maflcko maflcko commented Dec 17, 2020

The cirrus container is vanilla ubuntu, so we need to install the needed packages

Copy link
Member

@hebasto hebasto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Concept ACK fa63121

Sorry, but I don't see any reason in the recent push.

Also I'd suggest to separate COMMIT_RANGE related changes into their own commit, or--better--into a separated PR.

.cirrus.yml Outdated Show resolved Hide resolved
ci/lint/04_install.sh Outdated Show resolved Hide resolved
@maflcko
Copy link
Member Author

maflcko commented Dec 17, 2020

Sorry, but I don't see any reason in the recent push.

curl is used by the linters

@hebasto
Copy link
Member

hebasto commented Dec 17, 2020

Sorry, but I don't see any reason in the recent push.

curl is used by the linters

curl is already in apt install -y clang-format-9 python3-pip curl git :)

And wget is not used by the linters:

$ git grep -e 'wget' test/lint/ | wc -l
0

Also merge script into ci/lint_run_all.sh because env vars weren't
exported properly
@DrahtBot
Copy link
Contributor

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, 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.

@maflcko
Copy link
Member Author

maflcko commented Dec 18, 2020

Also I'd suggest to separate COMMIT_RANGE related changes into their own commit, or--better--into a separated PR.

Dropped here

Copy link
Member

@hebasto hebasto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK faeb40b, I have reviewed the code and it looks OK, I agree it can be merged.

@maflcko maflcko merged commit 20f4a94 into bitcoin:master Dec 18, 2020
@maflcko maflcko deleted the 2012-testDel branch December 18, 2020 08:55
@sheffine

This comment was marked as spam.

@hebasto
Copy link
Member

hebasto commented Dec 18, 2020

Also I'd suggest to separate COMMIT_RANGE related changes into their own commit, or--better--into a separated PR.

Dropped here

Mind looking into #20697 ?

sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Dec 18, 2020
faeb40b ci: Install missing lint packages (MarcoFalke)

Pull request description:

  The cirrus container is vanilla ubuntu, so we need to install the needed packages

ACKs for top commit:
  hebasto:
    ACK faeb40b, I have reviewed the code and it looks OK, I agree it can be merged.

Tree-SHA512: e56198108e26ea0ba2a344b1b74bc294652f34e9866cca053a25fb1b83bbd87ea40254c340e5e169fdfcbd4dcb39fdc2078b5157ca729a22a9a1792ec514a33e
maflcko pushed a commit that referenced this pull request Dec 21, 2020
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
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Dec 21, 2020
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
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Aug 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants