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

server: TestStatusEngineStatsJson failed #95491

Closed
cockroach-teamcity opened this issue Jan 19, 2023 · 8 comments · Fixed by #100115
Closed

server: TestStatusEngineStatsJson failed #95491

cockroach-teamcity opened this issue Jan 19, 2023 · 8 comments · Fixed by #100115
Labels
A-observability-inf 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 Jan 19, 2023

server.TestStatusEngineStatsJson failed with artifacts on master @ 942b55ef3f329d2e5e8142c8fc5282ed56173ea7:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/04ff595e8b8a4cdf61532aa9937d7edf/logTestStatusEngineStatsJson2437800523
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:278: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/04ff595e8b8a4cdf61532aa9937d7edf/logTestStatusEngineStatsJson2437800523
--- FAIL: TestStatusEngineStatsJson (8.45s)
Help

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

/cc @cockroachdb/obs-inf-prs @cockroachdb/server

This test on roachdash | Improve this report!

Jira issue: CRDB-23546

@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 Jan 19, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Jan 19, 2023
@cockroach-teamcity
Copy link
Member Author

server.TestStatusEngineStatsJson failed with artifacts on master @ 1708ea4b2a2b36bb88c028b6db65b023b28a73cf:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/5dd3194da4351b03928fb98be247cd8e/logTestStatusEngineStatsJson1936360921
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:281: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/5dd3194da4351b03928fb98be247cd8e/logTestStatusEngineStatsJson1936360921
--- FAIL: TestStatusEngineStatsJson (7.24s)
Help

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

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

server.TestStatusEngineStatsJson failed with artifacts on master @ 284d9de2d12dc8b85c463b5b7654e0cb1f7c7dc7:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/290373a27074403e036851126b3225f9/logTestStatusEngineStatsJson1514256422
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:281: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/290373a27074403e036851126b3225f9/logTestStatusEngineStatsJson1514256422
--- FAIL: TestStatusEngineStatsJson (42.76s)
Help

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

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

server.TestStatusEngineStatsJson failed with artifacts on master @ 284d9de2d12dc8b85c463b5b7654e0cb1f7c7dc7:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/290373a27074403e036851126b3225f9/logTestStatusEngineStatsJson3122952835
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:281: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/290373a27074403e036851126b3225f9/logTestStatusEngineStatsJson3122952835
--- FAIL: TestStatusEngineStatsJson (28.70s)
Help

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

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

server.TestStatusEngineStatsJson failed with artifacts on master @ 494b909193267b9810f181187a9e57207d81f930:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/290373a27074403e036851126b3225f9/logTestStatusEngineStatsJson1597719429
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:281: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: Error while dialing connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/290373a27074403e036851126b3225f9/logTestStatusEngineStatsJson1597719429
--- FAIL: TestStatusEngineStatsJson (17.43s)
Help

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

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

server.TestStatusEngineStatsJson failed with artifacts on master @ 9aa4f3485c75397e9ce0edabbf22c6343e1a901a:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/8eac222af22ad63c16ed43335cd017c2/logTestStatusEngineStatsJson2471064280
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:281: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: error while dialing: connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: error while dialing: connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/8eac222af22ad63c16ed43335cd017c2/logTestStatusEngineStatsJson2471064280
--- FAIL: TestStatusEngineStatsJson (16.86s)
Help

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

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

server.TestStatusEngineStatsJson failed with artifacts on master @ 7074da619b850a279a70d6f43ffd1aac4cc5fe67:

=== RUN   TestStatusEngineStatsJson
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/74885ac1e7f972ae9e97608ed3fdb458/logTestStatusEngineStatsJson733538378
    test_log_scope.go:79: use -show-logs to present logs inline
    status_test.go:282: status: 503 Service Unavailable, content-type: application/json, body: {
          "error": "connection error: desc = \"transport: error while dialing: connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "code": 14,
          "message": "connection error: desc = \"transport: error while dialing: connection interrupted (did the remote node shut down or are there networking issues?)\"",
          "details": [
          ]
        }, error: <nil>
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/74885ac1e7f972ae9e97608ed3fdb458/logTestStatusEngineStatsJson733538378
--- FAIL: TestStatusEngineStatsJson (169.16s)
Help

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

Same failure on other branches

This test on roachdash | Improve this report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-observability-inf 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

Successfully merging a pull request may close this issue.

3 participants