[Gluster-infra] [Bug 1615003] Not getting logs if test case is time out on build server
https://bugzilla.redhat.com/show_bug.cgi?id=1615003 Worker Ant changed: What|Removed |Added Status|NEW |CLOSED Resolution|--- |UPSTREAM Last Closed||2020-03-12 12:42:11 --- Comment #4 from Worker Ant --- This bug is moved to https://github.com/gluster/project-infrastructure/issues/22, and will be tracked there from now on. Visit GitHub issues URL for further details -- You are receiving this mail because: You are on the CC list for the bug. ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1615003] Not getting logs if test case is time out on build server
https://bugzilla.redhat.com/show_bug.cgi?id=1615003 Nigel Babu changed: What|Removed |Added Component|project-infrastructure |tests Flags|needinfo?(nig...@redhat.com | |) | --- Comment #3 from Nigel Babu --- This is not an infra bug. Going to move this over to tests. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4GlgeUxkJR=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1615003] Not getting logs if test case is time out on build server
https://bugzilla.redhat.com/show_bug.cgi?id=1615003 Shyamsundar changed: What|Removed |Added CC||srang...@redhat.com --- Comment #2 from Shyamsundar --- This is because the test is calling cleanup twice in its exit bash traps. - First, the test itself sets a trap to cleanup at https://github.com/gluster/glusterfs/blob/master/tests/bugs/core/multiplex-limit-issue-151.t#L30 - There is an additional trap set to cleanup in include.rc, https://github.com/gluster/glusterfs/blob/master/tests/include.rc#L719 The tar ball is generated in the cleanup routine, and also ensures that on content in the tar balls is between 2 invocations. Thus, calling cleanup twice will result in an empty tarball. This can be seen running the test locally as, `./tests/bugs/distribute/bug-1042725.t` There are a few things in that test we need clarified, 1. why trap this: https://github.com/gluster/glusterfs/blob/master/tests/bugs/core/multiplex-limit-issue-151.t#L29 2. Why trap cleanup, rather than invoke it at the end of the test as is normal Also, in the merged patch sets 2/4/6/7/8 (of [1]) I had added a cleanup at the end (as I traced the failure of ./tests/bugs/distribute/bug-1042725.t to incorrect cleanup by the previous test (or timeout in cleanup)). I did not do the same in patch set 9. So, I will post a patch that removes the traps set by this test (so we get logs from this test), and hence add the manual cleanup at the end of the test. (see bug#1615037 for the same) Finally, I do not see an infra bug in this. [1] https://review.gluster.org/c/glusterfs/+/20637 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Zd1jnsVEpJ=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1615003] Not getting logs if test case is time out on build server
https://bugzilla.redhat.com/show_bug.cgi?id=1615003 Atin Mukherjee changed: What|Removed |Added CC||amukh...@redhat.com, ||nig...@redhat.com Flags||needinfo?(nig...@redhat.com ||) Severity|unspecified |high --- Comment #1 from Atin Mukherjee --- Any specific reason why in case of time out we've not taken a dump of all the log files? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fnf299EEOL=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-infra
