[testsfail] Segmentation fault mir_demo_server --test-client /usr/bin/mir_demo_client_basic

*Possibly* related to another segfault on krillin: lp:1502782

Removing the other server graphics platforms mesa-kms and mesa-x11 before running the test will make this seg fault disappear..

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.18.0

Seen again here:

https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-touch/7135/consoleFull

The log above is slightly different it now also crashes inside the tests itself.. Which is not related to the change. I will see if I can still reproduce the problem on krillin.

Another instance:
http://s-jenkins.ubuntu-ci:8080/job/mir-mediumtests-runner-touch/7140/consoleFull

This indeed seems to be a different problem than the original bug since it happens much more often (always?) and affects more client runs.

Opened a new bug for it: https://bugs.launchpad.net/mir/+bug/1508478

Note that this bug still stands since the failure seen in https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-touch/7135/consoleFull is different from https://bugs.launchpad.net/mir/+bug/1508478

The log you mention also includes an acceptance test segmentation fault, which is new too..

@duflu do you need help reading logs?

Heh. Alf did the same thing in comment #7. And you really can't complain about those changes above that effectively changed nothing.

I'm still confused. And comment #9 didn't help me to become less confused.

We are still getting this:

https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-touch/7218/consoleFull

And here: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-touch/7220/consoleFull

Looking at https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-touch/ the odd recent success is mako, not krillin.

Switching to critical since this is now blocks (almost) all CI jobs from succeeding.

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.18.0

We have started seeing this again frequently enough to warrant restarting the investigation.

Just wondering if this has the same underlying cause as lp:1513901 - it seems to be in the same (shutdown) area.

Fix committed into lp:mir at revision 3124, scheduled for release in mir, milestone 0.18.0

This bug was fixed in the package mir - 0.18.0+16.04.20151216.1-0ubuntu1

---------------
mir (0.18.0+16.04.20151216.1-0ubuntu1) xenial; urgency=medium

  [ Kevin DuBois ]
  * New upstream release 0.18.0 (https://launchpad.net/mir/+milestone/0.18.0)
    - ABI summary: Only servers need rebuilding;
      . Mirclient ABI unchanged at 9
      . Mirserver ABI bumped to 36
      . Mircommon ABI unchanged at 5
      . Mirplatform ABI unchanged at 11
      . Mirprotobuf ABI unchanged at 3
      . Mirplatformgraphics ABI bumped to 7
      . Mirclientplatform ABI unchanged at 3
      . Mirinputplatform ABI added. Current version is 4
    - Enhancements:
      . Use libinput by default, and remove the android input stack
      . Add x11 input probing
      . Add alternative buffer swapping mechanism internally, available with
        --nbuffers 0
      . Automatic searching and selection of input platforms
      . Better support for themed cursors
      . Add demo client that uses multiple buffer streams in one surface
      . Improve fingerpaint demo to use touch pressure
      . Allow for configuring cursor acceleration, scroll speed and left or
        right handed mice
      . Allow for setting a base display configuration via client api
      . Various nested server multimonitor fixes and stability improvements
      . Remove DepthId from the SurfaceStack
    - Bug fixes:
      . Unit test failures in Display.* on Android (LP: #1519276)
      . Build failure due to missing dependency of client rpc code on mir
        protobuf (LP: #1518372)
      . Test failure in
        NestedServer.display_configuration_reset_when_application_exits
        (LP: #1517990)
      . CI test failures in various NesterServer tests (LP: #1517781)
      . FTBFS with -DMIR_PLATFORM=android (LP: #1517532)
      . Nesting Mir servers with assorted display configs causes lockup
        (LP: #1516670)
      . [testsfail] RaiseSurfaces.motion_events_dont_prevent_raise
        (LP: #1515931)
      . CI test failures in GLMark2Test (LP: #1515660)
      . Shells that inject user input events need to agree with the system
        compositor on the clock to use (LP: #1515515)
      . mircookie-dev is missing nettle-dev dependency (LP: #1514391)
      . Segmentation fault on server shutdown with mesa-kms (LP: #1513901)
      . mircookie requires nettle but libmircookie-dev doesn't depend on it
        (LP: #1513792)
      . libmircookie1 package does not list libnettle as dependency
        (LP: #1513225)
      . display configuration not reset when application exits (LP: #1511798)
      . unplugging external monitor causes nested server to throttle client
        (LP: #1511723)
      . 1/2 screen on external monitor (LP: #1511538)
      . unity-system-compositor crash, no interaction on windowed mode
        (LP: #1511095)
      . [regression] arm64/powerpc cross compile doesn't build any more
        (LP: #1510778)
      . mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
        RTLD_LAZY (LP: #1510218)
      . [multimonitor] nested server surface positioning incorrect
        (LP: #1506846)
      . unity-system-compositor fails to build against lp:mir r3027
   ...