Skip to content

Latest commit

 

History

History
156 lines (110 loc) · 5.99 KB

Build_Subcommand.rst

File metadata and controls

156 lines (110 loc) · 5.99 KB
Raw

Build Subcommand (_buildtest build)

.. program-output:: cat scripts/Build_Subcommand/help.txt

Building tests for Software Packages

To build test via buildtest you will need to use _buildtest build -s option. To demonstrate this lets run the following

_buildtest build -s CMake/3.9.5-GCCcore-6.4.0

The output will be the following

.. program-output:: cat scripts/Build_Subcommand/CMake-3.9.5-GCCcore-6.4.0.txt

Building test for System Packages

To build test for system package you will want to use _buildtest build --package and specify the name of the system package. This should be a system package that is installed in your system.

To demonstrate this example, lets build the test for package coreutils

_buildtest build --package coreutils

The output will be the following

.. program-output:: cat scripts/Build_Subcommand/coreutils.txt

When to use --toolchain option

TBD

Building all software tests via (_buildtest build --all-software)

If you want buildtest to generate test for everything you can just run _buildtest build --all-software which will try to build software test for every possible application module that has a corresponding yaml file in buildtest repository.

This may take some time depending on how many application tests are built. Shown below is a sample output

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest build --all-software
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: Software
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/ebapps/anaconda2/5.1.0/command.yaml
Generating  328  binary tests
Binary Tests are written in  /tmp/buildtest-tests/ebapp/Anaconda2/5.1.0/
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: Software
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/ebapps/anaconda3/5.1.0/command.yaml
Generating  326  binary tests
Binary Tests are written in  /tmp/buildtest-tests/ebapp/Anaconda3/5.1.0/
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: Software
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/ebapps/autoconf/2.69/command.yaml
Generating  7  binary tests
Binary Tests are written in  /tmp/buildtest-tests/ebapp/Autoconf/2.69-GCCcore-6.4.0/

Building All system package tests (_buildtest build --all-package)

The option --all-package will attempt to install tests for all system package. It is basically running _buildtest build --package for everything

Shown below is a sample output.

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest build --all-package
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: System Package
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/system/openscap-utils/command.yaml
Generating  5  binary tests
Binary Tests are written in  /tmp/buildtest-tests/system/openscap-utils
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: System Package
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/system/telnet/command.yaml
Generating  1  binary tests
Binary Tests are written in  /tmp/buildtest-tests/system/telnet
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: System Package
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/system/lynx/command.yaml
Generating  1  binary tests
Binary Tests are written in  /tmp/buildtest-tests/system/lynx

Clean build (_buildtest build --clean-build)

buildtest will preserve the testing directory when tests are generated. For example, if you run the following

_buildtest build --system gcc --shell sh
_buildtest build --system gcc --shell csh
_buildtest build --system gcc --shell bash

This will write the test for shell ("sh", "bash", "csh") in the same directory. If you want to remove the directory prior to running test you can do the following

_buildtest build --system gcc --clean-build

Customize Test Directory (_buildtest build --testdir)

If you want to customize the path to BUILDTEST_TESTDIR you may use the option --testdir or update the environment variable BUILDTEST_TESTDIR. The command line option will override environment variable and environment variable will override configuration value.

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest build --system gcc --testdir /home/siddis14/tmp/
--------------------------------------------
[STAGE 1]: Building Binary Tests
--------------------------------------------
Detecting Test Type: System Package
Processing Binary YAML configuration:  /home/siddis14/github/buildtest-configs/buildtest/system/gcc/command.yaml
Generating  7  binary tests
Binary Tests are written in  /home/siddis14/tmp/system/gcc
Writing Log file to:  /tmp/buildtest/system/gcc/buildtest_12_38_17_10_2018.log