[Pkg-giraffe-discuss] more automated testing on kopano* packages?
Guido Günther
agx at sigxcpu.org
Tue Dec 27 20:29:38 UTC 2016
On Tue, Dec 27, 2016 at 09:26:33PM +0100, Carsten Schoenert wrote:
> On 27.12.2016 14:03, Guido Günther wrote:
> > I have pushed a fix to kopancore on alioth that prevents the daemon from
> > starting when configured. The tests pass now but this does not look good:
> >
> > https://travis-ci.org/agx/kopanocore-debian/builds/186954826#L6166
> >
> > Since we're seeing it two times I assume it's kopano-admin crashing (but
> > returning with an exit code of zero nevertheless so it might happen in a
> > forke process).
>
> I see this too on my test pushes. The conatiner is using GCC 4.8.4,
> maybe it's also related to the "legacy" GCC collection.
Provide a link or or it didn't happen ;)
The docker container (if configured correctly) always uses the most
recent gcc from unstable:
https://travis-ci.org/agx/kopanocore-debian/builds/186999294#L288
> I never had this on my local testing in KVM image.
I've not seen this at kopano con either but I can reproduce it here with
my autopkgtest vm.
Cheers,
-- Guido
More information about the Pkg-giraffe-discuss
mailing list