On Wed, 17 Apr 2024 at 16:00, Tom Lane <t...@sss.pgh.pa.us> wrote: > Break gram.y (say, misspell some token in a production) and > see what happens. The behavior's likely to be timing sensitive > though.
Thanks for clarifying. It took me a little while to break gram.y in such a way that I was able to consistently reproduce, but I managed in the end using the attached small diff. And then running ninja in non-parallel mode: ninja -C build all -j1 As I expected this problem was indeed fairly easy to address by still building "backend/parser" before "interfaces". See attached patch.
v1-0001-Speed-up-clean-parallel-meson-builds-a-lot.patch
Description: Binary data
trigger-confusing-build-error.diff
Description: Binary data
