* [FFmpeg-devel] New Patchwork CI Builds
@ 2025-05-07 3:03 softworkz .
2025-05-24 9:40 ` softworkz .
0 siblings, 1 reply; 3+ messages in thread
From: softworkz . @ 2025-05-07 3:03 UTC (permalink / raw)
To: ffmpeg-devel
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-request@ffmpeg.org with subject "unsubscribe".
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [FFmpeg-devel] New Patchwork CI Builds
2025-05-07 3:03 [FFmpeg-devel] New Patchwork CI Builds softworkz .
@ 2025-05-24 9:40 ` softworkz .
2025-05-28 23:28 ` softworkz .
0 siblings, 1 reply; 3+ messages in thread
From: softworkz . @ 2025-05-24 9:40 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz .
> Sent: Mittwoch, 7. Mai 2025 05:04
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] New Patchwork CI Builds
>
> 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
The builds have been updated today as follows:
- When there are FATE errors, the builders are now calling
make fate-list-failing - to show which tests have failed
- In case of error, the log excerpts are showing a link to the
full log at the bottom now
- Even in cases of success, there's now a clickable link that
shows the link to the log output
Examples can be seen on this patch, which I used for testing:
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20250523202351.1712778-4-47210458+raphaelthegreat@users.noreply.github.com/
NOTE
The Windows builds are running partial FATE tests only, pending
this patchset https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14494
(or similar, if anybody has a different idea).
Best regards
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-request@ffmpeg.org with subject "unsubscribe".
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-05-28 23:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-05-07 3:03 [FFmpeg-devel] New Patchwork CI Builds softworkz .
2025-05-24 9:40 ` softworkz .
2025-05-28 23:28 ` softworkz .
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git