[Gluster-infra] [Bug 1600963] New: get the failed test details into gerrit output itself
https://bugzilla.redhat.com/show_bug.cgi?id=1600963 Bug ID: 1600963 Summary: get the failed test details into gerrit output itself Product: GlusterFS Version: mainline Component: project-infrastructure Severity: high Priority: high Assignee: b...@gluster.org Reporter: atumb...@redhat.com CC: amukh...@redhat.com, b...@gluster.org, gluster-infra@gluster.org, j...@pl.atyp.us, srang...@redhat.com # Description of problem: It would be great to get all the tests which failed in regression in gerrit output, instead of just SUCCESS or FAILURE. # Additional info: This helps the people to notice the failures in gerrit, without going out to build output (which not many people do). -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=40Ei63jKLa&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Haplometrosis.rht has a bad disk
Le jeudi 12 juillet 2018 à 23:46 +0200, Michael Scherer a écrit : > Hi, > > so I leared that haplometrosis, one of our 4 servers in the DC in > Raleigh has a disk issue: > > [ +0,002407] megaraid_sas :02:00.0: 28562 > (583673351s/0x0001/CRIT) > - VD 01/1 is now DEGRADED > [ +0,002694] megaraid_sas :02:00.0: 28564 > (583673351s/0x0001/CRIT) > - Consistency Check failed on VD 01/1 > [juin30 11:30] megaraid_sas :02:00.0: 28568 > (583673536s/0x0002/CRIT) - Diagnostics failed for PD 12(e0x00/s10) > > hopefully, the server is still working fine thanks to the magic of > raid, I will diagnose that later and see if we have to change a drive > or something. > > The server is running only softserve and fstat, and 20 builders. So I > will likely have to reboot it a bit, but it shouldn't affect > operations > too much. So, the super micro interface show 1 bad disk listed as "not configured". Supermicro interface being usually slightly rage inducing, I am not sure if that's one of the spare disk, or another one. I will dig further, but for now, it seems not being a big issue at all. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS signature.asc Description: This is a digitally signed message part ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1600963] get the failed test details into gerrit output itself
https://bugzilla.redhat.com/show_bug.cgi?id=1600963 --- Comment #1 from Shyamsundar --- There are several bugs of the same nature #1576161 and #1570576. I am thinking that we need a generic request/action to post failure onto gerrit itself, rather than having to goto Jenkins. Now, this may help for some cases, and in some other (possibly cores etc.) contributors would need to get to Jenkins, which is fine, but reduces the need to visit Jenkins. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=df3fIHdARw&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
