On 10/4/22 18:49, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.4. Depending on the results, this may be the only testing call.
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Not sure whether that's an issue with build options in the .spec file or whatever.
Those package builds run in temporary VMs [1]. Do you have a command at hand how to dump all relevant files in case any of the tests aborts? Can I lookup how the OpenLDAP project runs automated builds and tests in gitlab and borrow from that?
Ciao, Michael.
[1] https://build.opensuse.org/package/show/home:stroeder:branches:home:stroeder...
On Wed, Nov 16, 2022 at 11:32:09AM +0100, Michael Ströder wrote:
On 10/4/22 18:49, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.4. Depending on the results, this may be the only testing call.
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Not sure whether that's an issue with build options in the .spec file or whatever.
Those package builds run in temporary VMs [1]. Do you have a command at hand how to dump all relevant files in case any of the tests aborts? Can I lookup how the OpenLDAP project runs automated builds and tests in gitlab and borrow from that?
Hi Michael, you can find our gitlab automated build configuration in .gitlab-ci.yml in the git repo. Also of note might be ITS#9916 which has a proposed patch already[0], can you give that a try?
Thanks,
[0]. https://git.openldap.org/openldap/openldap/-/merge_requests/582
On 11/16/22 12:08, Ondřej Kuzník wrote:
Also of note might be ITS#9916 which has a proposed patch already[0], can you give that a try?
Are you refererring to this commit?
https://git.openldap.org/openldap/openldap/-/merge_requests/582/diffs?commit...
Ciao, Michael.
On Wed, Nov 16, 2022 at 01:33:55PM +0100, Michael Ströder wrote:
On 11/16/22 12:08, Ondřej Kuzník wrote:
Also of note might be ITS#9916 which has a proposed patch already[0], can you give that a try?
Are you refererring to this commit?
https://git.openldap.org/openldap/openldap/-/merge_requests/582/diffs?commit...
That's the one. If this makes a difference, please comment on the MR to that account as well.
Thanks,
On 11/16/22 13:51, Ondřej Kuzník wrote:
On Wed, Nov 16, 2022 at 01:33:55PM +0100, Michael Ströder wrote:
On 11/16/22 12:08, Ondřej Kuzník wrote:
Also of note might be ITS#9916 which has a proposed patch already[0], can you give that a try?
Are you refererring to this commit?
https://git.openldap.org/openldap/openldap/-/merge_requests/582/diffs?commit...
That's the one. If this makes a difference, please comment on the MR to that account as well.
Hmm, maybe I got something wrong. But this patch does not apply to RE26.
I'll wait with tests until this change reached RE26.
Ciao, Michael.
Ondřej Kuzník wrote:
On Wed, Nov 16, 2022 at 11:32:09AM +0100, Michael Ströder wrote:
On 10/4/22 18:49, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.4. Depending on the results, this may be the only testing call.
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Also of note might be ITS#9916 which has a proposed patch already[0], can you give that a try?
Irrelevant, since test000 does no backend operations.
On 11/16/22 19:52, Howard Chu wrote:
Ondřej Kuzník wrote:
On Wed, Nov 16, 2022 at 11:32:09AM +0100, Michael Ströder wrote:
On 10/4/22 18:49, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.4. Depending on the results, this may be the only testing call.
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Also of note might be ITS#9916 which has a proposed patch already[0], can you give that a try?
Irrelevant, since test000 does no backend operations.
test000 fails with message
backend_startup_one (type=mdb, suffix="o=OpenLDAP Project,l=Internet"): bi_db_open failed! (95)
tests/testrun/slapd.1.log attached herein:
https://bugs.openldap.org/show_bug.cgi?id=9954
Ciao, Michael.
Michael Ströder wrote:
On 10/4/22 18:49, Quanah Gibson-Mount wrote:
This is the first testing call for OpenLDAP 2.6.4. Depending on the results, this may be the only testing call.
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Not sure whether that's an issue with build options in the .spec file or whatever.
Built fine for me on Ubuntu 22.04 and make test passes.
hyc@gcc92:/tmp/openldap/tests$ gcc --version gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Using the gcc92 machine from the compile farm https://cfarm.tetaneutral.net/machines/list/
On 11/18/22 07:32, Howard Chu wrote:
Michael Ströder wrote:
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Not sure whether that's an issue with build options in the .spec file or whatever.
Built fine for me on Ubuntu 22.04 and make test passes.
hyc@gcc92:/tmp/openldap/tests$ gcc --version gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Using the gcc92 machine from the compile farm https://cfarm.tetaneutral.net/machines/list/
Ok. So let's find the possibly relevant difference.
Could you please have a short look at the build log in OBS and watch out for the compiler options used? They use many of the build hardening options:
https://build.opensuse.org/public/build/home:stroeder:branches:home:stroeder...
Ciao, Michael.
Michael Ströder wrote:
On 11/18/22 07:32, Howard Chu wrote:
Michael Ströder wrote:
make test seems to fail for openSUSE on riscv64 already for test000-rootdse.
Not sure whether that's an issue with build options in the .spec file or whatever.
Built fine for me on Ubuntu 22.04 and make test passes.
hyc@gcc92:/tmp/openldap/tests$ gcc --version gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Using the gcc92 machine from the compile farm https://cfarm.tetaneutral.net/machines/list/
Ok. So let's find the possibly relevant difference.
Could you please have a short look at the build log in OBS and watch out for the compiler options used? They use many of the build hardening options:
https://build.opensuse.org/public/build/home:stroeder:branches:home:stroeder...
I don't have permissions on the box to install some of the dev libraries. Are you sure systemd is working on your build machine?
Ciao, Michael.
On 11/18/22 14:35, Howard Chu wrote:
Michael Ströder wrote:
Could you please have a short look at the build log in OBS and watch out for the compiler options used? They use many of the build hardening options: >> https://build.opensuse.org/public/build/home:stroeder:branches:home:stroeder...
I don't have permissions on the box to install some of the dev libraries.
Are you referring to OBS or cfarm.tetaneutral.net?
You could alter the .spec file to install additional tools and libs.
Are you sure systemd is working on your build machine?
Are you concerned about --with-systemd in my .spec file? The build also failed before I introduced this.
AFAICT the OBS builds are always run on temporarily spawned VMs (IIRC qemu-kvm), not only containers. For most platforms the VMs are spawned on real native hardware (e.g. ARM and S/390). I have to ask OBS folks whether that's also true for riscv64.
Also the OBS builds including make test on the various platforms are spawned from the very same .spec file:
https://build.opensuse.org/package/show/home:stroeder:branches:home:stroeder...
Currently riscv64 is blocked by rebuilds of other dependencies. Maybe those rebuilds will fix an issue. Let's see...
Ciao, Michael.
Michael Ströder wrote:
On 11/18/22 14:35, Howard Chu wrote:
Michael Ströder wrote:
Could you please have a short look at the build log in OBS and watch out for the compiler options used? They use many of the build hardening options: >> https://build.opensuse.org/public/build/home:stroeder:branches:home:stroeder...
I don't have permissions on the box to install some of the dev libraries.
Are you referring to OBS or cfarm.tetaneutral.net?
I was talking about cfarm.
You could alter the .spec file to install additional tools and libs.
Are you sure systemd is working on your build machine?
Are you concerned about --with-systemd in my .spec file? The build also failed before I introduced this.
AFAICT the OBS builds are always run on temporarily spawned VMs (IIRC qemu-kvm), not only containers. For most platforms the VMs are spawned on real native hardware (e.g. ARM and S/390). I have to ask OBS folks whether that's also true for riscv64.
Your log clearly shows the build is running under a QEMU VM.
Also the OBS builds including make test on the various platforms are spawned from the very same .spec file:
https://build.opensuse.org/package/show/home:stroeder:branches:home:stroeder...
Currently riscv64 is blocked by rebuilds of other dependencies. Maybe those rebuilds will fix an issue. Let's see...
I suggest you examine the slap*.log files in the testrun directory for any error messages. A lot better than guessing.
Ciao, Michael.
On 11/18/22 18:41, Howard Chu wrote:
Michael Ströder wrote:
AFAICT the OBS builds are always run on temporarily spawned VMs (IIRC qemu-kvm), not only containers. For most platforms the VMs are spawned on real native hardware .. >
Your log clearly shows the build is running under a QEMU VM.
Also on riscv64 OBS starts the build VM with:
qemu-kvm [..] -cpu host -M pc,accel=kvm,[..]
AFAICT this results in KVM being used without CPU emulation.
Ciao, Michael.
-
Howard Chu -
Michael Ströder -
Ondřej Kuzník