I've worked out a way to replicate the symptoms. Just not sure yet how it can be affecting CI:
I start by removing the libmirplatformgraphics.so in lib
Then when running e.g. mir_integration_tests the installed version of libmirplatformgraphics.so is picked up.
mir_integration_tests links to a local libmircommon.so.2 (as that's what is being built since -r1846
But the installed version of libmirplatformgraphics.so links to the installed libmircommon.so.1
And and two different libmircommon.so.* both try to register with libprotobuf
Which that gives us "libprotobuf ERROR..."
The question therefore is: could we pick up the wrong libmirplatformgraphics.so in CI?
I've worked out a way to replicate the symptoms. Just not sure yet how it can be affecting CI:
I start by removing the libmirplatformg raphics. so in lib _tests the installed version of libmirplatformg raphics. so is picked up. _tests links to a local libmircommon.so.2 (as that's what is being built since -r1846 raphics. so links to the installed libmircommon.so.1
Then when running e.g. mir_integration
mir_integration
But the installed version of libmirplatformg
And and two different libmircommon.so.* both try to register with libprotobuf
Which that gives us "libprotobuf ERROR..."
The question therefore is: could we pick up the wrong libmirplatformg raphics. so in CI?
Bugs in CI are not unknown.