hpcgroup
Run regression tests on Travis
Runs stencil4d-otf example using the dragonfly, fattree, and hypre, and torus network configurations, and compares the resulting output files to a baseline set of output files.
- Some times check to make sure the value is within a tolerance; some floating point time values are very slightly (10^-6) different on Travis than when the same test and code is run on LC
- Busy time in msg-stats files are ignored; they vary significantly between runs even on the same machine
The push build for this branch passes: https://travis-ci.com/nightlark/TraceR/builds/129162778
The failure is because https://github.com/LLNL/TraceR/pull/38 resulted in values changing in the CODES output files, as well as the TraceR WallTime values printed out.
Given recent changes to Travis, I don't think running tests there is as good as it used to be. Would be better to use GitHub Actions now.
Given recent changes to Travis, I don't think running tests there is as good as it used to be. Would be better to use GitHub Actions now.
Yes we are planning to move to GitHub actions soon.
