Hello. I have encountered a false Verified+1 (again) caused by a naginated retry effectively removing non-naginated failure.
The mechanism is basically the same as the one described in this [0] older e-mail. Consensus then was that VIRL tests are unreliable, but false +1 is caused by inconsistent use of naginator. Either all verify jobs should use naginator (with identical settings), or no verify job should use it. I have prepared a Change [1] to remove naginator from all verify jobs (keeping it in merge jobs). Vratko. [0] https://lists.fd.io/g/vpp-dev/message/9837 [1] https://gerrit.fd.io/r/16583
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11754): https://lists.fd.io/g/vpp-dev/message/11754 Mute This Topic: https://lists.fd.io/mt/28819751/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
