Description of problem:
./tests/bugs/bug-918437-sh-mtime.t failed on gluster build system with the following error :
stat: cannot stat `/d/backends/gfs0/brick02/b': No such file or directory
[11:16:05] ./tests/bugs/bug-918437-sh-mtime.t ................
It seems that file being checked after performing self heal is wrong.
Test Summary Report
./tests/bugs/bug-918437-sh-mtime.t (Wstat: 0 Tests: 37 Failed: 1)
Failed test: 37
Files=271, Tests=7911, 4619 wallclock secs ( 2.95 usr 1.75 sys + 426.03 cusr 593.78 csys = 1024.51 CPU)
++ ls -l '/core.*'
++ wc -l
+ '[' 0 '!=' 0 ']'
+ '[' 1 -ne 0 ']'
+ tar -czf /archives/logs/glusterfs-logs-20140805:10:09:52.tgz /var/log/glusterfs
tar: Removing leading `/' from member names
+ echo Logs archived in http://slave24.cloud.gluster.org/logs/glusterfs-logs-20140805:10:09:52.tgz
Logs archived in http://slave24.cloud.gluster.org/logs/glusterfs-logs-20140805:10:09:52.tgz
+ exit 1
+ '[' 1 = 0 ']'
+ ssh email@example.com gerrit review --message ''\''http://build.gluster.org/job/rackspace-regression-2GB-triggered/688/consoleFull : FAILED'\''' --project=glusterfs --verified=-1 --code-review=0 843c006d2ba4a58fa04ba1e040467f9d06954ced
+ exit 1
Build step 'Execute shell' marked build as failure
Version-Release number of selected component (if applicable):
Regression test by gluster bulid system
Steps to Reproduce:
REVIEW: http://review.gluster.org/8465 (tests: trigger entry heals by lookup) posted (#1) for review on master by Ravishankar N (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/8465 committed in master by Pranith Kumar Karampuri (email@example.com)
Author: Ravishankar N <firstname.lastname@example.org>
Date: Wed Aug 13 10:17:50 2014 +0530
tests: trigger entry heals by lookup
Trigger entry heals explicitly by lookup until heal full is fixed in
afr v2 to do conservative merge.
Signed-off-by: Ravishankar N <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Pranith Kumar Karampuri <email@example.com>
Tested-by: Pranith Kumar Karampuri <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.