We can use github workflow to test out the verification script. The workflow run provides a clean workspace. Here's an example https://github.com/apache/datafusion-python/blob/main/.github/workflows/verify-release-candidate.yml
You can test this by pushing the workflow definition to your fork's main branch and trigger it manually. On Tue, Jun 9, 2026 at 5:57 PM Matt Topol <[email protected]> wrote: > >> > The verify script requirements need to get updated: >> > >> > - meson is required but not listed >> >> meson is not required to run the verify script, we depend on cmake, they >> are two independent build systems and meson is not fully supported(e.g, >> meson doesn't support iceberg-bundle). >> > > If meson isn't supposed to be required, then something should change in > the verify script because cmake failed before it even got to building until > I installed meson. > > > - gtest/gmock are required but not listed >> >> googletest will automatically be made available by cmake's FetchContent, >> did >> you run into some problems? >> > > Cmake didn't do the fetch content by default then, it failed during > configure because it couldn't find gtest/gmock. After I installed them, I > could build. > > > - I had to export CPR_USE_SYSTEM_CURL=OFF for some reason due to ssl >> > stuff, unsure. >> >> I once met an issue that the system curl version is too low(something >> like curl >= 7.64.0 is required), may I know your >> installed curl version? We might need to specify the minimum curl >> version in the README. >> > > My system curl is 8.14.1 so this seems odd. I'll try recreating the issue > tomorrow and capture the exact error. > >>
