Test-suite-simple: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
* do not forget to create the BRANCHES file in ROBOTS/hostname/usernames/BRANCHES with the folder and the name of your branch like | * do not forget to create the BRANCHES file in ROBOTS/hostname/usernames/BRANCHES with the folder and the name of your branch like | ||
/home/attacc/SOFTWARE/yambo-bugfixes bugfixes | |||
* In order to make test-suite work properly you need to add ssh-key in GitHub and clone the code using SSH and not HTTPS | * In order to make test-suite work properly you need to add ssh-key in GitHub and clone the code using SSH and not HTTPS |
Revision as of 21:02, 7 November 2020
Intro for dummies
Download and configure (warning the last step will download ~1GB)
%git clone https://github.com/yambo-code/yambo-tests.git yambo-tests %cd yambo-tests %./configure --with-yambo=/home/marini/Yambo/yambo/master/ %./driver.pl -d all
Run the test suite and wait for it to finish (warning yambo, ypp, p2y, a2y, yambo_rt and ypp_rt need to be already compiled)
%./driver.pl -tests Si_bulk -keys rt
Check for available options
%./driver.pl -H
Troubleshooting
- If you link external libraries please be sure to copy ncdump and nccopy in the Yambo bin folder
- do not forget to create the BRANCHES file in ROBOTS/hostname/usernames/BRANCHES with the folder and the name of your branch like
/home/attacc/SOFTWARE/yambo-bugfixes bugfixes
- In order to make test-suite work properly you need to add ssh-key in GitHub and clone the code using SSH and not HTTPS
- Be sure that the following packages are installed on your pc: ncftp, ncftpls, ncftput, wget, git, awk, txt2html, rsync
Add a new input inside a test
%cd TESTS/MAIN/Si_bulk/RT
create input file
%cp my_test.in INPUTS/XX_testname %git add INPUTS/XX_testname
and add output reference files
%cp *my_tests* REFERENCE %git add REFERENCE/*my_test*
After that if you go back to the main folder and run
%./driver.pl -tests Si_bulk -keys rt
the new test will be executed. If everything works fine you can commit:
%git commit
For a more extended description see Test-suite