Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • alya-testsuite4 alya-testsuite4
  • 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-testsuite4alya-testsuite4
  • Wiki
  • Analyze the results

Analyze the results · Changes

Page history
Update Analyze the results authored Mar 30, 2020 by Damien Dosimont's avatar Damien Dosimont
Show whitespace changes
Inline Side-by-side
Analyze-the-results.md
View page @ 688d8c3a
......@@ -10,20 +10,20 @@ You'll be redirected to the testsuite main page, showing the build, test, and co
## 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 (![ko](<img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20">), 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 (<img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20">), 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)
*Build page showing various compilations*
## Tests
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 |
| ------ | ------ |
| <img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20"> | OK |
| <img src="uploads/e44db76c513f51763fba543f02105c9e/ok.png" width="20"> | OK |
| <img src="uploads/397a6076cb9ba95116a9a578f5a67397/ko.png" width="20"> | Unspecific execution erro or combination of various errors |
| <img src="uploads/2897f0394a8faa852e6da3e9815500d1/time.png" width="20"> | Timeout |
......
Clone repository
  • Home
  • User
    • Presentation
    • Get the testsuite
    • Basic usage
    • Advanced configuration
    • Advanced usage
    • Analyze the results
    • Code Coverage
  • Developer
    • Adding/modifying tests workflow
    • Test configuration
    • Manage the tolerances