Wireshark mailing list archives
Re: Why is conflict check on the buildbot green?
From: Gerald Combs <gerald () wireshark org>
Date: Mon, 6 Jul 2020 10:20:28 -0700
On 7/4/20 11:52 PM, Jaap Keuter wrote:
Hi, Due to some recent issues with DHCPv6 the buildbot began flagging the 'conflict check' stage as failed. This drew my attention to the fact that there is a long list of warnings in there about wrong use of protocol fields, but once the DHCPv6 issues were fixed the build happily went back to green for the ‘conflict check’. Why is is not orange with the warning output?
Buildbot uses regexes to check for warning output, and only does so for a specific type of build step. I've updated the 'conflict check' step to look for warnings. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Why is conflict check on the buildbot green? Jaap Keuter (Jul 04)
- Re: Why is conflict check on the buildbot green? Alexis La Goutte (Jul 05)
- Re: Why is conflict check on the buildbot green? Jaap Keuter (Jul 05)
- Message not available
- Re: Why is conflict check on the buildbot green? Jaap Keuter (Jul 05)
- Re: Why is conflict check on the buildbot green? Martin Mathieson via Wireshark-dev (Jul 05)
- Re: Why is conflict check on the buildbot green? Guy Harris (Jul 05)
- Re: Why is conflict check on the buildbot green? Martin Mathieson via Wireshark-dev (Jul 06)
- Re: Why is conflict check on the buildbot green? Jaap Keuter (Jul 05)
- Re: Why is conflict check on the buildbot green? Alexis La Goutte (Jul 05)