|Summary:||Is fstat.gluster.org capturing all the regression failures?|
|Product:||[Community] GlusterFS||Reporter:||Atin Mukherjee <amukherj>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:|
|Version:||mainline||CC:||bugs, gluster-infra, nigelb, ppai|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-04-18 07:37:26 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Atin Mukherjee 2018-04-17 15:32:56 UTC
Description of problem: https://build.gluster.org/job/centos7-regression/712/console <-- failed today tests/00-geo-rep/00-georep-verify-setup.t failing but https://fstat.gluster.org/summary?start_date=2018-04-16&end_date=2018-04-17&branch=master doesn't capture it.. I am pretty sure today we have definitely more than 10 regression failures..
Comment 1 Nigel Babu 2018-04-18 00:10:26 UTC
We don't seem to catch timeout related test failure. However, the other point is that you would not have seen this yesterday in any case. The cron runs at 0100 UTC. This is 0530 IST, so the updates are not real time. They're offset by about 24h. I'll keep this bug open to track timeout related failures.
Comment 2 Prashanth Pai 2018-04-18 03:35:22 UTC
+1 I saw this too. ./tests/00-geo-rep/00-georep-verify-setup.t failed multiple times. I couldn't find it on fstat.gluster.org
Comment 3 Nigel Babu 2018-04-18 07:37:26 UTC
We're now capturing timeout-related failures as well.