... | ... | @@ -36,23 +36,23 @@ If your configuration file is obsolete, you will be asked to run the `./configur |
|
|
|
|
|
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
|
|
|
##### Marenostrum user
|
|
|
|
|
|
Something like `bscxxxxx`. No default.
|
|
|
|
|
|
#### Gitlab user (https)
|
|
|
##### Gitlab user (https)
|
|
|
|
|
|
Your user name to connect to the git repository through the https connection. Basically, your gitlab account.
|
|
|
|
|
|
#### Email
|
|
|
##### Email
|
|
|
|
|
|
Your bsc email. No default.
|
|
|
|
|
|
#### Alya branch
|
|
|
##### Alya branch
|
|
|
|
|
|
Type the branch name of Alya you want to test. You can also type a commit SHA or a tag.
|
|
|
|
|
|
#### Available builds
|
|
|
##### 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`.
|
|
|
|
... | ... | @@ -60,11 +60,17 @@ Here, you can define the builds you want to run. Type the names separate by a sp |
|
|
|
|
|
These options are additional options that appear when configure with the option `--ALL`
|
|
|
|
|
|
#### _Code coverage revision_
|
|
|
##### alya git repository url (ssh)
|
|
|
Use the default, unless you are working with a fork of alya
|
|
|
|
|
|
Type the revision used as a reference to do the code coverage. Type `last` or press enter for the last Trunk commit.
|
|
|
##### alya git repository url (https)
|
|
|
Use the default, unless you are working with a fork of alya
|
|
|
|
|
|
#### _MN login_
|
|
|
##### _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:
|
|
|
|
... | ... | @@ -74,7 +80,7 @@ Type one the marenostrum login node among: |
|
|
|
|
|
If you press enter without typing anything, the default value `mn2.bsc.es` will be automatically selected.
|
|
|
|
|
|
#### _P9 login_
|
|
|
##### _P9 login_
|
|
|
|
|
|
Same as for marenostrum, but this one for the p9 cluster. Chose between:
|
|
|
|
... | ... | @@ -84,13 +90,11 @@ Same as for marenostrum, but this one for the p9 cluster. Chose between: |
|
|
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
|
|
|
##### 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_
|
|
|
##### _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.
|
|
|
|
... | ... | @@ -105,9 +109,6 @@ If you want to change a particular setting, you can run `./configure` using one |
|
|
* `-e | --email [email] ` Change the email
|
|
|
* `-as | --alya-svn [path] ` Set up alya svn repository path on mn
|
|
|
* `-ab | --alya-branch [svn-branch] ` Select alya svn branch
|
|
|
* `-ts | --test-git-ssh [git-url] ` Set up test git repository (ssh url)
|
|
|
* `-th | --test-git-https [git-url] ` Set up test git repository (https url)
|
|
|
* `-tb | --test-branch [git-branch] ` Select test git branch/commit/tag
|
|
|
* `-c | --cc-ref [git-commit] ` Define code coverage reference commit
|
|
|
* `-p | --path [path] ` Change server path
|
|
|
* `-b | --builds [builds] ` Change the set of builds
|
... | ... | |