basalt-26.3: roachtest: activerecord failed

Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.

roachtest.activerecord failed with artifacts on basalt-26.3 @ 410866d934770553b0ff008caa721a72632dbaaa:

Failed with:

(orm_helpers.go:232).summarizeFailed: 
Tests run on Cockroach v26.3.2-dev-410866d934770553b0ff008caa721a72632dbaaa
Tests run against activerecord 8.1.0
8905 Total Tests Run
8901 tests passed
4 tests failed
45 tests skipped
60 tests ignored
0 tests passed unexpectedly
3 tests failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- PASS: SerializedAttributeTestWithYamlSafeLoad#test_unexpected_serialized_type (expected)
--- FAIL: CalculationsTest#test_should_calculate_grouped_by_function_with_table_alias (unexpected)
--- FAIL: CalculationsTest#test_should_calculate_grouped_by_function (unexpected)
--- PASS: SerializedAttributeTest#test_unexpected_serialized_type (expected)
--- FAIL: CalculationsTest#test_pluck_loaded_relation_sql_fragment (unexpected)
For a full summary look at the activerecord artifacts 
An updated blocklist (activeRecordBlocklist) is available in the artifacts' activerecord log
test artifacts and logs in: /artifacts/activerecord/run_1

Cluster Node to Ip Mapping:

Parameters:

• MetamorphicBasaltMultiAZ=false
• arch=amd64
• cloud=gce
• coverageBuild=false
• cpu=4
• diskCount=0
• encrypted=false
• fs=ext4
• localSSD=true
• metamorphicDRPC=true
• metamorphicLeases=default
• metamorphicWriteBuffering=true
• runtimeAssertionsBuild=true
• storageNodesVersion=v0.1.20-nightly.20260918

Start with the failure summary at orm_helpers.go:232 and the ActiveRecord artifacts in /artifacts/activerecord/run_1. Inspect the three failing CalculationsTest cases and their full logs, then compare the run with the roachtest README guidance. Done means the failure is explained and the activerecord roachtest no longer reports these unexpected failures.