Actually a viable workaround is just to do a WATCH_ONLY build after seeing this failure, so presumably that means the WATCH_ONLY build isn't chdir'ing into the wrong place like the regular build does, which seems to support this theory.
Actually a viable workaround is just to do a WATCH_ONLY build after seeing this failure, so presumably that means the WATCH_ONLY build isn't chdir'ing into the wrong place like the regular build does, which seems to support this theory.