On 08/11/2018 12:43 AM, Mohit Agrawal wrote: > File a bug https://bugzilla.redhat.com/show_bug.cgi?id=1615003, I am not > able to extract logs > specific to this test case from the log dump. 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 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. Finally, I do not see an infra bug in this. (updated the bug as well) > > > Thanks > Mohit Agrawal > > On Sat, Aug 11, 2018 at 9:27 AM, Atin Mukherjee <amukherj@xxxxxxxxxx > <mailto:amukherj@xxxxxxxxxx>> wrote: > > https://build.gluster.org/job/line-coverage/455/consoleFull > <https://build.gluster.org/job/line-coverage/455/consoleFull> > > 1 test failed: > tests/bugs/core/multiplex-limit-issue-151.t (timed out) > > The last job > https://build.gluster.org/job/line-coverage/454/consoleFull > <https://build.gluster.org/job/line-coverage/454/consoleFull> took > only 21 secs, so we're not anyway near to breaching the threshold of > the timeout secs. Possibly a hang? > > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > https://lists.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
