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.

Sign up for GitHub

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

Jump to bottom

: failed #107909

Closed
cockroach-teamcity opened this issue Jul 31, 2023 · 4 comments
Closed

: failed #107909

cockroach-teamcity opened this issue Jul 31, 2023 · 4 comments
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. T-testeng TestEng Team
Milestone
23.2

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jul 31, 2023 •
edited by cockroach-jira-scripts
Loading

. failed with artifacts on master @ b27094b0ded0d37a56d3e8dd31e2e02514ee0eff:

stdout: 
, stderr:

Parameters: TAGS=bazel,gss , stress=true

Help

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

Same failure on other branches

/cc @cockroachdb/test-eng

This test on roachdash | Improve this report!

Jira issue: CRDB-30256
@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. T-testeng TestEng Team labels Jul 31, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone Jul 31, 2023
@cockroach-teamcity
Copy link
Member Author

. failed with artifacts on master @ b27094b0ded0d37a56d3e8dd31e2e02514ee0eff:

stdout: 
, stderr:

Parameters: TAGS=bazel,gss , stress=true

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@renatolabs renatolabs mentioned this issue Jul 31, 2023
Merged
@cockroach-teamcity
Copy link
Member Author

. failed with artifacts on master @ 37e61e9e245ac623b461e7917761c27d0223f1bb:

stdout: 
, stderr:

Parameters: TAGS=bazel,gss , stress=true

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

. failed with artifacts on master @ 37e61e9e245ac623b461e7917761c27d0223f1bb:

stdout: 
, stderr:

Parameters: TAGS=bazel,gss , stress=true

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@andyyang890
Copy link
Collaborator

Sorry for the noise, I messed up the TeamCity configuration for stressing a unit test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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. T-testeng TestEng Team
Projects
None yet
Milestone
23.2
Development

No branches or pull requests
2 participants
@cockroach-teamcity @andyyang890