The experimental build mode should not remove the build directory neither
update the local working copy. Unfortunately this features were brocken because
of typos in a comparisson where lower case and upper case modes were mixed.

When running the Dart.sh script normally all available cores are used which
works well in most cases. Up to now it was possible to limit the number of
used cores by defining the environment variable NCPU which was used for the
build as well as the test stage. Depending on the system this resulted in a
large number of tests which ran into timeouts which were not seen when running
the tests sequentially. With this commit it becomes possible to limit the used
cores during the test stage independently. This is done by defining the
environent variable NCPU4TEST.

Administrator authored 2 years ago and Florian Uhlig committed 2 years ago

Use a different installation directory For the test of the installation to
allow to remove also the build directory.

Test installation also on Debian 10

There was a problem when running CbmRoot from the installation directory with
Debian10. So add also the installation test for Debian10.

Administrator authored 2 years ago and Pierre-Alain Loizeau committed 2 years ago

Remove obsolete, unneeded and unused code.

Administrator authored 2 years ago and Volker Friese committed 2 years ago

Remove many switches which are not needed any longer, since minimum versions
for C++ standard, Root, FairSoft and FairRoot are fixed.

The CI pipeline should run as fast as possible, so stop a test stage as early
as possible.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Installl CbmRoot and remove part of the source directory

Add code which tests if the installtion of CbmRoot works and if the installed
version is functional. Test the "make install" target and run some macros from
teh installation directory.

To be able to test the CbmRoot installation it is necessary that no header
files are accessible in the source directory since this is the fallback for
ROOT when compiling a macro. To achieve this the directories containing any
headers are removed from the source directory.
This is a dangerous operation when executed in a source directory used for
active development. The installation test should only be used when running
the CI/CD workflow.

Before the change it was necessary to define an environment variable to switch
between different test suites like for example the Experimental or Nightly
tests. Now the test suites are chosen by the CMake command line parameter
CBM_TEST_MODEL. These are Experimental, Nightly and Weekly which differ by the
number of executed tests.

For the continuous tests rerun failed tests a second time. This should reduce
the number of failing test pipelines.
In most cases of failing tests the Geant3 simulations crash due to the well
known memory error. If these tests are restarted they normally work without
problem.
Since the feature to restart tests is only available with cmake 3.17 change
the scripts of the CI pipeline to use at least this version.

With CMake versions >= 3.14.0 is is possible to extract the buildid
when submitting results to CDash. This allows to construct the proper
URL to the results on CDash and display it at the end of the CTest script.

Administrator authored 4 years ago and Florian Uhlig committed 4 years ago

This change is needed for proper display on CDash.

Use build type CONTINUOUS for merge requests such that the MR are shown in CDash
at the correct place.

Pipeline now fails also in case of failing tests.
New CI option MergeRequest for Dart.sh wrapper which creates a special CDash label.
Use new CI option when GitLab CI runs for a merge request.

This version is an exact copy of the last revision of the trunk branch
of the old SVN repository of CbmRoor at
https://subversion.gsi.de/cbmsoft/cbmroot/trunk
The old SVN repository will still be available for read access.