sql/tests: TestRandomSyntaxFunctions failed #108153
Assignees
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
This was referenced Aug 5, 2023
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ 695d4ec85157a4da0c97237e6f16bf919eebf6c5: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ f1623e0a2cffc81580ee3c3b71035efd854d89c9: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ f1623e0a2cffc81580ee3c3b71035efd854d89c9: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ 1382b26a97bf6f70a07d363dc319283c173359eb: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ a3a389e464defd3d301a0b080435cf33502a02d2: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ 6fa90e9e1003b0e0355c1ff42eb34b1b64ab36f2: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ 7da4ef5af83c38680c536e7c18a9db61274b9d25: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ 6b0f43a13c4d2b36b4da5961e523161dabe212c0: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ c13bf7633cbb416d9e43f8c57b1e309fab1110ce: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ abf61bbf38a990f938b56a80284a834e2d087ea1: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
|
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ e0de1f12d4f496fc7e4050a33e96f8c635c7a27c: Fatal error: Stack: Log preceding fatal error
Same failure on other branches
|
craig bot
pushed a commit
that referenced
this issue
Aug 17, 2023
…108925 107863: sql: add bitwise operation for varbit with variable length r=rharding6373 a=cty123 As raised in #107821, the existing bitwise operations in CRDB follow the same standard as Postgresql that require the two operands of varbit type to have the same length. The restriction makes it easier for the implementation but harder for users. As of today, we need to apply casting and left padding to make sure the operands have the same length. Instead, it might be useful to have CRDB built-in functions that can handle this. Here I have implemented 2 basic bitwise operation functions that are tailored for varbit typed data of arbitrary length. 108525: sql: TestRandomSyntaxFunctions: skip function call and fix CREATE STATS use of span after finish r=fqazi a=fqazi Previously, this test could depending on the concurrency, could spawn a large number of schema telemetry jobs via (ctdb_internal.create_sql_schema_telemetry_job). This could lead to contention that will eventually cause this test to time out. To address this, this patch limits calling the telemetry job creation function. Fixes: #108153 Release note: None 108807: server,log: report tenant names in logging output r=stevendanna,abargainier a=knz Epic: CRDB-27982 Fixes #103406. Prior to this change, the tenant details reported in logging output were limited to just the tenant ID. This is because the original tenant server initialization code only had access to the tenant ID (provided as CLI argument). Since recently, the tenant name is also becoming known during tenant server initialization. This is currently done via the tenant connector. This commit expands on this foundation by injecting the tenant name into the logging output as soon as it is available. For example: ``` I230815 19:31:07.290757 922 sql/temporary_schema.go:554 ⋮ [T4,Vblah,n1] 148 found 0 temporary schemas ^^^^^ here ``` or using JSON: ``` {"channel_numeric":0,"channel":"DEV",...,"tenant_id":4,"tenant_name":"blah",...} ^^^^^^^^^^^^^^^^^^^^ here ``` Note: we are choosing to report the tenant name *in addition* to the tenant ID to preserve compatibilit with automation (eg. logspy) which needs to filter entries based on ID. Release note (cluster virtualization): The name of the virtual cluster (tenant), when known, is now reported in logging events. Refer to the documentation of individual logging format for details. 108823: row: remove no longer nil txn check r=yuzefovich a=yuzefovich I believe this non-nil txn check is no longer needed as of 8f7f2f4 (which fixed the only known place where we forgot to set the txn field on the FlowCtx). Epic: None Release note: None 108858: *: bump some core dependencies r=knz a=rickystewart Unfortunately we're still getting `nogo` crashes. Try bumping these dependencies even further. Informs #99988. Epic: none Release note: None 108866: storage: Write sstables in v4 format for shared ingestions r=RaduBerinde a=itsbilal We require sstables to be written with obsolete bits for shared sstable ingestion to work correctly. This change moves to writing sstables with the new format if the cluster version is high enough. Unblocks #107394. Epic: none Release note: None 108886: kvstreamer, row: adjust all tests to work with the test tenant r=yuzefovich a=yuzefovich Epic: CRDB-18499 Informs #76378 Release note: None 108924: logictest: avoid FATAL during cleanup r=rafiss a=rafiss This prevents the test from failing if there is an error closing a connection at the end of the test. There is no strong need for us to assert that closing the connection worked. fixes #108833 Release note: None 108925: streamingest: speed-up c2c cutover r=lidorcarmel a=lidorcarmel Each c2c processor checks the job info table every 30 seconds to see whether a cutover has started. Normally a cutover should take about 10 seconds. This pr changes the default to 10 seconds, to reduce the total time for cutting over. Epic: none Release note: None Co-authored-by: cty123 <[email protected]> Co-authored-by: Faizan Qazi <[email protected]> Co-authored-by: Raphael 'kena' Poss <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Ricky Stewart <[email protected]> Co-authored-by: Bilal Akhtar <[email protected]> Co-authored-by: Rafi Shamim <[email protected]> Co-authored-by: Lidor Carmel <[email protected]>
fqazi
added a commit
to fqazi/cockroach
that referenced
this issue
Aug 18, 2023
Previously, this test could depending on the concurrency, could spawn a large number of schema telemetry jobs via (ctdb_internal.create_sql_schema_telemetry_job). This could lead to contention that will eventually cause this test to time out. To address this, this patch limits calling the telemetry job creation function. Fixes: cockroachdb#108153 Release note: None
fqazi
added a commit
to fqazi/cockroach
that referenced
this issue
Aug 18, 2023
Previously, this test could depending on the concurrency, could spawn a large number of schema telemetry jobs via (ctdb_internal.create_sql_schema_telemetry_job). This could lead to contention that will eventually cause this test to time out. To address this, this patch limits calling the telemetry job creation function. Fixes: cockroachdb#108153 Release note: None
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sql/tests.TestRandomSyntaxFunctions failed with artifacts on master @ d87a04bf528cf3d8f242ceb539451cd14aa7a3cf:
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-30332
The text was updated successfully, but these errors were encountered: