On 12/04/25 1:35 am, Otto Kekäläinen wrote: >>> Note I got this far by skipping the test suite. I will need to revisit >>> it though, but getting end-to-end working first makes optimizing >>> stages easier workflow-wise. >> >> What are the other failing tests? > > Alright, I have now everything else woking apart from the test suite.
\o/ > Currently it is failing on: > > 2025/04/11 20:02:11 Could not prepare the database: Cannot connect to > the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon > running? > > Maybe I should selectively try to disable tests that depend on Docker? If tests are trying to start a docker daemon, then yes. If it is just using docker golang library then it is worth investigating. I looked at the log and I see some tests failing due to test dependencies not being satisfied (this looks like genuine error rather than missing tags or some cfg problem). The other failure is what you point to above. And indeed this needs to be disabled as you can't run docker in a chroot build. Some other tests are trying to initialize a postgresql db and I am unsure how feasible stuff like that is inside a chroot. Maybe it is worth it to disable those too? > > Full log at https://salsa.debian.org/go-team/packages/usql/-/merge_requests/1 >
