----- Original Message ----- > From: "Dan Kenigsberg" <dan...@redhat.com> > To: from...@redhat.com, smizr...@redhat.com, ybron...@redhat.com > Cc: ee...@redhat.com, aba...@redhat.com, vdsm-patches@lists.fedorahosted.org, > dc...@redhat.com, lara...@redhat.com, > fsimo...@redhat.com > Sent: Friday, May 30, 2014 3:00:26 PM > Subject: Re: [oVirt Jenkins] vdsm_master_unit_tests - Build # 3043 - Failure! > > Francesco, Yaniv, > > Have you found the time to dig into the coredump > of these Segmentation faults? > > (It is unrelated to Liron's new patches)
No much progress since last report. I'm very annoyed by this issue but I'm having hard time wrapping my head around it. Let me summarize what I currently know: * the segfault should be reproduceable on any box running nose >= 1.3.0, just using $ cd vdsm $ ./configure && make $ NOSE_WITH_XUNIT=1 make check or at least I can reproduce the issue on all the boxes I tried locally (vanilla F20, F19) * if we run each testunit separately, we do NOT observe the failure. This triggers the segfault: $ cd tests $ ./run_tests_local.sh ./*.py This does not: $ cd tests $ for TEST in `ls ./*.py`; do ./run_tests_local.sh $TEST; done * the stack traces I observed are huge, more than 750 levels deep. This suggests the stack exausted, and this in turn probably triggered by some kind of recursion gone wild. Note the offending stack trace is just on one thread; all the others are quiet. * I tried to reproduce the issue with a simpler use case with no luck so far. At the moment I don't have better suggestions than bite the bullet and dig in the huge stack trace looking for repetitive patterns or some sort of hint. Suggestions welcome! -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani _______________________________________________ vdsm-patches mailing list vdsm-patches@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-patches
