On Thu, Apr 14, 2016 at 10:13 AM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
I am pretty sure that earlier we used to log the culprit test generating
the core. But now I don't see that same behavior in these runs [1] [2]
[1]
https://build.gluster.org/job/rackspace-regression-2GB-triggered/19709/consoleFull
[2]
https://build.gluster.org/job/rackspace-regression-2GB-triggered/19720/consoleFull
These runs are from 3.7 release branch and not all the test framework improvements have been backported there.
I have a patch [1] which backports every change under tests/ dir but it is failing because some of the required code changes have not been backported.
For this particular crash that you are observing, the test which generates the core is ./tests/basic/tier/tier-file-create.t. How to determine? Well, based on core name which has PID and then look into messages or logs to see what was happening during that time.
The cause of the crash has been documented well in the bug [2] and a partial fix [3] by Pranith is available.
Pranith,
With respect to dict_foreach problem you mention, won't taking a lock in dict_foreach solve the problem?
~Atin
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
