Closed jerboaa closed 7 months ago
Example failure we see in CI is here: https://github.com/graalvm/mandrel-packaging/actions/runs/7494241350/job/20401713155?pr=388#step:9:432
Further info as the PR tester uses a different workflow that we use for mandrel nightly CI (where we don't see the issue). It does not seem related to:
graal/common.json
). See this PR build.We only see this issue for Graal master, 24.1 (JDK 23 based builds). See https://github.com/graalvm/mandrel-packaging/pull/390 which has a clean CI run here: https://github.com/graalvm/mandrel-packaging/actions/runs/7501144635?pr=390
This issue appears to be stale because it has been open 30 days with no activity. This issue will be closed in 7 days unless Stale
label is removed or a new comment is made.
We don't seem to see those issues any more. See for example: https://github.com/graalvm/mandrel-packaging/actions/runs/7901681233/job/21565689677?pr=405
Closing for now.
Starting with #384 we see weird Windows build failures in the ninja build. The error looks like:
The
mkdir
call using a mangled non-windows path ofD_/a/mandrel-packaging/mandrel-packaging/mandrel/substratevm/mxbuild/jdk23/svm-jvmfuncs-fallback-builder
overD:\a\mandrel-packaging\mandrel-packaging\mandrel\substratevm\mxbuild\jdk23\svm-jvmfuncs-fallback-builder
seems to cause this. I don't know what makes ninja build change this (or try to create that directory) while for other CI Windows builds we don't see it.This needs investigation. /cc @Karm @zakkak