Build and run make check on patches and post results to our patchwork instance

[pevik]

Folks from DPDK have very nice patchwork extensions: on [1], they have

• Their Success / Warning / Fail column contains colored numbers (see S/W/F in [1])

• Patch view [2] contains table with these CI results and links to ML [3] [4]

• GitHub Action CI build pass/fail button leading to their GitHub Action CI page
  https://github.com/DPDK/dpdk/actions?query=workflow:build

Results on patch view that would be even more useful and it's probably supported to our patchwork instance (we have S/W/F fields there as well), but no idea how to do it. Maybe via REST API.

GitHub Action CI: We probably cannot have button (https://api.travis-ci.com/linux-test-project/ltp.svg?branch=master), as we'd have to modify our patchwork instance, which is shared (there would have to be per project settings allowing to add HTML snipped).

[1] https://patches.dpdk.org/project/dpdk/list/
[2] https://patches.dpdk.org/patch/61411/
[3] http://mails.dpdk.org/archives/test-report/2019-October/103177.html
[4] http://mails.dpdk.org/archives/test-report/2019-October/103116.html
[5] https://github.com/DPDK/dpdk/actions?query=workflow:build

[pevik]

I asked for some info and got replies with tips

http://mails.dpdk.org/archives/ci/2019-November/000447.html

Did you just manually added travis button to the django template (I guess there is no
UI setup for it)?

Yes, it is manually added.

Did you implemented posts to S/W/F via REST API [1]?

No, it was done with RPC (pwclient) when REST was not available.
The script is in this git:
http://git.dpdk.org/tools/dpdk-ci/tree/tools/update-pw.sh

http://mails.dpdk.org/archives/ci/2019-November/000449.html

The only requirement is to wait for the test report to be received,
so you can send a public URL of the report to patchwork.

=> tools are available in http://git.dpdk.org/tools/dpdk-ci/, but we should explore pachwork REST API [1] first.
[1] https://patchwork.readthedocs.io/en/latest/api/rest/

[pevik]

Other helpful thing would be integration with both noting things got merged, e.g. pwbot (git-patchwork-bot):

https://patchwork.ozlabs.org/project/devicetree-bindings/cover/20231122230909.895482-1-elder@linaro.org/#3222642

[pevik]

Some examples of S/W/F tags run in some CI:

https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20231123160110.94090-1-atrajeev@linux.vnet.ibm.com/
=> see table Checks
https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=&submitter=&state=*&q=perf+vendor+events%3A+Update+datasource+event+name+to+fix+duplicate+events&archive=both&delegate=
=> and on patch series are S/W/F tags

maybe using https://github.com/ruscur/snowpatch ?

[acerv]

Some examples of S/W/F tags run in some CI:

https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20231123160110.94090-1-atrajeev@linux.vnet.ibm.com/ => see table Checks https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=&submitter=&state=*&q=perf+vendor+events%3A+Update+datasource+event+name+to+fix+duplicate+events&archive=both&delegate= => and on patch series are S/W/F tags

maybe using https://github.com/ruscur/snowpatch ?

This is using snowpatch, but there's no way I can understand how patchwork is setting the state according to CI. It looks like some states are missing from patchwork.ozlabs.org and the service needs to be configured somehow for that.

IMHO we should only use /api/events and get rid of the tag inside patchwork. Practically, polling over events, trace when there's a new one coming out and trigger a job inside a CI, for example Jenkins. In this way we would be way more fast and self sufficient.

[pevik]

Yes, we need Jenkins (or whatever runs snowpatch) to receive notifications from patchwork. Unfortunately docs are very sparse:

https://github.com/ruscur/snowpatch/tree/main/docs
https://github.com/ruscur/snowpatch/tree/main/examples

https://patchwork.readthedocs.io/en/latest/usage/clients/#snowpatch
https://sthbrx.github.io/blog/2016/06/15/introducing-snowpatch-continuous-integration-for-patches/

Also the thing is where to get jenkins instance: https://ci.opensuse.org is dead.

[pevik]

Current (April 8, 2025) users of tags:
https://patchwork.kernel.org/project/netdevbpf/list/
https://patchwork.kernel.org/project/netdevbpf/patch/20250408081958.289773-1-jiawenwu@trustnetic.com/

also on our patchwork instance (done by Rob Herring?):
https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250407223714.2287202-2-sean.anderson@linux.dev/

[pevik]

@acerv started working on it, he already has some nice results:
https://patchwork.ozlabs.org/project/ltp/patch/20250409-ci_testing_branch-v1-1-ccea0cdf0781@suse.com/
https://patchwork.ozlabs.org/project/ltp/patch/20250409-fix_make_clean-v3-2-a33a84b2be05@suse.com/