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

testutils/lint: TestLint failed #86926

Closed
cockroach-teamcity opened this issue Aug 26, 2022 · 6 comments
Closed

testutils/lint: TestLint failed #86926

cockroach-teamcity opened this issue Aug 26, 2022 · 6 comments
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot.
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Aug 26, 2022

testutils/lint.TestLint failed with artifacts on master @ 5c0af43059fba81d2f146923f724694c106cc5d9:

=== RUN   TestLint
--- FAIL: TestLint (1089.35s)
=== RUN   TestLint/TestStaticCheck
    lint_test.go:1773: 
        pkg/sql/copy.go:433:8: const copyBatchRowSize is unused (U1000)
    --- FAIL: TestLint/TestStaticCheck (884.23s)

Parameters: GOFLAGS=-json

Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-19038

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. labels Aug 26, 2022
@cockroach-teamcity cockroach-teamcity added this to the 22.2 milestone Aug 26, 2022
@cucaroach
Copy link
Contributor

I'm so confused, that line of code doesn't contain that variable on master but it does at that SHA. I have no idea what to do with this...

@srosenberg
Copy link
Member

It was trigged by this build [1] manually? The changes are not yet in master.

[1] https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_UnitTests/6246057

@cucaroach
Copy link
Contributor

Still confused, that commit even has old/wrong commit notes:

    Release note (sql change): COPY FROM operations are now atomic by
    default instead of being segmented into 100 row transactions. Setting
    the sql.copyfrom.atomic cluster setting to false to get the old
    behavior.

On master its:

    Release note (backward-incompatible change): COPY FROM operations are
    now atomic by default instead of being segmented into 100 row
    transactions. Set the copy_from_atomic_enabled session setting to
    false to get the old behavior.

Its like bors constructed a merge node with an older version of my PR or something?

@srosenberg
Copy link
Member

Its like bors constructed a merge node with an older version of my PR or something?

That's likely what happened. Bors uses a workaround [1] which first creates staging.tmp (with master and PRs), then copies it over to staging. Technically, staging.tmp shouldn't trigger CI, but it does sometimes [2]. It might be worth checking with #dev-inf if this is a known issue.

[1] https://forum.bors.tech/t/what-is-the-staging-tmp-branch-used-for/65
[2] https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_UnitTests?branch=staging.tmp

@yuzefovich
Copy link
Member

This was fixed in #85704.

@cucaroach
Copy link
Contributor

Okay so one mystery solved, thanks @yuzefovich, although gotta wonder what's up with the linter and why didn't it fire on my PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot.
Projects
None yet
Development

No branches or pull requests

4 participants