roachtest: activerecord failed #94211
Assignees
Labels
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
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 Dec 24, 2022
|
roachtest.activerecord failed with artifacts on master @ c4bde8b72cdd4016845ae70ef5162b3f11fab1fb: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ c4bde8b72cdd4016845ae70ef5162b3f11fab1fb: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 9c5375f6a7375724cdbcbaa0029ed97a230d7abe: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 0725273ac7f789ba8ed78aacaf73cc953ca47fe8: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 0725273ac7f789ba8ed78aacaf73cc953ca47fe8: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 1d7bd69205c2197ccac33df9e2e6d4ff8c0fdbcf: Parameters: Same failure on other branches
|
rafiss
removed
the
release-blocker
|
roachtest.activerecord failed with artifacts on master @ 642afd6e8c8d1f967da4aa0c3c08e2bdc0495100: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 7594fb2d1438dd5ed8f80a887b8d60b6cdd296ed: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ a3d53668ff52c2306f37fcad8e9212ff665ca115: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 8866ecadd99e5f6dc8db9fed5d09bc57cd90b03c: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 4ec5a5f43980583eff8b8f8dff1b23090c7e2304: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 942b55ef3f329d2e5e8142c8fc5282ed56173ea7: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ d698e5eaf36bee19901beeff7db3425315402907: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 2861a4ee05fac1cc13f87bf00f368a65ea8700dc: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ b21379bb56dd206e6f63cc7d07ca72e85db7a4c4: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ b21379bb56dd206e6f63cc7d07ca72e85db7a4c4: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ dc974cd698364a4db5acb630162dd8b1856cfad6: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 6eabc2f348710f4146ff984bc346cd8cbe96f83b: Parameters: Same failure on other branches
|
craig bot
pushed a commit
that referenced
this issue
Jan 25, 2023
94180: streamingccl: don't resume job in TestTenantStreamingCutoverOnSourceFailure r=adityamaru a=stevendanna
ALTER TENANT ... COMPLETE REPLICATION
resumes the job for the user, so there is no need to resume the job here. This does raise the question about whether or not it is the right behaviour to resume the job by default.
Fixes #94034
Release note: None
95753: roachtest: fix env var passing in activerecord test r=srosenberg a=andyyang890
This patch fixes the rails version pinning in the activerecord
roachtest. The rails version is passed in via the env variable
`RAILS_VERSION` and was previously being set before the `sudo`
in the adapter install command and thus erroneously discarded.
Informs #94211
Release note: None
95773: multiregionccl: add a missing log scope r=ajwerner a=ajwerner
Epic: none
Release note: None
95802: builtins: array_to_string should traverse nested arrays r=yuzefovich a=msirek
Fixes #95588
In Postgres, `array_to_string` traverses nested arrays and prints their contents. In CRDB, the nested array structures are printed out. For example,
`SELECT array_to_string(ARRAY[ARRAY[ARRAY[5,6], ARRAY[2,3]]], ' ');`
CRDB Result: `ARRAY[ARRAY[5:::INT8,6:::INT8],ARRAY[2:::INT8,3:::INT8]]` Postgres Result: `5 6 2 3`
This fix brings the behavior of `array_to_string` in line with Postgres, and avoids printing the nested ARRAY structures.
Some tools like GoldenGate rely on Postgres-compatible behavior of `array_to_string` for proper functioning.
Release note (bug fix): This patch fixes the array_to_string built-in function so that nested arrays are traversed without printing 'ARRAY' at each nesting level.
95824: sql/execinfrapb: remove no-effect nullable from GenerativeSplitAndScatterSpec r=rhu713 a=rhu713
Remove no-effect nullable from GenerativeSplitAndScatterSpec that was causing warning messages during build.
Release note: None
Co-authored-by: Steven Danna <[email protected]>
Co-authored-by: Andy Yang <[email protected]>
Co-authored-by: Andrew Werner <[email protected]>
Co-authored-by: Mark Sirek <[email protected]>
Co-authored-by: Rui Hu <[email protected]>
|
roachtest.activerecord failed with artifacts on master @ 2ad8df3df3272110705984efc32f1453631ce602: Parameters: Same failure on other branches
|
craig bot
pushed a commit
that referenced
this issue
Jan 26, 2023
94153: sql: Remove type annotations from `column_default` in `information_schema.columns` r=ZhouXing19 a=e-mbrown Informs: #87774 The type annotation on `column_default` caused confusion in postgres compatible apps. This change formats the `column_default` without the type annotation. It does not address the incorrect type annotation. Release note (bug fix): The content of `column_default` in `information_schema.columns` no longer have type annotations. 95855: backupccl: run restore/tpce/32tb/aws/nodes=15/cpus=16 once a week r=benbardin a=msbutler This patch adds the restore/tpce/32TB/aws/nodes=15/cpus=16 test to our weekly test suite. The backup fixture was generated by initing a tpce cluster with 2 Million customers, and running this workload while 48 incremental backups were taken at 15 minute increments. The roachtest restores from a system time captured in the 24th backup. The cluster used to restore the backup will run on aws with 15 nodes each with 16 vcpus. To verify this test exists, run: `roachtest list tag:weekly` Release note: None Epic: none 95861: kv: remove lastToReplica and lastFromReplica from raftMu r=nvanbenschoten a=nvanbenschoten Extracted from #94165 without modification. ---- In 410ef29, we moved these fields from under the Replica.mu to under the Replica.raftMu. This was done to avoid lock contention. In this commit, we move these fields under their own mutex so that they can be accessed without holding the raftMu. This allows us to send Raft messages from other goroutines. The commit also switches from calling RawNode.ReportUnreachable directly in sendRaftMessage to using the more flexible unreachablesMu set, which defers the call to ReportUnreachable until the next Raft tick. As a result, the commit closes #84246. Release note: None Epic: None 95876: sql: remove round-trips from common DISCARD ALL r=ajwerner a=ajwerner #### sql: avoid checking if a role exists when setting to the current role This is an uncached round-trip. It makes `DISCARD` expensive. In #86485 we implemented `SET SESSION AUTHORIZATION DEFAULT`, this added an extra sql query to `DISCARD ALL` to check if the role we'd become exists. This is almost certainly unintentional in the case where the role we'd become is the current session role. I think this just happened because of code consolidation. We now no longer check if the current session role exists. This removes the last round-trip from DISCARD ALL. #### sql: use in-memory session data to decide what to do in DISCARD In #86246 we introduced logic to discard schemas when running DISCARD ALL and DISCARD TEMP. This logic did expensive kv operations unconditionally; if the session knew it had never created a temporary schema, we'd still fetch all databases and proceed to search all databases for a temp schema. This is very expensive. Fixes: #95864 Release note (performance improvement): In 22.2, logic was added to make `SET SESSION AUTHORIZATION DEFAULT` not a no-op. This implementation used more general code for setting the role for a session which made sure that the role exists. The check for whether a role exists is currently uncached. We don't need to check if the role we already are exists. This improves the performance of `DISCARD ALL` in addition to `SET SESSION AUTHORIZATION DEFAULT`. Release note (performance improvement): In 22.2, we introduced support for `DISCARD TEMP` and made `DISCARD ALL` actually discard temp tables. This implementation ran expensive logic to discover temp schemas rather than consulting in-memory data structures. As a result, `DISCARD ALL`, which is issued regularly by connection pools, became an expensive operation when it should be cheap. This problem is now resolved. 95997: ui: hide list of statement for non-admins r=maryliag a=maryliag To get the list of fingerprints used by an index, we use the `system.statement_statistics` directly, but non-admins don't have access to system table. Until #95756 or #95770 are done, we need to hide this feature for non-admins. Part Of #93087 Release note (ui change): Hide list of used fingerprint per index on Index Details page, for non-admin users. 95998: roachtest: update activerecord blocklist r=ZhouXing19 a=andyyang890 This patch removes a few tests from the blocklist that do not exist in the test suite for rails 7.0.3, which were being run prior to the fix for version pinning. Informs #94211 Release note: None 96003: kv: add MVCC local timestamp details to ReadWithinUncertaintyIntervalError r=nvanbenschoten a=nvanbenschoten This PR adds details about MVCC local timestamps to ReadWithinUncertaintyIntervalErrors. This provides more information about the cause of uncertainty errors. The PR also includes a series of minor refactors to clean up this code. Release note: None Epic: None Co-authored-by: e-mbrown <[email protected]> Co-authored-by: Michael Butler <[email protected]> Co-authored-by: Nathan VanBenschoten <[email protected]> Co-authored-by: Andrew Werner <[email protected]> Co-authored-by: maryliag <[email protected]> Co-authored-by: Andy Yang <[email protected]>
|
roachtest.activerecord failed with artifacts on master @ 95a3a11f11b09481bbdf56820eea4420120f04f9: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 69dd453d0e61e258f402c5751de310405743cd18: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 1fb7236f7b1f53e28bde833c28bed83a976138cf: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ 44d9f3c8b7bd46839187cea69eaec640c080ac05: Parameters: Same failure on other branches
|
|
roachtest.activerecord failed with artifacts on master @ ff67a4ba86d710db090ce700f229020365851183: Parameters: Same failure on other branches
|
This was referenced Apr 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
roachtest.activerecord failed with artifacts on master @ 4232883add85a151c423c45904ac4096d04656c5:
Parameters:
ROACHTEST_cloud=gce,ROACHTEST_cpu=4,ROACHTEST_encrypted=false,ROACHTEST_fs=ext4,ROACHTEST_localSSD=true,ROACHTEST_ssd=0Help
See: roachtest README
See: How To Investigate (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-22743
The text was updated successfully, but these errors were encountered: