Comments

• 

  24 days ago by sbrabec | Reply

  My goal was an installable util-linux-testsuite that can be run outside the build environment.

  In the first attempt I tried to create and upstream-able changes to makefiles that will make the testsuite installable. It fails. Autotools target "check" just does not support installation, and it would mean an important rewrite. And it would also need to rewrite meson rules for the new build system.

  Hopefully, the testsuite itself supports easy change of the provided srcdir and builddir. So I needed to properly configure it and cherry pick binaries and other files from the build environment that are needed by the testsuite. So I did a simple mapping:

  top_srcdir=$datadir/util-linux

  top_builddir=$libdir/util-linux

  A new wrapper properly sets the parameters of the testsuite run.

  Now I have a prototype of an installable testsuite. Recently, some tests that succeeded in the in-built "make check" still fail. It needs tracking of these tests and installation of additional files. After doing the rest of this work, the package could be installed, added to OpenQA and started there. It will allow us to run tests with the root privileges, and it will also allow us to properly run tests that fail inside the chroot build environment.

×
Edit Comment 9208
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
My goal was an installable util-linux-testsuite that can be run outside the build environment. In the first attempt I tried to create and upstream-able changes to makefiles that will make the testsuite installable. It fails. Autotools target "check" just does not support installation, and it would mean an important rewrite. And it would also need to rewrite meson rules for the new build system. Hopefully, the testsuite itself supports easy change of the provided srcdir and builddir. So I needed to properly configure it and cherry pick binaries and other files from the build environment that are needed by the testsuite. So I did a simple mapping: top\_srcdir=$datadir/util-linux top\_builddir=$libdir/util-linux A new wrapper properly sets the parameters of the testsuite run. Now I have a prototype of an installable testsuite. Recently, some tests that succeeded in the in-built "make check" still fail. It needs tracking of these tests and installation of additional files. After doing the rest of this work, the package could be installed, added to OpenQA and started there. It will allow us to run tests with the root privileges, and it will also allow us to properly run tests that fail inside the chroot build environment.
 
×
Reply to sbrabec
My goal was an installable util-linux-testsuite that can be run outside the build environment.
In the first attempt I tried to create and upstream-able changes to makefiles that will make the testsuite installable. It fails. Autotools target "check" just does not support installation, and it would mean an important rewrite. And it would also need to rewrite meson rules for the new build system.
Hopefully, the testsuite itself supports easy change of the provided srcdir and builddir. So I needed to properly configure it and cherry pick binaries and other files from the build environment that are needed by the testsuite. So I did a simple mapping:
top_srcdir=$datadir/util-linux
top_builddir=$libdir/util-linux
A new wrapper properly sets the parameters of the testsuite run.
Now I have a prototype of an installable testsuite. Recently, some tests that succeeded in the in-built "make check" still fail. It needs tracking of these tests and installation of additional files. After doing the rest of this work, the package could be installed, added to OpenQA and started there. It will allow us to run tests with the root privileges, and it will also allow us to properly run tests that fail inside the chroot build environment.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview