*: bunch of failures #109994
Labels
Milestone
Comments
cockroach-teamcity
added
branch-master
|
@rickystewart seems like these panics are still happening on master. |
|
. failed with artifacts on master @ 3fb3b588117a2f790ba9bd7fcc0b93874822b695: Same failure on other branches
|
|
. failed with artifacts on master @ b7840ea58fc6db38528e1b499a0357d8ca51501e: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: |
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ 397dc0b48ba959278c0ab9e0042bf5b78940b279: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
|
. failed with artifacts on master @ b5836a5b4ab6c4fe58ada6002eb8c56c4e35438e: Parameters: Same failure on other branches
|
healthy-pod
pushed a commit
to healthy-pod/cockroach
that referenced
this issue
Sep 9, 2023
By running under `-race`, the go command defines the `race` build tag for us [1]. Previously, we defined it under `TAGS` to let the issue poster know that this is a failure under `race` and indicate that in the issue. At the time, defining the tag twice didn't cause issues but after cockroachdb#109773, it led to build failures [2]. To reproduce locally: ``` bazel test -s --config=race pkg/util/ctxgroup:all --test_env=GOTRACEBACK=all --define gotags=bazel,gss,race ``` As a follow-up, we should find another way to let the issue poster know that a failure was running under `race`. [1] https://go.dev/doc/articles/race_detector#Excluding_Tests [2] cockroachdb#109994 (comment) Epic: none Release note: None
craig bot
pushed a commit
that referenced
this issue
Sep 11, 2023
108175: kvserver: unskip lease preferences during outage r=andrewbaptist a=kvoli Previously, `TestLeasePreferenceDuringOutage` would force replication queue processing of the test range, then assert that the range up-replicated and lease transferred to a preferred locality. This test was skipped, and two of the assumptions it relied on to pass were no longer true. After #85219, the replicate queue no longer re-processes replicas. Instead, the queue requeues replicas after processing, at the appropriate priority. This broke the test due to the replicate queue being disabled, making the re-queue a no-op. After #94023, the replicate queue no longer looked for lease transfers, after processing a replication action. Combined with #85219, the queue would now be guaranteed to not process both up-replication and lease transfers from a single enqueue. Update the test to not require a manual process, instead using a queue range filter, which allows tests which disable automatic replication, to still process filtered ranges via the various replica queues. Also, ensure that the non-stopped stores are considered live targets, after simulating an outage (bumping manual clocks, stopping servers) -- so that the expected up-replication, then lease transfer can proceed. Fixes: #88769 Release note: None 109432: cluster-ui: handle partial response errors on the database details page r=THardy98 a=THardy98 Part of: #102386 **Demos** (Note: these demos show this same logic applied to both the databases and database table pages as well): DB-Console - https://www.loom.com/share/5108dd655ad342f28323e72eaf68219c - https://www.loom.com/share/1973383dacd7494a84e10bf39e5b85a3 This change applies the same error handling ideas from #109245 to the database details page, enabling non-admin users to use the database details page and providing better transparency to data fetching issues. Errors encountered while fetching table details can be viewed via the tooltip provided by the `Caution` icon at the table's name. `unavailable` cells also provide a tooltip that displays the error impacting that exact cell. Release note (ui change): Non-admin users are able to use the database details page. 110292: c2c: use seperate spanConfigEventStreamSpec in the span config event stream r=stevendanna a=msbutler Previously, the spanConfigEventStream used a streamPartitionSpec, which contained a bunch of fields unecessary for span config streaming. This patch creates a new spanConfigEventStreamSpec which contains the fields only necessary for span config event streaming. Informs #109059 Release note: None 110309: teamcity-trigger: ensure that `race` tag is only passed once r=healthy-pod a=healthy-pod By running under `-race`, the go command defines the `race` build tag for us [1]. Previously, we defined it under `TAGS` to let the issue poster know that this is a failure under `race` and indicate that in the issue. At the time, defining the tag twice didn't cause issues but after #109773, it led to build failures [2]. To reproduce locally: ``` bazel test -s --config=race pkg/util/ctxgroup:all --test_env=GOTRACEBACK=all --define gotags=bazel,gss,race ``` As a follow-up, we should find another way to let the issue poster know that a failure was running under `race`. [1] https://go.dev/doc/articles/race_detector#Excluding_Tests [2] #109994 (comment) Epic: none Release note: None Co-authored-by: Austen McClernon <[email protected]> Co-authored-by: Thomas Hardy <[email protected]> Co-authored-by: Michael Butler <[email protected]> Co-authored-by: healthy-pod <[email protected]>
jlinder
removed
C-test-failure
|
Closing as dupe of #99988 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
. failed with artifacts on master @ 8ee0bc7e4391add8c3d8ec99cddf510f581b1a8f:
Parameters:
TAGS=bazel,gss,deadlock,stress=trueHelp
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-31207
The text was updated successfully, but these errors were encountered: