Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • alya-testsuite4 alya-testsuite4
  • Project information
    • Project information
    • Activity
    • Members
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Wiki
    • Wiki
  • Activity
Collapse sidebar
  • alyaalya
  • alya-testsuite4alya-testsuite4
  • Wiki
  • Advanced configuration

Advanced configuration · Changes

Page history
Create Advanced configuration authored Mar 30, 2020 by Damien Dosimont's avatar Damien Dosimont
Hide whitespace changes
Inline Side-by-side
Advanced-configuration.md 0 → 100644
View page @ ca4d8487
This page describes the advanced configuration options of the testsuite.
## 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.
\ No newline at end of file
Clone repository
  • Home
  • User
    • Presentation
    • Get the testsuite
    • Basic usage
    • Configure and run the testsuite
    • Analyze the results
    • Code Coverage
  • Developer
    • Adding/modifying tests workflow
    • Test configuration
    • Manage the tolerances