Thanks Drew. That appears to be the problem, which I believe we
encountered before during verification.

I also noted that after the tests complete, we don't properly clean up the
docker containers which are left running indefinitely.

All that said, I don't think those are blockers and I did get a clean run.

+1 (binding)

verified sigs/sums/license/build/tests (python 3.13)

-Dan

On Fri, Feb 6, 2026 at 3:02 PM Drew <[email protected]> wrote:

> Thanks for the validation Dan!
>
> The SQLAlchemy error is a test collision with local config. The failing
> test calls `load_catalog("default")`, which reads `~/.pyiceberg.yaml` if it
> exists. If that file has a default catalog (like with a uri), those
> settings leak into the test and trigger the error you ran into. I've opened
> a PR <https://github.com/apache/iceberg-python/pull/3006> to fix the
> config collision. For now, you can mv or rename the ~/.pyiceberg.yaml and
> the test should pass. That being said, this is kind of a band-aid, and we
> should reevaluate how catalogs are being used across the tests.
>
> The "too many open files" issue is system dependent and file limits are
> sometimes low. Running `ulimit -n 4096` fixes it for the current run.
>
>
> Drew
>
> On Fri, Feb 6, 2026 at 9:39 AM Daniel Weeks <[email protected]> wrote:
>
>> -1
>>
>> I've tried verifying the release multiple times over the last few days
>> following the specific steps on the release validation page, but I haven't
>> been able to complete the tests.
>>
>> I've tried with both Python 3.11 and 3.13.  I also tried using freshly
>> created virtual environments, but ran into a number of issues.
>>
>> The first issue related to tests opening too many files, which I worked
>> around by increasing the ulimit.
>>
>> However, I have not been able to get past the following test:
>>
>> FAILED
>> tests/integration/test_writes/test_writes.py::test_nanosecond_support_on_catalog
>> - sqlalchemy.exc.NoSuchModuleError: Can't load plugin:
>> sqlalchemy.dialects:https
>>
>> Is this related to a dependency change or have we not captured something
>> in the release verification process?
>>
>> -Dan
>>
>> On Wed, Feb 4, 2026 at 1:12 AM Jean-Baptiste Onofré <[email protected]>
>> wrote:
>>
>>> +1 (non binding)
>>>
>>> Regards
>>> JB
>>>
>>> On Sat, Jan 31, 2026 at 3:32 AM Kevin Liu <[email protected]> wrote:
>>>
>>>> +1 (binding)
>>>>
>>>> [x] Download links are valid.
>>>> [x] Checksums and signatures.
>>>> [x] LICENSE/NOTICE files exist
>>>> [x] No unexpected binary files
>>>> [x] All source files have ASF headers
>>>> [x] Can compile from source
>>>> [x] Built and tested from source (w/ python 3.13)
>>>>
>>>> Thanks for running the release!
>>>>
>>>> Best,
>>>> Kevin Liu
>>>>
>>>> On Fri, Jan 30, 2026 at 5:37 PM Shawn Chang <[email protected]>
>>>> wrote:
>>>>
>>>>> +1 (non-binding)
>>>>>
>>>>> Verified on mac M3 pro:
>>>>> - GPG signature: valid
>>>>> - SHA512 checksums: valid
>>>>> - License headers (RAT check): passed
>>>>> - Unit and integration tests: passed
>>>>>
>>>>> Thanks Drew for helping with release!
>>>>>
>>>>> Best,
>>>>> Shawn
>>>>>
>>>>> On Fri, Jan 30, 2026 at 3:27 PM Drew <[email protected]> wrote:
>>>>>
>>>>>> Hi Everyone,
>>>>>>
>>>>>> I propose that we release the following RC as the official PyIceberg 
>>>>>> 0.11.0 release.
>>>>>>
>>>>>> The commit ID is d62b36024ab36fc3f86be50634cd8b32ce3fb9a1
>>>>>>
>>>>>> * This corresponds to the tag: pyiceberg-0.11.0rc2 
>>>>>> (e636578b6f597b55c460b2c44a851e4b23814012)
>>>>>> * 
>>>>>> https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.11.0rc2
>>>>>> * 
>>>>>> https://github.com/apache/iceberg-python/tree/d62b36024ab36fc3f86be50634cd8b32ce3fb9a1
>>>>>>
>>>>>> The release tarball, signature, and checksums are here:
>>>>>>
>>>>>> * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.11.0rc2/
>>>>>>
>>>>>> You can find the KEYS file here:
>>>>>>
>>>>>> * https://downloads.apache.org/iceberg/KEYS
>>>>>>
>>>>>> Convenience binary artifacts are staged on pypi:
>>>>>> https://pypi.org/project/pyiceberg/0.11.0rc2/
>>>>>>
>>>>>> And can be installed using: pip3 install pyiceberg==0.11.0rc2
>>>>>>
>>>>>> Instructions for verifying a release can be found here:
>>>>>>
>>>>>> * https://py.iceberg.apache.org/verify-release/
>>>>>>
>>>>>> Please download, verify, and test.
>>>>>>
>>>>>> Please vote in the next 72 hours.
>>>>>> [ ] +1 Release this as PyIceberg 0.11.0
>>>>>> [ ] +0
>>>>>> [ ] -1 Do not release this because...
>>>>>>
>>>>>>

Reply via email to