[lttng-dev] [PATCH lttng-ust v2] Fix: allocate ts_end in ringbuffer shared memory
jonathan.rajotte-julien at efficios.com
Fri May 10 14:19:50 EDT 2019
> > This is probably an artefact but all your path have 2.9 in them. This work is
> > done against master of lttng-tools and lttng-ust.
> > Our CI does not indicate any failure for the master branches. 
> > 
> A bit quick on the send email on that one.
> Our ci currently indicate failure for the master branch but nothing during the
> build process (at make check).
Again not true, failures are related to urcu.
I'll go get some coffee clearly need it.
More information about the lttng-dev