...
| Code Block | ||
|---|---|---|
| ||
tests
├── __init__.py
├── ci_scripts
│ ├── .gitlab-ci.yml
│ └── .iter-ci.sh
├── configs
│ ├── actor_configuration.yml
│ └── ids_configuration.yml
├── input_pulse_file
│ ├── ITER
│ │ └── 3
│ │ └── 0
│ │ └── {pulsefiles}
│ └── GITLAB
│ └── 3
│ └── 0
│ └── {pulsefiles}
├── main_code_run
│ └── run_actor.sh
├── modules
│ ├── modules_gitlab.yml
│ └── modules_iter.yml
├── native_codes_build
│ └── build_actor.sh
├── pytest_scripts
│ ├── conftest.py
│ ├── __init__.py
│ ├── pytest.ini
│ └── test_actor.py
├── README.md
├── test.sh
└── utils
├── get_actor_info.py
├── get_ids_info.py
└── get_ids_name.py |
CI engine - ITER or GITLAB
Actor Testing Framework is prepared to run on both ITER CI (called Bamboo) and GITLAB CI (works like Gateway).
There is a slight difference between these platforms that causes the framework to be configured differently to run tests on each of them.
ITER CI Configuration
ITER Modules
To set up the ITER modules needed to build and run the actor, there is a file called modules/modules_iter.yml , where you need to provide all the necessary modules, preferably full versions.
| Code Block | ||
|---|---|---|
| ||
├── modules
│ ├── modules_gitlab.yml
│ └── modules_iter.yml # <-- This is file dedicated for ITER modules
##############################################
- example: inside modules_iter.yml:
##############################################
modules:
- IMAS
- iWrap
- INTERPOS/9.1.0-intel-2020b
- XMLlib/3.3.1-intel-2020b |