Invalid for the Mir project. Sounds like it's just another protobuf bug. Hopefully we won't need to workaround it in Mir, but that's not completely out of the question. Especially if protobuf3 hits distro without first getting fixed we won't have much choice.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT) Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in protobuf package in Ubuntu: In Progress Bug description: builds with 3.0.0-7, then has one failing test: test 19 Start 19: Protobuf-can-be-reloaded 19: Test command: /<<BUILDDIR>>/mir-0.24.0+16.10.20160815.3/obj-powerpc64le-linux-gnu/bin/mir_test_reload_protobuf 19: Test timeout computed to be: 9.99988e+06 19/19 Test #19: Protobuf-can-be-reloaded ..........................***Exception: SegFault 0.17 sec 95% tests passed, 1 tests failed out of 19 Total Test time (real) = 125.73 sec The following tests FAILED: 19 - Protobuf-can-be-reloaded (SEGFAULT) Errors while running CTest Makefile:85: recipe for target 'test' failed make[2]: *** [test] Error 8 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1619616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
