If you gave ReduceByKey a fancy output array that decorated another
array, you could get a runtime error for using an invalid array (if the
device adapter used the generic algorithm). The problem was that
ReduceByKey creates a temporary array, and that array was given the same
storage as the output array. That might not be valid for fancy arrays,
so instead use the default storage for the temporary array.
A single gitlab-runner can run multiple test stages
concurrently on the same hardware. When we have 3
jobs asking for 100% of the cpu's we get a 300%
reduction in performance caused by task switching
5c16b3be2 ubuntu1604 builders now use the correct c && c++ compilers
3c80b35b8 ubuntu1604 test step needs to know where MPI install location is
889cb33dd gitlab-ci test jobs better handle false positive failures
b2823d79a ubuntu1604 gcc48 builder install test now pass
93cbea2d7 Update README with update CMake and compiler tested versions
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2042
If you gave ScanInclusiveByKey a fancy output array that decorated
another array, you would get a runtime error for using an invalid array.
The problem was that ScanInclusiveByKey creates a temporary output array
and then copies the result to the actual output array. The problem was
that the temporary output array was given the same storage as the output
array, which won't work if the output array is fancy. Instead, make the
storage for the temporary array default.
Problem was that CMake 3.12 was the CMake version used in the
build image, and test image was using 3.13. This was a problem
as the install test invocation aren't backwards convertible and
therefore failed.
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 .
```
e6f86c2ad Only check sentinel-data if testing is enabled
9ad4ad721 Add content to sentinel-data
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !2022
It makes me irrationally nervous to check an empty file as the sentinel
data. Instead, add some text that can be compared agains. Also add some
explenation to the file to prevent naive developers from messing with
the file.
5061d43f5 vtkm_option should be used as it properly handles CMP0077
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: Kenneth Moreland <kmorel@sandia.gov>
Merge-request: !2020