Skip to content
Build & Test

Build & Test - Fix 0-Task Plans in Single-Shard Router When Updating a Local Table with Reference Table in Subquery #2770

Sign in to view logs

Build & Test - Fix 0-Task Plans in Single-Shard Router When Updating a Local Table with Reference Table in Subquery

Build & Test - Fix 0-Task Plans in Single-Shard Router When Updating a Local Table with Reference Table in Subquery #2770

Triggered via pull request February 24, 2025 14:04
@m3hm3tm3hm3t
synchronize #7897
m3hm3t/issue_7891
Status Cancelled
Total duration 25m 45s
Artifacts 161

build_and_test.yml

on: pull_request
Initialize parameters
0s
Initialize parameters
Matrix: build
check-sql-snapshots
26s
check-sql-snapshots
check-style
1m 54s
check-style
Detect regression tests need to be ran
9s
Detect regression tests need to be ran
Matrix: test-arbitrary-configs
Matrix: test-citus
Matrix: test-pg-upgrade
PG15 - check-citus-upgrade
1m 0s
PG15 - check-citus-upgrade
CH Benchmark
0s
CH Benchmark
TPCC Benchmark
0s
TPCC Benchmark
Parallel 32
3s
Parallel 32
upload-coverage
57s
upload-coverage
Matrix: Test flakyness
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 158 warnings
PG15 - check-split
Process completed with exit code 2.
PG15 - check-multi-mx
Process completed with exit code 2.
PG17 - check-multi
Process completed with exit code 2.
PG15 - check-multi
Process completed with exit code 2.
PG16 - check-multi
Process completed with exit code 2.
PG16 - check-arbitrary-configs-1
Canceling since a higher priority waiting request for 'Build & Test-7897' exists
PG16 - check-arbitrary-configs-1
The operation was canceled.
check-sql-snapshots
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
check-sql-snapshots
The process '/usr/bin/git' failed with exit code 128
Build for PG15
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Build for PG17
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Build for PG16
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
check-style
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
check-style
The process '/usr/bin/git' failed with exit code 128
Detect regression tests need to be ran
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Detect regression tests need to be ran
The process '/usr/bin/git' failed with exit code 128
Parallel 32
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Parallel 32
The process '/usr/bin/git' failed with exit code 128
PG16 - check-pytest
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-pytest
The process '/usr/bin/git' failed with exit code 128
PG15 - check-citus-upgrade
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-citus-upgrade
The process '/usr/bin/git' failed with exit code 128
PG17 - check-pytest
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-pytest
The process '/usr/bin/git' failed with exit code 128
PG15 - check-pytest
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-pytest
The process '/usr/bin/git' failed with exit code 128
PG15 - check-columnar-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-columnar-isolation
The process '/usr/bin/git' failed with exit code 128
PG15-PG16 - check-pg-upgrade
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15-PG16 - check-pg-upgrade
The process '/usr/bin/git' failed with exit code 128
PG16-PG17 - check-pg-upgrade
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16-PG17 - check-pg-upgrade
The process '/usr/bin/git' failed with exit code 128
PG15-PG17 - check-pg-upgrade
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15-PG17 - check-pg-upgrade
The process '/usr/bin/git' failed with exit code 128
PG16 - check-follower-cluster
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-follower-cluster
The process '/usr/bin/git' failed with exit code 128
PG16 - check-columnar-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-columnar-isolation
The process '/usr/bin/git' failed with exit code 128
PG17 - check-follower-cluster
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-follower-cluster
The process '/usr/bin/git' failed with exit code 128
PG15 - check-follower-cluster
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-follower-cluster
The process '/usr/bin/git' failed with exit code 128
PG17 - check-columnar-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-columnar-isolation
The process '/usr/bin/git' failed with exit code 128
PG16 - check-enterprise-isolation-logicalrep-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-enterprise-isolation-logicalrep-2
The process '/usr/bin/git' failed with exit code 128
PG16 - check-enterprise-isolation-logicalrep-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-enterprise-isolation-logicalrep-3
The process '/usr/bin/git' failed with exit code 128
PG17 - check-enterprise-isolation-logicalrep-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-enterprise-isolation-logicalrep-3
The process '/usr/bin/git' failed with exit code 128
PG16 - check-split
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-split
The process '/usr/bin/git' failed with exit code 128
PG15 - check-enterprise-isolation-logicalrep-3
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-enterprise-isolation-logicalrep-3
The process '/usr/bin/git' failed with exit code 128
PG17 - check-columnar
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-columnar
The process '/usr/bin/git' failed with exit code 128
PG16 - check-columnar
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-columnar
The process '/usr/bin/git' failed with exit code 128
PG15 - check-columnar
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-columnar
The process '/usr/bin/git' failed with exit code 128
PG16 - check-enterprise-failure
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-enterprise-failure
The process '/usr/bin/git' failed with exit code 128
PG15 - check-query-generator
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-query-generator
The process '/usr/bin/git' failed with exit code 128
PG16 - check-query-generator
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-query-generator
The process '/usr/bin/git' failed with exit code 128
PG17 - check-enterprise-isolation-logicalrep-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-enterprise-isolation-logicalrep-2
The process '/usr/bin/git' failed with exit code 128
PG15 - check-split
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-split
The process '/usr/bin/git' failed with exit code 128
PG15 - check-enterprise-isolation-logicalrep-2
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-enterprise-isolation-logicalrep-2
The process '/usr/bin/git' failed with exit code 128
PG15 - check-enterprise-failure
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-enterprise-failure
The process '/usr/bin/git' failed with exit code 128
PG17 - check-enterprise-failure
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-enterprise-failure
The process '/usr/bin/git' failed with exit code 128
PG17 - check-split
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-split
The process '/usr/bin/git' failed with exit code 128
PG16 - check-vanilla
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-vanilla
The process '/usr/bin/git' failed with exit code 128
PG17 - check-query-generator
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-query-generator
The process '/usr/bin/git' failed with exit code 128
PG15 - check-enterprise
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-enterprise
The process '/usr/bin/git' failed with exit code 128
PG16 - check-enterprise
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-enterprise
The process '/usr/bin/git' failed with exit code 128
PG17 - check-enterprise
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-enterprise
The process '/usr/bin/git' failed with exit code 128
PG15 - check-vanilla
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-vanilla
The process '/usr/bin/git' failed with exit code 128
PG17 - check-vanilla
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-vanilla
The process '/usr/bin/git' failed with exit code 128
PG16 - check-enterprise-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-enterprise-isolation
The process '/usr/bin/git' failed with exit code 128
PG15 - check-enterprise-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-enterprise-isolation
The process '/usr/bin/git' failed with exit code 128
PG17 - check-enterprise-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-enterprise-isolation
The process '/usr/bin/git' failed with exit code 128
PG16 - check-enterprise-isolation-logicalrep-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-enterprise-isolation-logicalrep-1
The process '/usr/bin/git' failed with exit code 128
PG15 - check-failure
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-failure
The process '/usr/bin/git' failed with exit code 128
PG15 - check-enterprise-isolation-logicalrep-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-enterprise-isolation-logicalrep-1
The process '/usr/bin/git' failed with exit code 128
PG15 - check-multi-mx
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-multi-mx
The process '/usr/bin/git' failed with exit code 128
PG17 - check-failure
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-failure
The process '/usr/bin/git' failed with exit code 128
PG17 - check-enterprise-isolation-logicalrep-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-enterprise-isolation-logicalrep-1
The process '/usr/bin/git' failed with exit code 128
PG16 - check-failure
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-failure
The process '/usr/bin/git' failed with exit code 128
PG16 - check-multi-mx
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-multi-mx
The process '/usr/bin/git' failed with exit code 128
PG17 - check-multi-mx
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-multi-mx
The process '/usr/bin/git' failed with exit code 128
PG16 - installcheck
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - installcheck
The process '/usr/bin/git' failed with exit code 128
PG17 - installcheck
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - installcheck
The process '/usr/bin/git' failed with exit code 128
PG15 - installcheck
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - installcheck
The process '/usr/bin/git' failed with exit code 128
PG16 - check-operations
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-operations
The process '/usr/bin/git' failed with exit code 128
PG15 - check-operations
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-operations
The process '/usr/bin/git' failed with exit code 128
PG17 - check-operations
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-operations
The process '/usr/bin/git' failed with exit code 128
PG16 - check-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-isolation
The process '/usr/bin/git' failed with exit code 128
PG15 - check-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-isolation
The process '/usr/bin/git' failed with exit code 128
PG17 - check-isolation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-isolation
The process '/usr/bin/git' failed with exit code 128
PG16 - check-arbitrary-configs-3
The process '/usr/bin/git' failed with exit code 128
PG17 - check-multi
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-multi
The process '/usr/bin/git' failed with exit code 128
PG15 - check-multi
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-multi
The process '/usr/bin/git' failed with exit code 128
PG16 - check-multi
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-multi
The process '/usr/bin/git' failed with exit code 128
PG16 - check-arbitrary-configs-5
The process '/usr/bin/git' failed with exit code 128
PG17 - check-arbitrary-configs-3
The process '/usr/bin/git' failed with exit code 128
PG16 - check-arbitrary-configs-4
The process '/usr/bin/git' failed with exit code 128
PG17 - check-arbitrary-configs-2
The process '/usr/bin/git' failed with exit code 128
PG17 - check-multi-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG17 - check-multi-1
The process '/usr/bin/git' failed with exit code 128
PG16 - check-multi-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG16 - check-multi-1
The process '/usr/bin/git' failed with exit code 128
PG15 - check-multi-1
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
PG15 - check-multi-1
The process '/usr/bin/git' failed with exit code 128
PG17 - check-arbitrary-configs-0
The process '/usr/bin/git' failed with exit code 128
PG17 - check-arbitrary-configs-4
The process '/usr/bin/git' failed with exit code 128
PG17 - check-arbitrary-configs-5
The process '/usr/bin/git' failed with exit code 128
PG15 - check-arbitrary-configs-3
The process '/usr/bin/git' failed with exit code 128
PG15 - check-arbitrary-configs-2
The process '/usr/bin/git' failed with exit code 128
PG17 - check-arbitrary-configs-1
The process '/usr/bin/git' failed with exit code 128
PG15 - check-arbitrary-configs-4
The process '/usr/bin/git' failed with exit code 128
PG15 - check-arbitrary-configs-5
The process '/usr/bin/git' failed with exit code 128
PG16 - check-arbitrary-configs-0
The process '/usr/bin/git' failed with exit code 128
PG15 - check-arbitrary-configs-0
The process '/usr/bin/git' failed with exit code 128
PG15 - check-arbitrary-configs-1
The process '/usr/bin/git' failed with exit code 128
PG16 - check-arbitrary-configs-2
The process '/usr/bin/git' failed with exit code 128
PG16 - check-arbitrary-configs-1
The process '/usr/bin/git' failed with exit code 128
upload-coverage
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101

