** Description changed:
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
+
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+ The reason this matters:
+
+ The principle downstream from Mir (Unity8) loads Mir as one of a number
+ of plugins, several of which use protobuf. That means that we're prone
+ to being loaded, unloaded and reloaded and don't have control of this.
+
+ We've encountered problems in this scenario before that have been traced
+ to protobuf so we have a specific test. But other Unity8 plugins may
+ encounter the same issue.
+
+ As seen in comment #25 the problem here is entirely down to a change in
+ the behavior of libmirprotobuf-lite - it no longer unloads on dlclose().
+
+ This is only a problem because there is code (see patch in comment #20)
+ that assumes that the library will not be used after a call to
+ google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.
--
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The reason this matters:
The principle downstream from Mir (Unity8) loads Mir as one of a
number of plugins, several of which use protobuf. That means that
we're prone to being loaded, unloaded and reloaded and don't have
control of this.
We've encountered problems in this scenario before that have been
traced to protobuf so we have a specific test. But other Unity8
plugins may encounter the same issue.
As seen in comment #25 the problem here is entirely down to a change
in the behavior of libmirprotobuf-lite - it no longer unloads on
dlclose().
This is only a problem because there is code (see patch in comment
#20) that assumes that the library will not be used after a call to
google::protobuf::ShutdownProtobufLibrary() unless it is reloaded.
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
