Bug 1497803 - fstat missing failures when filtering?
Summary: fstat missing failures when filtering?
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-02 17:28 UTC by Shyamsundar
Modified: 2018-08-13 04:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-13 04:06:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Shyamsundar 2017-10-02 17:28:53 UTC 
So, when I check 30 days of failure in 3.10 branch: https://fstat.gluster.org/summary?start_date=2017-08-30&end_date=2017-09-30&branch=release-3.10

I get, just 2 failures in NetBSD.

But, this run: https://build.gluster.org/job/centos6-regression/6423/consoleFull
Date: Fri Sep 15 09:26:56 UTC 2017

Is not reported, which it should.

Request you to look into it, to see if this is a bug and needs fixing.
Comment 1 Nigel Babu 2018-08-13 04:06:48 UTC 
I'm going to close this for now in favor of an fstat bug https://github.com/gluster/fstat/issues/45
Note You need to log in before you can comment on or make changes to this bug.