jobs: flake in TestRegistryLifecycle/rollback

[knz]

Found in https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_UnitTests/2178285?

------- Stdout: -------
=== RUN   TestRegistryLifecycle/rollback
--- FAIL: TestRegistryLifecycle/rollback (2.75s)
jobs_test.go:200: Starting resume
jobs_test.go:208: Exiting resume
jobs_test.go:200: Starting resume
jobs_test.go:208: Exiting resume
jobs_test.go:250: Starting success
jobs_test.go:254: Exiting success
jobs_test.go:200: Starting resume
jobs_test.go:648: expected job status: succeeded but got: running
jobs_test.go:208: Exiting resume

[blathers-crl]

Hi @knz, please add a C-ategory label to your issue. Check out the label system docs.

While you're here, please consider adding an A- label to help keep our repository tidy.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.}

[knz]

I'll add a commit to skip the test for the time being.

[spaskob]

make stress PKG=./pkg/jobs TESTFLAGS='-v ' TESTS=TestRegistryLifecycle/rollback
does not reproduce the flake locally

[spaskob]

make stress PKG=./pkg/jobs TESTFLAGS='-v ' TESTS=TestRegistryLifecycle
also does not reproduce the flake locally in >2000 runs.

[knz]

Have you tried the git SHA where the issue was found originally.

It's possible the root cause has been fixed on master already. If that is the case (i.e. you can repro in the past but not any more) it would be useful to determine which change was responsible.

[spaskob]

What would be that SHA? TC information is extremely hard to parse.

[knz]

What would be that SHA? TC information is extremely hard to parse.

You always have two differnt ways to identify this:

1. identify the PR that the build is coming from. The PR number is at the top left
   

   Then go to the PR, look at the history of the PR and find which build failed, and scan through the list of commit SHAs to find which one was used for the build.

2. or, go to the full test log like this:

   • Dependencies
     

   • Click the failed CI target, then click on the red failure message
     

   • Click "download log" at the top right
     

   • The SHA is at the top