unittest for parquet fails locally #18212
Description
What happens?
Running unit tests locally fail, mainly parquet-related tests. When I try to inspect the temporary parquet files, the duckdb_unittest_tempdir is empty, so not sure what's happening. Please let me know if I can provide more information to help.
$ ./build/release/test/unittest test/parquet/test_parquet_schema.test rbenv:system
Filters: test/parquet/test_parquet_schema.test
[0/1] (0%): test/parquet/test_parquet_schema.test
1. test/parquet/test_parquet_schema.test
================================================================================
Query unexpectedly failed (test/parquet/test_parquet_schema.test:151)
(test/parquet/test_parquet_schema.test:151)!
Query unexpectedly failed (test/parquet/test_parquet_schema.test:151)
(test/parquet/test_parquet_schema.test:151)!
================================================================================
SELECT *
FROM read_parquet('duckdb_unittest_tempdir/60061/integers.parquet', schema=map {
0: {name: 'renamed_i', type: 'BIGINT', default_value: NULL},
1: {name: 'new_column', type: 'UTINYINT', default_value: 43}
});
================================================================================
Actual result:
================================================================================
Invalid Input Error: No magic bytes found at end of file 'duckdb_unittest_tempdir/60061/integers.parquet'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
unittest is a Catch v2.13.7 host application.
Run with -? for options
test/parquet/test_parquet_schema.test
/Users/xevix/external/duckdb/test/sqlite/test_sqllogictest.cpp:225
...............................................................................
test/parquet/test_parquet_schema.test:151: FAILED:
explicitly with message:
0
[1/1] (100%): test/parquet/test_parquet_schema.test
test cases: 1 | 0 passed | 1 failed
assertions: 55 | 54 passed | 1 failed
To Reproduce
./build/release/test/unittest test/parquet/test_parquet_schema.test
OS:
macOS 15.5 aarch64
DuckDB Version:
DuckDB Client:
N/A
Hardware:
No response
Full Name:
Alejandro Wainzinger
Affiliation:
N/A
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a source build
Did you include all relevant data sets for reproducing the issue?
Not applicable - the reproduction does not require a data set
Did you include all code required to reproduce the issue?
- Yes, I have
Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?
- Yes, I have