-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: sqlsmith/setup=empty/setting=no-ddl failed #92505
Labels
branch-release-22.1
Used to mark GA and release blockers, technical advisories, and bugs for 22.1
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
T-sql-queries
SQL Queries Team
Milestone
Comments
cockroach-teamcity
added
branch-release-22.1
Used to mark GA and release blockers, technical advisories, and bugs for 22.1
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
labels
Nov 26, 2022
There are no obvious culprits among the queries that ran or memory/cpu usage. It seems likely that there were some network latency/connectivity issues. Possibly related to #91771? Seeing lines like
and node 4 didn't even make it into the logs.
|
I'll close this as a dup of #92557 for now, since it seems likely they have a common cause that will be fixed soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
branch-release-22.1
Used to mark GA and release blockers, technical advisories, and bugs for 22.1
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
T-sql-queries
SQL Queries Team
roachtest.sqlsmith/setup=empty/setting=no-ddl failed with artifacts on release-22.1 @ 6b3f19ae0f6f47bb606d47a07fd5e0f8a80e4fe8:
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-21818
The text was updated successfully, but these errors were encountered: