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

server/debug: TestAdminDebugRedirect timed out #108246

Closed
rytaft opened this issue Aug 5, 2023 · 2 comments
Closed

server/debug: TestAdminDebugRedirect timed out #108246

rytaft opened this issue Aug 5, 2023 · 2 comments
Assignees
@ericharmeling
Labels
A-observability-inf C-test-failure Broken test (automatically or manually discovered).

Comments

@rytaft
Copy link
Collaborator

rytaft commented Aug 5, 2023 •
edited by cockroach-jira-scripts
Loading

See https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_BazelEssentialCi/11200270?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildProblemsSection=true&expandBuildChangesSection=true&expandBuildTestsSection=true

cc @knz

Jira issue: CRDB-30381
@rytaft rytaft added the C-test-failure Broken test (automatically or manually discovered). label Aug 5, 2023
@blathers-crl blathers-crl bot added the T-server-and-security DB Server & Security label Aug 5, 2023
@rytaft rytaft mentioned this issue Aug 5, 2023
Merged
@exalate-issue-sync exalate-issue-sync bot added T-observability-inf and removed T-server-and-security DB Server & Security labels Aug 18, 2023
@ericharmeling ericharmeling self-assigned this Aug 22, 2023
@ericharmeling
Copy link
Contributor

ericharmeling commented Aug 22, 2023 •
edited
Loading

I have been unable to reproduce this failure on gceworker with a number of different test configurations.

This timeout might have something to do with the brief machine type switch for TC unit tests. A lot of tests were timing out after the switch from t2d-standard-48 to c2-standard-60 (see background slack thread), and this test was running on that new machine type when it failed.

We have since switched back to using t2d-standard-48, so I don't expect this timeout to occur again. It's also worth noting that the last time this test failed was in 2017, and I don't believe it's failed but this once since then.

@ericharmeling
Copy link
Contributor

Going to close this for now, with the explanation given above. If this test flakes again, we can do a more in-depth investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ericharmeling ericharmeling

Labels
A-observability-inf C-test-failure Broken test (automatically or manually discovered).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rytaft @ericharmeling