I attached the log for the failure (come from the build bot). About the double reporting, I seen it on one of the build bot, but we have some case when 2 different test have the same name what can explain the issue (e.g. TestFormattersBoolRefPtr)
Tamas On Wed, Sep 9, 2015 at 6:54 PM Zachary Turner <ztur...@google.com> wrote: > +Todd just in case this is related to his changes. We were seeing 1 or 2 > test failures double reporting on Windows after the patch, so I'm not sure > if it could be related. > > On Wed, Sep 9, 2015 at 10:37 AM Enrico Granata via lldb-commits < > lldb-commits@lists.llvm.org> wrote: > >> >> On Sep 9, 2015, at 5:10 AM, Tamas Berghammer <tbergham...@google.com> >> wrote: >> >> Hi Enrico, >> >> TestFormattersBoolRefPtr.py started to fail on the OSX buildbot. I think >> the first build where it is failed is >> http://lab.llvm.org:8011/builders/lldb-x86_64-darwin-13.4/builds/5522, >> but I am not sure as the bot is a bit unreliable. Can you take a look for >> it, or if not, then are you fine with XFAIL-ing it until it get fixed? >> >> Thanks, >> Tamas >> >> >> This test seems to pass fine on a ToT checkout for me, and the bot seems >> to just say the test failed with no log of the issue. Do you mind providing >> a log if you have one available? >> >> Thanks, >> *- Enrico* >> 📩 egranata@.com ☎️ 27683 >> >> _______________________________________________ >> lldb-commits mailing list >> lldb-commits@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits >> >
log
Description: Binary data
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
