diff options
| author |  Axel Huebl <axel.huebl@plasma.ninja>
| 2020-09-30 13:00:29 -0700 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2020-09-30 13:00:29 -0700 |
| commit | f2e4811afdc32055e5fa49241c02deae4e5ad318 (patch) | |
| tree | deca5bd1ebebab63aa15a9cb5fa4d60c3cfbddc0 /Source/Parallelization/GuardCellManager.H | |
| parent | c58c1387e22615971ec9f5e0981469b840feb503 (diff) | |
| download | WarpX-f2e4811afdc32055e5fa49241c02deae4e5ad318.tar.gz WarpX-f2e4811afdc32055e5fa49241c02deae4e5ad318.tar.zst WarpX-f2e4811afdc32055e5fa49241c02deae4e5ad318.zip | |
CI: Output CPU Type (#1393)
Since our CI is cloud-based, we can get various kinds of
CPUs in different runs. For machine-precision tests, I got
the feeling that some tests that rely heavily on exact numbers
are overly strict with respect to guarantees between various
CPU generations, esp. since we rely on fastmath.
This will output the CPU type at the beginning of runs, so we
can find out more when tests fail with "checksum" (output data
fingerprint) errors.
Diffstat (limited to 'Source/Parallelization/GuardCellManager.H')
0 files changed, 0 insertions, 0 deletions