MaskRay added a comment. In D156363#4545215 <https://reviews.llvm.org/D156363#4545215>, @dyung wrote:
> If you cannot reproduce this issue, I can take my buildbot offline and try to > reproduce it to pinpoint which command is causing the problem, but I won’t be > able to do so until Monday. Thank you, knowing which command caused the failure will be very helpful. `clang/test/Driver/fsanitize.c` has the most mysterious failure I have dealt with for this patch. FWIW I've checked that the test passes even if `/usr` does not exist (emulated by proot) => there is as if no host GCC installation that could affect Driver's behavior % cat /tmp/Rel/bin/xxx #!/bin/zsh d=$(dirname "$0") exec proot -R /tmp -b /bin -b /lib64 -b /lib $d/clang --target=aarch64-linux-musl "$@" % cd clang/test/Driver % CLANG=/tmp/Rel/bin/xxx /tmp/Rel/bin/llvm-lit -vv fsanitize.c .. passed Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D156363/new/ https://reviews.llvm.org/D156363 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
