[Gluster-devel] tests/basic/tier/tier.t failure in NetBSD

Joseph Fernandes josferna at redhat.com
Sun Feb 28 11:18:37 UTC 2016

Hi All,

1. record-metadata-heat.t is already added to bad test: As far as the feature goes its just test the switch
   on the recording of metadata heat. We are aware of the issue here its not the feature but the timing that is used in the test.
   We will be working on it once our priority list of things are addressed.
2. I just had a look at the tier.t failure case. The tests fails at test 45. i.e detach command failure. We can have a look at it and will fix it.
3. Jeff could you please point us to the failure link of fops-during-migration-pause.t so that we can investigate.

Now about tiering test files. Most of the times the tiering tests have failed due to the timing issues of checking status.
i.e synchronizing when file gets promoted and demoted. and its very difficult to have this synchronized with the t file infra (tiering team can add more to this.)
But just to tell that user data is unsafe on this premise would not be correct, as any data loss or corruption or unavailability is already handled in the t files
of tiering.
We will put our best effort to tackle these issues asap.


----- Original Message -----
From: "Jeff Darcy" <jdarcy at redhat.com>
To: "Atin Mukherjee" <amukherj at redhat.com>
Cc: "Gluster Devel" <gluster-devel at gluster.org>
Sent: Sunday, February 28, 2016 3:43:20 PM
Subject: Re: [Gluster-devel] tests/basic/tier/tier.t failure in NetBSD

> The above test failed here [1]
> [1]
> https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/14590/consoleFull

I just got a similar failure on another (trivial) patch.


My failed-test-analysis script shows the following:

   nine more failures for tier.t
   two for fops-during-migration-pause.t
   one for record-metadata-heat.t

Failures from these tests outnumber failures from all other tests
combined, by a long shot, and I doubt that it's because *any* of the
patches that had to be re-tested had anything whatsoever to do with

I propose that tiering and its tests be disabled on NetBSD.  I doubt
that anybody uses the feature on that platform, and this frequency of
test failures suggests that their data would be at risk if they tried.
When tiering on Linux becomes stable, we can consider tiering on NetBSD
as a feature in a future release.
Gluster-devel mailing list
Gluster-devel at gluster.org

More information about the Gluster-devel mailing list