On 08/12/2018 08:42 PM, Shyam Ranganathan wrote: > As a means of keeping the focus going and squashing the remaining tests > that were failing sporadically, request each test/component owner to, > > - respond to this mail changing the subject (testname.t) to the test > name that they are responding to (adding more than one in case they have > the same RCA) > - with the current RCA and status of the same > > List of tests and current owners as per the spreadsheet that we were > tracking are: > > ./tests/bugs/bug-1110262.t TBD The above test fails as follows, Run: https://build.gluster.org/job/line-coverage/427/consoleFull Log snippet: (retried and passed so no further logs) 18:50:33 useradd: user 'dev' already exists 18:50:33 not ok 13 , LINENUM:42 18:50:33 FAILED COMMAND: useradd dev 18:50:33 groupadd: group 'QA' already exists 18:50:33 not ok 14 , LINENUM:43 18:50:33 FAILED COMMAND: groupadd QA Basically, the user/group existed and hence the test failed. Now, I tried getting to the build history of the machine that failed this test, but Jenkins has not been cooperative, this was in an effort to understand which previous run failed. Also one other test case uses the same user and group names, tests/bugs/bug-1584517.t, but that runs after this test. So I do not know how that user and group name leaked, due to which this test case failed. Bug filed: https://bugzilla.redhat.com/show_bug.cgi?id=1615604 Shyam _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
