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

run go.mod tidy - drop compat with 1.16 #12911

Merged
merged 1 commit into from May 4, 2022

Conversation

dprotaso
Copy link
Member

@dprotaso dprotaso commented May 4, 2022

go mod tidy -go=1.16 && go mod tidy -go=1.17
then
go mod tidy -compat=1.17

This was causing our downstream-test in knative.dev/pkg to fail
since go mod tidy was exiting with an error code 1

Example output

knative.dev/serving/pkg/queue imports
        github.com/prometheus/client_golang/prometheus imports
        github.com/prometheus/procfs loaded from github.com/prometheus/procfs@v0.6.0,
        but go 1.16 would select v0.7.3
knative.dev/serving/cmd/activator imports
        go.uber.org/zap tested by
        go.uber.org/zap.test imports
        go.uber.org/goleak loaded from go.uber.org/goleak@v1.1.11-0.20210813005559-691160354723,
        but go 1.16 would select v1.1.12
knative.dev/serving/pkg/queue imports
        github.com/prometheus/client_golang/prometheus imports
        github.com/prometheus/procfs imports
        github.com/prometheus/procfs/internal/fs loaded from github.com/prometheus/procfs@v0.6.0,
        but go 1.16 would select v0.7.3
knative.dev/serving/pkg/queue imports
        github.com/prometheus/client_golang/prometheus imports
        github.com/prometheus/procfs imports
        github.com/prometheus/procfs/internal/util loaded from github.com/prometheus/procfs@v0.6.0,
        but go 1.16 would select v0.7.3
knative.dev/serving/cmd/activator imports
        go.uber.org/zap tested by
        go.uber.org/zap.test imports
        go.uber.org/goleak imports
        go.uber.org/goleak/internal/stack loaded from go.uber.org/goleak@v1.1.11-0.20210813005559-691160354723,
        but go 1.16 would select v1.1.12
knative.dev/serving/hack imports
        github.com/tsenart/vegeta/v12 imports
        github.com/tsenart/vegeta/v12/internal/resolver tested by
        github.com/tsenart/vegeta/v12/internal/resolver.test imports
        github.com/miekg/dns loaded from github.com/miekg/dns@v1.1.35,
        but go 1.16 would select v1.1.41

go mod tidy -go=1.16 && go mod tidy -go=1.17
then
go mod tidy -compat=1.17

This was causing our downstream-test in knative.dev/pkg to fail
since go mod tidy was existing with an error code 1

Example output
```
knative.dev/serving/pkg/queue imports
        github.com/prometheus/client_golang/prometheus imports
        github.com/prometheus/procfs loaded from github.com/prometheus/procfs@v0.6.0,
        but go 1.16 would select v0.7.3
knative.dev/serving/cmd/activator imports
        go.uber.org/zap tested by
        go.uber.org/zap.test imports
        go.uber.org/goleak loaded from go.uber.org/goleak@v1.1.11-0.20210813005559-691160354723,
        but go 1.16 would select v1.1.12
knative.dev/serving/pkg/queue imports
        github.com/prometheus/client_golang/prometheus imports
        github.com/prometheus/procfs imports
        github.com/prometheus/procfs/internal/fs loaded from github.com/prometheus/procfs@v0.6.0,
        but go 1.16 would select v0.7.3
knative.dev/serving/pkg/queue imports
        github.com/prometheus/client_golang/prometheus imports
        github.com/prometheus/procfs imports
        github.com/prometheus/procfs/internal/util loaded from github.com/prometheus/procfs@v0.6.0,
        but go 1.16 would select v0.7.3
knative.dev/serving/cmd/activator imports
        go.uber.org/zap tested by
        go.uber.org/zap.test imports
        go.uber.org/goleak imports
        go.uber.org/goleak/internal/stack loaded from go.uber.org/goleak@v1.1.11-0.20210813005559-691160354723,
        but go 1.16 would select v1.1.12
knative.dev/serving/hack imports
        github.com/tsenart/vegeta/v12 imports
        github.com/tsenart/vegeta/v12/internal/resolver tested by
        github.com/tsenart/vegeta/v12/internal/resolver.test imports
        github.com/miekg/dns loaded from github.com/miekg/dns@v1.1.35,
        but go 1.16 would select v1.1.41
```
@knative-prow knative-prow bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label May 4, 2022
@knative-prow
Copy link

knative-prow bot commented May 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 4, 2022
@dprotaso
Copy link
Member Author

dprotaso commented May 4, 2022

/hold

surprised to see a fixtures.ttar - wonder if that's a test fixture that's leaking

@knative-prow knative-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 4, 2022
@codecov
Copy link

codecov bot commented May 4, 2022

Codecov Report

Merging #12911 (53a3405) into main (061be9e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #12911   +/-   ##
=======================================
  Coverage   87.04%   87.04%           
=======================================
  Files         197      197           
  Lines       14437    14437           
=======================================
  Hits        12567    12567           
  Misses       1576     1576           
  Partials      294      294           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 061be9e...53a3405. Read the comment docs.

@dprotaso
Copy link
Member Author

dprotaso commented May 4, 2022

Removed it here: prometheus/procfs#447

in the meantime
/hold cancel

@knative-prow knative-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 4, 2022
@nader-ziada
Copy link
Member

Removed it here: prometheus/procfs#447

do you need to wait for that?

@nader-ziada
Copy link
Member

/lgtm

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label May 4, 2022
@knative-prow knative-prow bot merged commit 9dc1baa into knative:main May 4, 2022
@dprotaso dprotaso deleted the go-mod-1-17-compat branch May 4, 2022 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants