[MDEV-12751] Oqgraph tests fail on kvm-deb-trusty-ppc64le due to missing libjudy Created: 2017-05-09  Updated: 2020-08-27  Resolved: 2020-08-27

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Daniel Bartholomew
Resolution: Done Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-8976 OQGraph should be disabled for POWER8... Closed

 Description   

The builder kvm-deb-xenial-ppc64le builds the Oqgraph package and installs it for tests.

It turns out that long time ago, rather than making libjudy a dependency, we pre-installed it on our install VMs, see MDEV-5432. So, installation doesn't fail, only later the library fails to be loaded due to 

2017-05-09 12:59:31 70366832332416 [ERROR] Can't open shared library '/usr/lib/mysql/plugin/ha_oqgraph.so' (errno: 2, libJudy.so.1: cannot open shared object file: No such file or directory)

I assume there was a good reason for this, I don't know/don't remember what it was. If it still exists, then the library needs to be installed on the new VMs as well. Otherwise, the dependency should be added to the oqgraph package (then it will probably have to wait till 10.3).

 Comments   
Comment by Daniel Bartholomew [ 2017-05-10 ]

The kvm-deb-xenial-ppc64le install VM already has a valid libjudydebian1 installed (at least, libJudy.so.1 is present). If tests are failing, it's not because libJudy.so.1 is missing. It's there.

buildbot@ubuntu-xenial-ppc64le:~$ ls -l /usr/lib/powerpc64le-linux-gnu/libJudy*
 
lrwxrwxrwx 1 root root     16 May  6  2015 /usr/lib/powerpc64le-linux-gnu/libJudy.so.1 -> libJudy.so.1.0.3
 
-rw-r--r-- 1 root root 461728 May  6  2015 /usr/lib/powerpc64le-linux-gnu/libJudy.so.1.0.3

The kvm-deb-trusty-ppc64le install VM did not have a valid libjudydebian1 installed, so I just now installed the one from Debian Jessie.

I have also added a rule to my repository prep script to add that same deb package to our trusty-ppc64el repository.

Comment by Elena Stepanova [ 2017-05-10 ]

Indeed, it was only trusty, not xenial. I must have looked at a wrong name, sorry about that. I've updated the summary field.

Comment by Daniel Bartholomew [ 2020-08-27 ]

Closing old issues. Nothing to be done here, and trusty is deprecated anyway.

Generated at Thu Feb 08 08:00:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.