Artifacts

Produced during runtime
Name Size
15_16_upgrade
84 KB
15_17_upgrade
84.1 KB
15_arbitrary_configs_0
383 KB
15_arbitrary_configs_1
391 KB
15_arbitrary_configs_2
381 KB
15_arbitrary_configs_3
380 KB
15_arbitrary_configs_4
380 KB
15_arbitrary_configs_5
387 KB
15_check-columnar
181 KB
15_check-columnar-isolation
15.1 KB
15_check-enterprise
185 KB
15_check-enterprise-failure
86.5 KB
15_check-enterprise-isolation
58.1 KB
15_check-enterprise-isolation-logicalrep-1
49.4 KB
15_check-enterprise-isolation-logicalrep-2
20.4 KB
15_check-enterprise-isolation-logicalrep-3
16.8 KB
15_check-failure
177 KB
15_check-follower-cluster
21.5 KB
15_check-isolation
275 KB
15_check-multi
1.32 MB
15_check-multi-1
1.66 MB
15_check-multi-mx
469 KB
15_check-operations
157 KB
15_check-query-generator
21.3 KB
15_check-split
151 KB
15_check-vanilla
1.76 MB
15_citus_upgrade
200 KB
16_17_upgrade
84.1 KB
16_arbitrary_configs_0
384 KB
16_arbitrary_configs_1
328 KB
16_arbitrary_configs_2
382 KB
16_arbitrary_configs_3
380 KB
16_arbitrary_configs_4
381 KB
16_arbitrary_configs_5
388 KB
16_check-columnar
181 KB
16_check-columnar-isolation
15.1 KB
16_check-enterprise
185 KB
16_check-enterprise-failure
86.2 KB
16_check-enterprise-isolation
57.6 KB
16_check-enterprise-isolation-logicalrep-1
48.9 KB
16_check-enterprise-isolation-logicalrep-2
20.1 KB
16_check-enterprise-isolation-logicalrep-3
16.7 KB
16_check-failure
177 KB
16_check-follower-cluster
21.6 KB
16_check-isolation
275 KB
16_check-multi
1.33 MB
16_check-multi-1
1.66 MB
16_check-multi-mx
468 KB
16_check-operations
156 KB
16_check-query-generator
23.4 KB
16_check-split
151 KB
16_check-vanilla
1.82 MB
17_arbitrary_configs_0
384 KB
17_arbitrary_configs_1
391 KB
17_arbitrary_configs_2
381 KB
17_arbitrary_configs_3
380 KB
17_arbitrary_configs_4
381 KB
17_arbitrary_configs_5
387 KB
17_check-columnar
181 KB
17_check-columnar-isolation
15.1 KB
17_check-enterprise
185 KB
17_check-enterprise-failure
86.2 KB
17_check-enterprise-isolation
57.2 KB
17_check-enterprise-isolation-logicalrep-1
48.7 KB
17_check-enterprise-isolation-logicalrep-2
20.1 KB
17_check-enterprise-isolation-logicalrep-3
16.7 KB
17_check-failure
177 KB
17_check-follower-cluster
21.8 KB
17_check-isolation
275 KB
17_check-multi
1.38 MB
17_check-multi-1
1.66 MB
17_check-multi-mx
468 KB
17_check-operations
156 KB
17_check-query-generator
25.1 KB
17_check-split
150 KB
17_check-vanilla
1.9 MB
build-15
11 MB
build-16
11.2 MB
build-17
11.8 MB
codeclimate-15_16_upgrade
99.4 KB
codeclimate-15_17_upgrade
99.7 KB
codeclimate-15_arbitrary_configs_0
111 KB
codeclimate-15_arbitrary_configs_1
112 KB
codeclimate-15_arbitrary_configs_2
111 KB
codeclimate-15_arbitrary_configs_3
110 KB
codeclimate-15_arbitrary_configs_4
112 KB
codeclimate-15_arbitrary_configs_5
111 KB
codeclimate-15_cdc_installcheck
93.1 KB
codeclimate-15_citus_upgrade
86.9 KB
codeclimate-15_regress_check-columnar
96.7 KB
codeclimate-15_regress_check-columnar-isolation
76.8 KB
codeclimate-15_regress_check-enterprise
110 KB
codeclimate-15_regress_check-enterprise-failure
90.8 KB
codeclimate-15_regress_check-enterprise-isolation
95.4 KB
codeclimate-15_regress_check-enterprise-isolation-logicalrep-1
95.1 KB
codeclimate-15_regress_check-enterprise-isolation-logicalrep-2
89.7 KB
codeclimate-15_regress_check-enterprise-isolation-logicalrep-3
88.3 KB
codeclimate-15_regress_check-failure
104 KB
codeclimate-15_regress_check-follower-cluster
94.5 KB
codeclimate-15_regress_check-isolation
112 KB
codeclimate-15_regress_check-multi
128 KB
codeclimate-15_regress_check-multi-1
134 KB
codeclimate-15_regress_check-multi-mx
118 KB
codeclimate-15_regress_check-operations
101 KB
codeclimate-15_regress_check-pytest
86 KB
codeclimate-15_regress_check-query-generator
93.2 KB
codeclimate-15_regress_check-split
103 KB
codeclimate-15_regress_check-vanilla
83.3 KB
codeclimate-16_17_upgrade
99.6 KB
codeclimate-16_arbitrary_configs_0
112 KB
codeclimate-16_arbitrary_configs_1
112 KB
codeclimate-16_arbitrary_configs_2
111 KB
codeclimate-16_arbitrary_configs_3
111 KB
codeclimate-16_arbitrary_configs_4
112 KB
codeclimate-16_arbitrary_configs_5
111 KB
codeclimate-16_cdc_installcheck
93.5 KB
codeclimate-16_regress_check-columnar
96.8 KB
codeclimate-16_regress_check-columnar-isolation
76.8 KB
codeclimate-16_regress_check-enterprise
111 KB
codeclimate-16_regress_check-enterprise-failure
90.9 KB
codeclimate-16_regress_check-enterprise-isolation
95.8 KB
codeclimate-16_regress_check-enterprise-isolation-logicalrep-1
95.1 KB
codeclimate-16_regress_check-enterprise-isolation-logicalrep-2
90 KB
codeclimate-16_regress_check-enterprise-isolation-logicalrep-3
88.7 KB
codeclimate-16_regress_check-failure
105 KB
codeclimate-16_regress_check-follower-cluster
94.6 KB
codeclimate-16_regress_check-isolation
112 KB
codeclimate-16_regress_check-multi
128 KB
codeclimate-16_regress_check-multi-1
134 KB
codeclimate-16_regress_check-multi-mx
119 KB
codeclimate-16_regress_check-operations
101 KB
codeclimate-16_regress_check-pytest
86.2 KB
codeclimate-16_regress_check-query-generator
94.7 KB
codeclimate-16_regress_check-split
102 KB
codeclimate-16_regress_check-vanilla
83.6 KB
codeclimate-17_arbitrary_configs_0
112 KB
codeclimate-17_arbitrary_configs_1
113 KB
codeclimate-17_arbitrary_configs_2
112 KB
codeclimate-17_arbitrary_configs_3
111 KB
codeclimate-17_arbitrary_configs_4
112 KB
codeclimate-17_arbitrary_configs_5
112 KB
codeclimate-17_cdc_installcheck
93.6 KB
codeclimate-17_regress_check-columnar
97.3 KB
codeclimate-17_regress_check-columnar-isolation
77.3 KB
codeclimate-17_regress_check-enterprise
111 KB
codeclimate-17_regress_check-enterprise-failure
91.4 KB
codeclimate-17_regress_check-enterprise-isolation
96.1 KB
codeclimate-17_regress_check-enterprise-isolation-logicalrep-1
95.5 KB
codeclimate-17_regress_check-enterprise-isolation-logicalrep-2
90.2 KB
codeclimate-17_regress_check-enterprise-isolation-logicalrep-3
89.2 KB
codeclimate-17_regress_check-failure
105 KB
codeclimate-17_regress_check-follower-cluster
95.1 KB
codeclimate-17_regress_check-isolation
113 KB
codeclimate-17_regress_check-multi
129 KB
codeclimate-17_regress_check-multi-1
135 KB
codeclimate-17_regress_check-multi-mx
119 KB
codeclimate-17_regress_check-operations
101 KB
codeclimate-17_regress_check-pytest
86.5 KB
codeclimate-17_regress_check-query-generator
93.8 KB
codeclimate-17_regress_check-split
103 KB
codeclimate-17_regress_check-vanilla
83.9 KB