canonical-ci-engineering team mailing list archive

[James Henstridge <james.henstridge@xxxxxxxxxxxxx>]

On 12 December 2015 at 11:56, Michi Henning <michi.henning@xxxxxxxxxxxxx> wrote:
> This is definitely linked to cyclops-node13.
>
> I’ve done a whole bunch of builds. The same test fails whenever it runs on
> cyclops-node13 and passes whenever it gets a builder other than 13.
>
> Michi.
>
>
> On 12 Dec 2015, at 11:16 , Michi Henning <michi.henning@xxxxxxxxxxxxx>
> wrote:
>
> I rebuild the branch without change, and it passed this time on
> cyclops-node09:
>
> http://s-jenkins.ubuntu-ci:8080/job/thumbnailer-devel-vivid-armhf-ci/271/consoleFull
>
> Another branch (no difference with respect to this test) failed, again on
> cyclops-node13:
>
> http://s-jenkins.ubuntu-ci:8080/job/thumbnailer-devel-vivid-armhf-ci/270/consoleFull
>
> Cheers,
>
> Michi.
>
>
> On 12 Dec 2015, at 10:48 , Michi Henning <michi.henning@xxxxxxxxxxxxx>
> wrote:
>
> Hi guys,
>
> we have seen this particular failure several times in the past two weeks,
> and it has just happened again.
>
> https://jenkins.qa.ubuntu.com/job/thumbnailer-devel-xenial-armhf-ci/20/consoleFull
>
> We don’t see this on each build, just occasionally.
>
> Test 8 fails with:
>
> 8: Test command: /usr/bin/xvfb-run "-a" "-s" "-screen 0 800x600x24"
> "./qml_test" "-import"
> "/tmp/buildd/thumbnailer-2.3+16.04.20151102.2bzr311pkg0xenial20/obj-arm-linux-gnueabihf/plugins"
> 8: Test timeout computed to be: 1500
> 8: QXcbConnection: Could not connect to display :109
> 8: Aborted
>  8/22 Test  #8: qml .........................................***Failed
> 0.23 sec
> QXcbConnection: Could not connect to display :109
> Aborted
>
>
> The test runs some qml that displays various images by writing to a canvas,
> and we test that the images appear as expected by testing various pixel
> values.
>
> This test has worked without failing for several months, which makes me
> suspect that something may be wrong with the builder.

So, looking at the xvfb-run man page, it sends the X server logs to
/dev/null by default:

       -e file, --error-file=file
              Store output from xauth  and  Xvfb  in  file.   The  default  is
              /dev/null.

We should adjust the test to do something useful with those logs (e.g.
print them out if the test fails).  Presumably the cause of the test
failure will be obvious once we can see that.

James.