We have a set of 4 cores which seem to originate from 2 bugs as filed and referenced below. Bug 1: https://bugzilla.redhat.com/show_bug.cgi?id=1636570 Cleanup sequence issues in posix xlator. Mohit/Xavi/Du/Pranith are we handling this as a part of addressing cleanup in brick mux, or should we? Instead of piece meal fixes? Bug 2: https://bugzilla.redhat.com/show_bug.cgi?id=1637743 Initial analysis seems to point to glusterd starting the same brick instance twice (non-mux case). Request GlusterD folks to take a look. 1) Release-5 Link: ttps://build.gluster.org/job/nightly-release-5/ Failures: a) https://build.gluster.org/job/regression-test-with-multiplex/886/consoleText - Bug and RCA: https://bugzilla.redhat.com/show_bug.cgi?id=1636570 2) Master Link: https://build.gluster.org/job/nightly-master/ Failures: a) Failed job line-coverage: https://build.gluster.org/job/line-coverage/530/consoleText - Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1637743 (initial analysis) - Core generated - Test: ./tests/bugs/snapshot/bug-1482023-snpashot-issue-with-other-processes-accessing-mounted-path.t b) Failed job regression: https://build.gluster.org/job/regression-test-burn-in/4127/consoleText - Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1637743 (initial analysis) (same as 2.a) - Core generated - Test: ./tests/bugs/glusterd/quorum-validation.t c) Failed job regression-with-mux: https://build.gluster.org/job/regression-test-with-multiplex/889/consoleText - Bug and RCA: https://bugzilla.redhat.com/show_bug.cgi?id=1636570 (same as 1.a) - Core generated - Test: ./tests/basic/ec/ec-5-2.t NOTE: All night-lies failed in distributed-regression tests as well, but as these are not yet stable not calling these out. _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
