-
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
sql/tests: TestRandomSyntaxFunctions failed #107237
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-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Milestone
Comments
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-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
labels
Jul 20, 2023
This was referenced Jul 21, 2023
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ 4af7886e1be69d85c0c6b4a9d355a1e03fff8074: Fatal error:
Stack:
Log preceding fatal error
Same failure on other branches
|
craig bot
pushed a commit
that referenced
this issue
Jul 24, 2023
107444: issues: use prefix match to check for existing issue r=renatolabs,tbg a=rafiss It is conventional to annotate a test failure issue title with some additional information about the failure cause. The previous logic was too strict in requiring an exact title match. Now it will match as long as the title matches exactly OR if the prefix matches and is followed by whitespace. Example: I added a suffix to [`sql/tests: TestRandomSyntaxFunctions failed [panic in request_job_execution_details]`](#106970) since the issue was with a function the jobs team added. But the next day #107237 was opened anew. This PR would prevent that from happening. Epic: None Release note: None Co-authored-by: Rafi Shamim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ c6f4c0ed6e39ec4795755b8b477e6cac0abf818f:
Fatal error:
Stack:
Log preceding fatal error
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-29955
The text was updated successfully, but these errors were encountered: