On quarta-feira, 27 de julho de 2016 09:53:32 PDT Jędrzej Nowacki wrote:
> No, the machine gets destroyed after test failure. Normally gdb session is
> attached to crashing process, that was not the case for some odd reason.
> Can it be that QTestLib is crashing too?
There have been tools to collect core dumps for years. The modern choice is
systemd-coredump, which automatically logs and compresses them for you. The CI
system should ask coredumpctl for all core dumps that were created after the
build started, then transfer them out before the machine is destroyed (it's
easier to do that
A lot of information is logged on the journal. Just run:
journalctl -o json /usr/lib/systemd/systemd-coredump
(use "-o verbose" to read more easily)
It's easier to filter if the build is run in a separate slice or cgroup.
Otherwise, filter by UID or write a simple journal walker that executes a more
complex match.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
