[llvm] [lit] Echo full RUN lines in case of external shells (PR #65267)

via llvm-commits llvm-commits at lists.llvm.org
Wed Sep 6 20:34:56 PDT 2023


dyung wrote:

> Unfortunately whenever I re-start the build bot, it thinks it need to re-try the previous build since that had the failed connection - but that previous build still has this patch applied and therefore terminates again :-( I'm trying to work around this now.

@uweigand if you are still trying to recover your buildbot, this is the process I used which I was able to recover mine. Thanks to the info everyone found here, it seems there are 4 affected tests fork-sigusr.test, merge-sigusr.test, sigint.test and sigusr.test. With the worker offline, I manually edited the files to add a `, *` to the `UNSUPPORTED` line to get the run to skip the tests so it wouldn't fail. I then stashed the change and brought the worker back online. When the job rerun had finished the sync and was doing the build, I went to the local git repo and unstashed the test changes and then let the build/test complete. Then before the next run is executed, just revert the local test changes. The tests were not exactly skipped (they ended up being "UNRESOLVED" because of the new syntax required for the UNSUPPORTED lines), but the net result was the run completed and moved on to the next job which then passed. Hope this helps you to recover your bot.

"Completed" job: https://lab.llvm.org/buildbot/#/builders/247/builds/8680

https://github.com/llvm/llvm-project/pull/65267


More information about the llvm-commits mailing list