Skip to content
GitLab

Analyze the results · Changes

Page history
Update Analyze the results authored by Damien Dosimont's avatar Damien Dosimont
Show whitespace changes
Inline Side-by-side
Analyze-the-results.md
View page @ bed8edb3
...@@ -10,7 +10,7 @@ You'll be redirected to the testsuite main page, showing the build, test, and co ...@@ -10,7 +10,7 @@ You'll be redirected to the testsuite main page, showing the build, test, and co
## Builds ## Builds
If you click on the build item, you will access the build page. For each build, you'll see its name, the compiler, the version, some tags specific to this build, the modules loaded to compile, the configuration file, the job script content, and the output and error files generated by the job execution, as well as the execution time. If a build has failed (red cross), don't hesitate to analyze the content of the various files to understand what is the cause of the failure. If you click on the build item, you will access the build page. For each build, you'll see its name, the compiler, the version, some tags specific to this build, the modules loaded to compile, the configuration file, the job script content, and the output and error files generated by the job execution, as well as the execution time. If a build has failed (![ko](uploads/14d197e227c63daf4dae6d565aec6fe2/ko.png)), don't hesitate to analyze the content of the various files to understand what is the cause of the failure.
![Capture_d_écran_de_2020-03-30_17-21-46](uploads/e9701a604ed6c1567cc75d6c9998a487/Capture_d_écran_de_2020-03-30_17-21-46.png) ![Capture_d_écran_de_2020-03-30_17-21-46](uploads/e9701a604ed6c1567cc75d6c9998a487/Capture_d_écran_de_2020-03-30_17-21-46.png)
*Build page showing various compilations* *Build page showing various compilations*
...@@ -19,7 +19,13 @@ If you click on the build item, you will access the build page. For each build, ...@@ -19,7 +19,13 @@ If you click on the build item, you will access the build page. For each build,
If you click on the test item, you will access the test page. For each test, you'll see an item with its name, its authors, a brief description, the alya modules it requires, the post process tool (`alya2pos`, `mpio2txt` or `none`), if the job has been relaunched one or several times because of a possible system failure (retry), and the global status of this job (showing the worst error that happened during this test execution with each of the build and mpi/openmp combination). If you click on the test item, you will access the test page. For each test, you'll see an item with its name, its authors, a brief description, the alya modules it requires, the post process tool (`alya2pos`, `mpio2txt` or `none`), if the job has been relaunched one or several times because of a possible system failure (retry), and the global status of this job (showing the worst error that happened during this test execution with each of the build and mpi/openmp combination).
Here, the list of statuses:
| Symbol | Meaning |
| ------ | ------ |
| ![ok](uploads/12ed412aaa18f7987dfd1021afa29a07/ok.png) | OK |
| ![ko](uploads/3e6640fec1ee1d497e014ea8f3008159/ko.png) | Unspecific execution erro or combination of various errors |
| ![time](uploads/2897f0394a8faa852e6da3e9815500d1/time.png) | Timeout |
As for the compilation, you can get more insight into the test results by clicking on the corresponding red cross. As for the compilation, you can get more insight into the test results by clicking on the corresponding red cross.
......