Commit Graph

12 Commits

Author SHA1 Message Date
Vicente Adolfo Bolea Sanchez
55e8d258ad CMAKE: update latest CI CMake to 3.23.4 2022-10-26 17:18:15 -04:00
Vicente Adolfo Bolea Sanchez
ebdd6b55a5 perftest: add benchmark build 2022-10-03 13:21:09 -04:00
Vicente Adolfo Bolea Sanchez
db770e7598 CI: Limit usage of hipcc and use -O0 2022-09-30 17:04:25 -04:00
Vicente Adolfo Bolea Sanchez
daf41d29f9 ci: memcheck generates junit reports 2022-06-16 13:39:24 -04:00
Vicente Adolfo Bolea Sanchez
5e845e6db3 CI: fix junit upload cmake ver requirement 2022-06-15 17:13:20 -04:00
Vicente Adolfo Bolea Sanchez
67b92d3365 ci: Add OLCF GitLab-CI
Co-authored-by: Vicente Bolea <vicente.bolea@kitware.com>
Co-authored-by: Chuck Atkins <chuck.atkins@kitware.com
2021-12-15 13:00:47 -05:00
Vicente Adolfo Bolea Sanchez
5353934e6b CI: Add Junit support
Signed-off-by: Vicente Adolfo Bolea Sanchez <vicente.bolea@kitware.com>
2021-08-12 19:35:39 -04:00
Robert Maynard
f2b8cac0c9 gitlab-ci centos7 exclude tests causing rhel8 issues
The centos7 on rhel8 was not running the install tests
as the path to cmake/ctest wasn't valid. This causes
the causes the following issues:

1. NOT_RUN tests with REPEAT don't show up in CMake failed
output fixed by:
  https://gitlab.kitware.com/cmake/cmake/-/merge_requests/4801

2. failed tests cause ctest_test to return an error code,
   which propagates to the script, which propagates to
   having ctest running the script return an error.
2020-05-27 10:22:33 -04:00
Robert Maynard
b59913fad3 Log CDash build ids from each step of the build process
This can help track down a weird CDash bugs caused by multiple
in-flight builds that get canceled and result in bad CDash
reporting
2020-05-13 15:58:34 -04:00
Robert Maynard
889cb33dde gitlab-ci test jobs better handle false positive failures
If ctest had to re-run failed tests and those test pass we
now consider it a successful run
2020-04-16 13:25:55 -04:00
Robert Maynard
24a264fce8 Add scripts to allow developers to replicate CI environments
To simplify reproducing docker based CI workers locally, VTK-m has python program that handles all the
work automatically for you.

The program is located in `[Utilities/CI/reproduce_ci_env.py ]` and requires python3 and pyyaml.

To use the program is really easy! The following two commands will create the `build:rhel8` gitlab-ci
worker as a docker image and setup a container just as how gitlab-ci would be before the actual
compilation of VTK-m. Instead of doing the compilation, instead you will be given an interactive shell.

```
./reproduce_ci_env.py create rhel8
./reproduce_ci_env.py run rhel8
```

To compile VTK-m from the the interactive shell you would do the following:
```
> src]# cd build/
> build]# cmake --build .
```
2020-04-09 13:54:20 -04:00
Robert Maynard
5bc09b976e Add gitlab-ci infrastructure 2020-03-26 13:40:47 -04:00