ABCDEFGHIJKLMNOPQR
1
Last Updated:
21:00 EDT 08-Aug-2018
2
Link to see which runs failed:
See sheet "Run failures" "Patch set 9"
3
Line-coverage failures are not captured in fstat, see sheet named "Nightly line-coverage" for the same
4
Reviews posted and open:
https://review.gluster.org/#/q/starredby:srangana%2540redhat.com
5
Failing/Retrying test casesBZ#OwnerStatusAdditional comments
6
NEW FAILURES
7
./tests/basic/distribute/rebal-all-nodes-migrate.tTBD
8
./tests/basic/tier/tier-heald.tTBD
Core dumped (looks similar to ./tests/bugs/glusterd/remove-brick-testcases.t (run: lcov#432) core
9
./tests/basic/afr/sparse-file-self-heal.tTBD
10
./tests/bugs/shard/bug-1251824.tTBD
11
./tests/bugs/shard/configure-lru-limit.tTBD
12
./tests/bugs/replicate/bug-1408712.t1615078Ravi
https://review.gluster.org/#/c/glusterfs/+/20708/
13
./tests/basic/afr/replace-brick-self-heal.t1615239Ravi
https://review.gluster.org/#/c/glusterfs/+/20717/
14
./tests/00-geo-rep/00-georep-verify-setup.t
1610405, 1614799
Kotresh
Patch1 (https://review.gluster.org/20601/): Merged
Patch2 (https://review.gluster.org/20704/) : Patch sent
[Kotresh] The issue is root caused. There is a race which could cause deadlock while updating monitor status file which uses fcntl locks. I am working on the patch and will update on it.
15
./tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.tKarthik
https://review.gluster.org/#/c/glusterfs/+/20722/
Single retry occurance
16
./tests/basic/stats-dump.tTBDSingle retry occurance
17
./tests/bugs/bug-1110262.tTBDSingle retry occurance
18
./tests/basic/ec/ec-data-heal.tMohithttps://review.gluster.org/20657
Most probably will be addressed through https://review.gluster.org/20657 . +moagrawa@redhat.com
19
./tests/bugs/replicate/bug-1448804-check-quorum-type-values.tPranithhttps://review.gluster.org/c/glusterfs/+/20697[Ravi] @pranith.k@gmail.com Has sent https://review.gluster.org/c/glusterfs/+/20697 for the test
20
./tests/bugs/snapshot/bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.tTBDOccured twice
21
./tests/basic/ec/ec-5-2.tSunilCore dumping in mux runs (twice)
22
./tests/bugs/shard/bug-shard-discard.tTBDSingle retry occurance
23
./tests/bugs/glusterd/remove-brick-testcases.tTBDcore dumped
24
./tests/bugs/protocol/bug-808400-repl.tTBD[Atin] +chenk@redhat.com Seems like a fuse crash, https://build.gluster.org/job/regression-on-demand-multiplex/195/consoleFull
25
./tests/bugs/quick-read/bug-846240.tDu
[Du] Fix submitted at: https://review.gluster.org/#/c/glusterfs/+/20710/
Sleep of 10 after opening the fd in the test reproduces the failure always
26
EXISTING FAILURES
27
./tests/bugs/replicate/bug-1290965-detect-bitrotten-objects.tMohit[Ravi] Crash is due to accessing an empty linked list in changelog_destroy_rpc_listner(). Mohit Agarwal will be fixing it.
28
./tests/00-geo-rep/georep-basic-dr-tarssh.t
1610405, 1614799
Kotresh
Patch1 (https://review.gluster.org/20601/): Merged
Patch2 (https://review.gluster.org/20704/) : Patch sent
[Kotresh] The issue is root caused. There is a race which could cause deadlock while updating monitor status file which uses fcntl locks. I am working on the patch and will update on it.
29
./tests/bugs/ec/bug-1236065.tPranith
https://review.gluster.org/#/c/glusterfs/+/20685
30
./tests/00-geo-rep/georep-basic-dr-rsync.t
1610405, 1614799
Kotresh
Patch1 (https://review.gluster.org/20601/): Merged
Patch2 (https://review.gluster.org/20704/) : Patch sent
[Kotresh] The issue is root caused. There is a race which could cause deadlock while updating monitor status file which uses fcntl locks. I am working on the patch and will update on it.
31
./tests/basic/ec/ec-1468261.tAshishLooks similar to the kill brick restart volume, connection issue https://lists.gluster.org/pipermail/gluster-devel/2018-August/055167.html
32
./tests/basic/afr/add-brick-self-heal.tRavi
https://review.gluster.org/#/c/glusterfs/+/20696/
[Ravi] Sent https://review.gluster.org/#/c/glusterfs/+/20696/ as a potental fix.
33
./tests/basic/afr/granular-esh/replace-brick.tPranithhttps://review.gluster.org/c/glusterfs/+/20681/https://review.gluster.org/c/glusterfs/+/20681/
34
./tests/bugs/core/multiplex-limit-issue-151.tSanjuUnder watchthis test case failed twice and its timeout both the times. It can be because of https://review.gluster.org/#/c/20584/
35
./tests/bugs/glusterd/validating-server-quorum.tAtin
https://review.gluster.org/#/c/glusterfs/+/20693/
[Atin] Posted a new patch https://review.gluster.org/#/c/glusterfs/+/20693/ . Ran lcov 6 times with the changes and haven't seen the test crashing yet.
36
./tests/bugs/replicate/bug-1363721.tRavi[ravi] The check that failed is apparently the client and shd failing to connect to a previously killed brick after a volume start force.
37
./tests/bugs/index/bug-1559004-EMLINK-handling.tPranith[Pranith] Timeout increased
38
./tests/bugs/replicate/bug-1433571-undo-pending-only-on-up-bricks.tKarthik
https://review.gluster.org/#/c/glusterfs/+/20701/
[Karthik] Patch submitted: https://review.gluster.org/#/c/glusterfs/+/20701/
39
NOT OCCURING ANYMORE
40
./tests/bugs/glusterd/add-brick-and-validate-replicated-volume-options.tAtinhttps://review.gluster.org/20651Still happens in Mux
41
./tests/bugs/glusterd/rebalance-operations-in-single-node.tTBDPending analysis
42
./tests/bugs/replicate/bug-1386188-sbrain-fav-child.tTBDPending analysis
43
./tests/bitrot/bug-1373520.t1611566Kotreshhttps://review.gluster.org/#/c/20619/https://review.gluster.org/#/c/20619/
44
./tests/bugs/distribute/bug-1117851.t1608564Shyam/Nigel
https://review.gluster.org/c/glusterfs/+/20648 https://review.gluster.org/c/build-jobs/+/20655
(Nithya) Timeout is close to 200 in lcov tests, changing the same
45
./tests/bugs/glusterd/quorum-validation.t1603063AtinPatch posted, pending reviewThis is true for validating-server-quorum.t, I don't have the root cause for quorum-validation.t failure yet.
46
./tests/bugs/distribute/bug-1042725.tShyamFailures are due to cleanup failures in previous test that fails "./tests/bugs/core/multiplex-limit-issue-151.t"
47
./tests/bugs/replicate/bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.tKarthikPatch posted, pending reviewPosted patches seem to address the issue
48
./tests/bugs/quota/bug-1293601.tTBDRCA Pending
49
./tests/bugs/bug-1368312.tNADuMarked BadMarked bad on Aug-02-2018: https://review.gluster.org/#/c/20549/
50
./tests/bugs/distribute/bug-1122443.tDu(reverted) https://review.gluster.org/16419Introduced by patch: https://review.gluster.org/16419
51
./tests/bugs/core/bug-1432542-mpx-restart-crash.t1608568Nithya/Shyamhttps://review.gluster.org/#/c/20568[Nithya] One of these failures was an oom kill
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100