cockroachdb / cockroachdb/cockroach

pkg/kv/kvserver/liveness/liveness_test_/liveness_test: pkg failed

Open
#174,765 3 comments 0 reactions 0 assignees View on GitHub
branch-master C-test-failure O-robot s390x-test-failure T-kv
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

pkg/kv/kvserver/liveness/liveness_test_/liveness_test.pkg [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsIbmCloudLinuxS390x_UnitTestsS390x/21501904?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsIbmCloudLinuxS390x_UnitTestsS390x/21501904?buildTab=artifacts#/) on master @ [ac07b321bb81d9cc26a252a361b2284eb718d9d8](https://github.com/cockroachdb/cockroach/commits/ac07b321bb81d9cc26a252a361b2284eb718d9d8):

```
Test binary potentially failed to execute because of bazel test timeout, init() issue, or some other error. Content:
```
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

/cc @cockroachlabs/test-eng

[Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Jira issue: CRDB-67968

Contributor guide

Open the contributing guide

Research direction

Start with the TeamCity build log and artifacts linked in the issue for pkg/kv/kvserver/liveness/liveness_test_/liveness_test on s390x. Investigate whether the test binary failed to execute because of a Bazel timeout, an init() issue, or another reported error; done means identifying and fixing the cause so the package test passes on that platform.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd, distributed-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.