tcpdump mailing list archives

Re: Selectively suppressing CI on some sites for a commit?


From: Guy Harris via tcpdump-workers <tcpdump-workers () lists tcpdump org>
Date: Thu, 6 Jan 2022 15:22:15 -0800

--- Begin Message --- From: Guy Harris <gharris () sonic net>
Date: Thu, 6 Jan 2022 15:22:15 -0800
On Jan 6, 2022, at 3:00 PM, Denis Ovsienko via tcpdump-workers <tcpdump-workers () lists tcpdump org> wrote:

On Thu, 6 Jan 2022 14:11:54 -0800 Guy Harris via tcpdump-workers <tcpdump-workers () lists tcpdump org> wrote:

I've just updated the libpcap .appveyor.yml to get Npcap from
npcap.com (the Npcap site has been moved there); I added [skip
cirrus] to skip Cirrus CI for that change, and it appears to work.

That's nice to know.  Either this is a relatively recent skip pattern in
Cirrus CI, or I didn't notice it before (see my message to the list
from 21 August 2020).

...or it doesn't work, even though the CI page on tcpdump.org didn't show the builds as being in progress.  It looks as 
if the libpcap builds *did* occur, and a tcpdump build (with the equivalent .appveyor.yml update) is in progress.

Do you think https://www.tcpdump.org/ci.html should document [skip cirrus] and [skip appveyor]?

[skip appveyor], possibly.  [skip cirrus], no, as my inference that it worked appears to be wrong.

Are there other comments to add to suppress OpenCSW CI and to
suppress the other CI sites that have been set up?  The only one I
want *not* suppressed is AppVeyor.

Not immediately, or not at all.  However, there are only two Buildbot
places where all skip patterns are processed (or not).

ci.tcpdump.org recognizes [skip ci] because that's the default
behaviour in that version of Buildbot.  Following the documentation,
several months and Buildbot versions ago I tried adding [skip buildbot]
to the list of skip patterns, but for some reason it had no effect
(could be a user error or a bug). Would it help to try again?

I tried it with the tcpdump build, and it *appears* to work with the Tcpdump Group buildbots (the RISC-V one is 
running, but it's still working on a build from a change François submitted 3 hours ago, so it hasn't even started my 
change; that buildbot appears not to be the fastest computer in existence, shall we say).

I am not familiar with OpenCSW Buildbot setup, but from the build
history it is obvious it disregards [skip ci], so it looks likely it
would disregard [skip buildbot] too.

It appears to disregard it.

--- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Current thread: