Ah, okay, I didn't realize it's expected for Jenkins to vote in the code-review field for unstable jobs. That put me in a prospective of also doubting the +2, since I expected a non-author's review to go into the Non-Author-Code-Review field, not Code-Review field but also set Non-Author flag.
Anyway, nevermind then, the root is the same 504 error Anil is already looking at. Thanks, Daniel On Tue, Dec 4, 2018 at 3:18 PM Thanh Ha via RT <[email protected]> wrote: > On Tue Dec 04 08:20:00 2018, [email protected] wrote: > > Hello, > > > > I'm seeing some very strange Gerrit voting bugs in the last few hours. > > > > * My +2 on a patch I have nothing to do with is in Code-Review, not > > Non-Author-Code-Review, flag > > * Jenkins verify -1 is also in Code-Review flag, not Verified flag > > > > https://git.opendaylight.org/gerrit/#/c/78391/ > > > > Thanks, > > Daniel > > Hi Daniel, > > I don't see anything wrong here. Your +2 vote is satisfying the Non-Author > check so things are normal here. > > As for Jenkins voting -1 in CR. This happens when a job is UNSTABLE rather > than failed. I saw Anil was investigating some Nexus issues earlier today > and seems like the job was affected by the Nexus infra issues that were > happening earlier. > > The build itself was successful, but at the end of the build logs failed > to deploy to Nexus which caused Jenkins to mark the job as UNSTABLE rather > than failed. > > Regards, > Thanh > > _______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
