|
|
|
This page describes the advanced configuration options of the testsuite and the various types of execution.
|
|
|
|
This page describes the advanced usages of the testsuite.
|
|
|
|
|
|
|
|
## Configuration
|
|
|
|
|
|
|
|
### To print the configuration help:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts configure -h
|
|
|
|
```
|
|
|
|
|
|
|
|
### First configuration
|
|
|
|
|
|
|
|
The first time you configure the testsuite, you will have to run the command
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts configure
|
|
|
|
```
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts configure --all
|
|
|
|
```
|
|
|
|
|
|
|
|
Running
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts configure --ALL
|
|
|
|
```
|
|
|
|
|
|
|
|
will give you access to more configuration options.
|
|
|
|
|
|
|
|
To update your configuration file to the last version without having to type all the data:
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts configure --re
|
|
|
|
```
|
|
|
|
|
|
|
|
If your configuration file is obsolete, you will be asked to run the `./configure --all` again when you launch the testsuite.
|
|
|
|
|
|
|
|
### Configuration options
|
|
|
|
|
|
|
|
Here are the different values you will be asked to provide when configuring the testsuite. Note that typing enter will use the default option, when possible.
|
|
|
|
|
|
|
|
##### Marenostrum user
|
|
|
|
|
|
|
|
Something like `bscxxxxx`. No default.
|
|
|
|
|
|
|
|
##### Gitlab user (https)
|
|
|
|
|
|
|
|
Your user name to connect to the git repository through the https connection. Basically, your gitlab account.
|
|
|
|
|
|
|
|
##### Email
|
|
|
|
|
|
|
|
Your bsc email. No default.
|
|
|
|
|
|
|
|
##### Alya branch
|
|
|
|
|
|
|
|
Type the branch name of Alya you want to test. You can also type a commit SHA or a tag.
|
|
|
|
|
|
|
|
##### Available builds
|
|
|
|
|
|
|
|
Here, you can define the builds you want to run. Type the names separate by a space. For a full testsuite execution, run `all`.
|
|
|
|
|
|
|
|
### Configuration advanced options
|
|
|
|
|
|
|
|
These options are additional options that appear when configure with the option `--ALL`
|
|
|
|
|
|
|
|
##### alya git repository url (ssh)
|
|
|
|
Use the default, unless you are working with a fork of alya
|
|
|
|
|
|
|
|
##### alya git repository url (https)
|
|
|
|
Use the default, unless you are working with a fork of alya
|
|
|
|
|
|
|
|
##### Code coverage revision
|
|
|
|
|
|
|
|
Type the revision used as a reference to do the code coverage. Type `master` or press enter for the last master commit.
|
|
|
|
|
|
|
|
##### MN login
|
|
|
|
|
|
|
|
Type one the marenostrum login node among:
|
|
|
|
|
|
|
|
* `mn1.bsc.es`
|
|
|
|
* `mn2.bsc.es`
|
|
|
|
* `mn3.bsc.es`
|
|
|
|
|
|
|
|
If you press enter without typing anything, the default value `mn2.bsc.es` will be automatically selected.
|
|
|
|
|
|
|
|
##### P9 login
|
|
|
|
|
|
|
|
Same as for marenostrum, but this one for the p9 cluster. Chose between:
|
|
|
|
|
|
|
|
* `p9login1.bsc.es`
|
|
|
|
* `p9login2.bsc.es`
|
|
|
|
|
|
|
|
the default value being `p9login2.bsc.es`.
|
|
|
|
Note that you don't have access to p9 by default. We recommend you to ask the support to enable it since it is crucial that Alya compiles and runs well on this architecture.
|
|
|
|
|
|
|
|
##### Marenostrum path
|
|
|
|
|
|
|
|
Type the path on Marenostrum GPFS where the testsuite will be executed and the data generated. If the path does not exists, it will be created. By default, the path is `/gpfs/projects/bsc21/bscxxxxx/ts/name_of_your_machine`
|
|
|
|
|
|
|
|
##### Build job queue/Test job queue
|
|
|
|
|
|
|
|
Here, you can define the queue for the build jobs (resp. the test jobs). Use bsc_case if possible, and debug only if you have a few jobs to run or if marenostrum is overloaded.
|
|
|
|
|
|
|
|
## Advanced runs
|
|
|
|
|
|
|
|
### To print the help
|
|
|
|
## To print the help
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts help
|
|
|
|
```
|
|
|
|
|
|
|
|
### Run only the builds
|
|
|
|
## Run only the builds
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts build
|
|
|
|
```
|
|
|
|
|
|
|
|
### Run only the tests
|
|
|
|
## Run only the tests
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts test
|
|
|
|
```
|
|
|
|
You need to compile the builds in a previous step.
|
|
|
|
|
|
|
|
### Run only the code coverage
|
|
|
|
## Run only the code coverage
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts cc
|
|
|
|
```
|
|
|
|
You need to compile the builds and run the tests in previous steps. Only work with intel compiler builds.
|
|
|
|
|
|
|
|
### Send the report email
|
|
|
|
## Send the report email
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts email
|
|
|
|
```
|
|
|
|
You need to compile the builds, run the tests and the code coverage in previous steps.
|
|
|
|
|
|
|
|
### Transmit the full report by email
|
|
|
|
## Transmit the full report by email
|
|
|
|
|
|
|
|
```sh
|
|
|
|
./ts send jean.pierre@mail.com
|
| ... | ... | @@ -147,7 +41,7 @@ You need to compile the builds, run the tests and the code coverage in previous |
|
|
|
|
|
|
|
The receiver will get a message with instructions about how to download the report.
|
|
|
|
|
|
|
|
### Options
|
|
|
|
## Options
|
|
|
|
|
|
|
|
You can add the following options to `./ts tests` and `./ts all` using the following syntax:
|
|
|
|
|
| ... | ... | |
