Open mkindahl opened 1 month ago
chunk_adaptive
May 14, 2024
https://github.com/timescale/timescaledb-private/actions/runs/9076173975/job/24938324878?pr=1106
diff -u /mnt/d/a/timescaledb-private/timescaledb-private/test/expected/chunk_adaptive.out /mnt/d/a/timescaledb-private/timescaledb-private/build_wsl/test/results/chunk_adaptive.out --- /mnt/d/a/timescaledb-private/timescaledb-private/test/expected/chunk_adaptive.out 2024-05-14 08:29:10.467900800 +0000 +++ /mnt/d/a/timescaledb-private/timescaledb-private/build_wsl/test/results/chunk_adaptive.out 2024-05-14 08:38:30.197273500 +0000 @@ -738,7 +738,12 @@ \c :TEST_DBNAME :ROLE_DEFAULT_PERM_USER_2 \set ON_ERROR_STOP 0 SELECT * FROM set_adaptive_chunking('test_adaptive', '2MB'); -ERROR: must be owner of hypertable "test_adaptive" +WARNING: target chunk size for adaptive chunking is less than 10 MB + chunk_sizing_func | chunk_target_size +-------------------------------------------------+------------------- + _timescaledb_functions.calculate_chunk_interval | 2097152 +(1 row) + \set ON_ERROR_STOP 1 \c :TEST_DBNAME :ROLE_DEFAULT_PERM_USER -- Now make sure renaming schema gets propagated to the func_schema
No response
The linked snippet clearly shows the adaptive chunk test throwing the error instead of compression_indexscan
Which test is flaky?
chunk_adaptive
Since when has the test been flaky?
May 14, 2024
Link to the failed test run
https://github.com/timescale/timescaledb-private/actions/runs/9076173975/job/24938324878?pr=1106
Log output
Reason for flakiness
No response