The important fail (mir-wily-i386-ci and mir-mediumtests-builder-wily-armhf are marked non-fatal) is:
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/6749/consoleFull
... > creating: package_archive/archive/work/output/ > inflating: package_archive/archive/work/output/libmircookie-dev_0.16.0bzr2962pkg0wily4058+autopilot0_armhf.deb > inflating: package_archive/archive/work/output/mir-client-platform-mesa-dev_0.16.0bzr2962pkg0wily4058+autopilot0_armhf.deb
So these are *wily* debs? On a vivid+overlay image?
... > running mir_demo_server --test-client /usr/bin/mir_demo_client_basic > initctl: unable to determine sessions > initctl: unable to determine sessions > [1443083181.507545] mirplatform: Found graphics driver: android > [1443083181.508430] mirplatform: Found graphics driver: mesa-kms > [1443083181.508582] mirplatform: Found graphics driver: mesa-x11 > [1443083181.509131] mirplatform: Found graphics driver: dummy > [1443083181.513890] mirserver: Starting > [1443083181.514775] mircommon: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/server-platform > [1443083181.515171] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.5 > [1443083181.515294] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-mesa-kms.so.5 > [1443083181.515385] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/server-mesa-x11.so.5 > [1443083181.519473] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-evdev.so.2 > [1443083181.522828] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so > [1443083181.524689] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so > [1443083181.527313] mirplatform: Found graphics driver: android > [1443083181.527801] mirplatform: Found graphics driver: mesa-kms > [1443083181.527953] mirplatform: Found graphics driver: mesa-x11 > [1443083181.528228] mirplatform: Found graphics driver: dummy > [1443083181.529234] mirserver: Selected driver: android (version 0.16.0) > [1443083182.041171] mirserver: Initial display configuration: > [1443083182.045442] mirserver: 0.0: LVDS 4.7" 61x102mm > [1443083182.045686] mirserver: Current mode 768x1280 60.00Hz > [1443083182.045778] mirserver: Preferred mode 768x1280 60.00Hz > [1443083182.045839] mirserver: Logical position +0+0 > [1443083182.045930] mirserver: 0.1: unused DisplayPort > ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION) > Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE > std::exception::what: bind: No such file or directory
*Looks* like all clients are dying for lack of an endpoint.
« Back to merge proposal
The important fail (mir-wily-i386-ci and mir-mediumtests -builder- wily-armhf are marked non-fatal) is:
https:/ /jenkins. qa.ubuntu. com/job/ mir-mediumtests -runner- mako/6749/ consoleFull
... archive/ archive/ work/output/ archive/ archive/ work/output/ libmircookie- dev_0.16. 0bzr2962pkg0wil y4058+autopilot 0_armhf. deb archive/ archive/ work/output/ mir-client- platform- mesa-dev_ 0.16.0bzr2962pk g0wily4058+ autopilot0_ armhf.deb
> creating: package_
> inflating: package_
> inflating: package_
So these are *wily* debs? On a vivid+overlay image?
... mir_demo_ client_ basic arm-linux- gnueabihf/ mir/server- platform arm-linux- gnueabihf/ mir/server- platform/ graphics- android. so.5 arm-linux- gnueabihf/ mir/server- platform/ graphics- mesa-kms. so.5 arm-linux- gnueabihf/ mir/server- platform/ server- mesa-x11. so.5 arm-linux- gnueabihf/ mir/server- platform/ input-evdev. so.2 arm-linux- gnueabihf/ mir/server- platform/ graphics- dummy.so arm-linux- gnueabihf/ mir/server- platform/ input-stub. so EXCEPTION) ion_detail10clo ne_implINS0_ 19error_ info_injectorIN S_6system12syst em_errorEEEEE :what: bind: No such file or directory
> running mir_demo_server --test-client /usr/bin/
> initctl: unable to determine sessions
> initctl: unable to determine sessions
> [1443083181.507545] mirplatform: Found graphics driver: android
> [1443083181.508430] mirplatform: Found graphics driver: mesa-kms
> [1443083181.508582] mirplatform: Found graphics driver: mesa-x11
> [1443083181.509131] mirplatform: Found graphics driver: dummy
> [1443083181.513890] mirserver: Starting
> [1443083181.514775] mircommon: Loading modules from: /usr/lib/
> [1443083181.515171] mircommon: Loading module: /usr/lib/
> [1443083181.515294] mircommon: Loading module: /usr/lib/
> [1443083181.515385] mircommon: Loading module: /usr/lib/
> [1443083181.519473] mircommon: Loading module: /usr/lib/
> [1443083181.522828] mircommon: Loading module: /usr/lib/
> [1443083181.524689] mircommon: Loading module: /usr/lib/
> [1443083181.527313] mirplatform: Found graphics driver: android
> [1443083181.527801] mirplatform: Found graphics driver: mesa-kms
> [1443083181.527953] mirplatform: Found graphics driver: mesa-x11
> [1443083181.528228] mirplatform: Found graphics driver: dummy
> [1443083181.529234] mirserver: Selected driver: android (version 0.16.0)
> [1443083182.041171] mirserver: Initial display configuration:
> [1443083182.045442] mirserver: 0.0: LVDS 4.7" 61x102mm
> [1443083182.045686] mirserver: Current mode 768x1280 60.00Hz
> [1443083182.045778] mirserver: Preferred mode 768x1280 60.00Hz
> [1443083182.045839] mirserver: Logical position +0+0
> [1443083182.045930] mirserver: 0.1: unused DisplayPort
> ERROR: Throw location unknown (consider using BOOST_THROW_
> Dynamic exception type: N5boost16except
> std::exception:
*Looks* like all clients are dying for lack of an endpoint.