Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • alya-testsuite alya-testsuite
  • 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-testsuitealya-testsuite
  • Wiki
  • Execute the Testsuite

Execute the Testsuite · Changes

Page history
Update Execute the Testsuite authored Jul 23, 2019 by Damien Dosimont's avatar Damien Dosimont
Hide whitespace changes
Inline Side-by-side
Execute-the-Testsuite.md
View page @ 6d633be0
......@@ -4,13 +4,15 @@ Testsuite basic usage is composed of three steps: download the testsuite, config
1. Checkout the TestSuite 2.0:
* Local Machine:
svn co svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/Trunk
* From MN4:
svn co file:///gpfs/projects/bsc21/svnroot/AlyaTS/Trunk
* Local Machine:
svn co svn+ssh://bsc21***@mn3.bsc.es/gpfs/projects/bsc21/svnroot/AlyaTS/Trunk
We recommend running the testsuite on your machine more than on marenostrum. If you struggle to configure your machine to run the testsuite, ask for an account on tannat and run the testuite from tannat.
If you have already downloaded the testsuite, you want to update it to get the last features:
......@@ -20,10 +22,73 @@ Testsuite basic usage is composed of three steps: download the testsuite, config
./configure
Look at the next section to get more details about how to configure the testsuite.
3. Execute the testSuite:
./testSuite
# Configuration
## First configuration
The first time you configure the testsuite, you will have to run the command
./configure
or
./configure --all
Also, if your configuration file is obsolete, you will be asked to run the `./configure --all again` when you launch the testsuite.
Here are the different values you will be asked to provide when configuring the testsuite.
### Your marenostrum user
Something like `bscxxxxx`.
### 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.
If you plan to run the testsuite on marenostrum, something we discourage, put `localhost`.
### 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 `p9login1.bsc.es`.
Note that you don't have access to p9 by default. We recommend asking for access to the support since it is crucial that Alya compiles and runs well on this architecture.
### Job queue
This option determines the job queue used to run the testsuite jobs on marenostrum.
* `debug`: the jobs have more priority but only one can run at the same time. Useful when the marenostrum queue is overloaded or if you run only one or a few subsets of tests. This is the default option.
* `bsc_case`: the jobs have less priority but several jobs can run simultaneously. Recommended when the marenostrum queue is not saturated.
### Email
Your bsc email.
### Alya branch
Specify the branch of Alya you want to test. Don't write the full path, just the name of the branch (for instance, type pre-Trunk for the branch `file:///gpfs/projects/bsc21/svnroot/Alya/branches/pre-Trunk`). `Trunk` by default.
### Marenostrum path
# Advanced Usage
You will find here advanced features.
......
Clone repository
  • Home
  • Basic information
  • Execute the Testsuite
  • Analyze the results