Hello Everybody,
today, I've set up a number of additional CI builds for Patchwork: - linux_x64_oot Out-of-tree build, no FATE Checks: apply,configure,make https://dev.azure.com/githubsync/ffmpeg/_build?definitionId=18 - linux-x64-shared Shared build, no FATE Checks: apply,configure,make https://dev.azure.com/githubsync/ffmpeg/_build?definitionId=17 - win-msvc-x64 Windows with MSYS2 and MS VC compilation Checks: apply,configure,make,make_fate https://dev.azure.com/githubsync/ffmpeg/_build?definitionId=19 - win-gcc-x64 Windows with MSYS2 and GCC compilation Checks: apply,configure,make,make_fate https://dev.azure.com/githubsync/ffmpeg/_build?definitionId=21 - mac-x64 MacOS 14, x64 VM Checks: apply,configure,make,make_fate https://dev.azure.com/githubsync/ffmpeg/_build?definitionId=15 I've used the existing code from the patchwork_job_runner repo as a starting point, but ended up quite differently as this is made for dedicated VMs rather than for cloud CI agents. I can share the code if someone would be interested. Still, I tried to replicate the existing behaviors as closely as possible. Differences: - Different to the existing runners, full logs can be publicly accessed through the URLs above. I'm actually reporting direct URLs to the logs, but Patchwork doesn't expose them in the UI (maybe this can be adjusted). - There's no commit message checking done (would be redundant). - No "new warnings" checks are done (builders are stateless). Same: - Apply and configure results are only reported in case of error. - Make and make_fate are reported on error and on success. - In case of make error make_fate is not reported. Please let me know in case of any questions. Important: as this is pretty fresh, there might be issues. Should you see a "red bubble" on any of your patches from which you think it's not justified, please let me know, it can be fixed. Thanks, sw _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
