Skip to content

Conversation

@nightlark
Copy link
Contributor

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

nightlark and others added 30 commits July 10, 2019 11:57
Run TraceR with a dfly network on the stencil4d-otf example on Travis
@nightlark
Copy link
Contributor Author

The push build for this branch passes: https://travis-ci.com/nightlark/TraceR/builds/129162778

The failure is because #38 resulted in values changing in the CODES output files, as well as the TraceR WallTime values printed out.

@bhatele bhatele changed the base branch from master to develop November 19, 2020 13:13
@nightlark
Copy link
Contributor Author

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.

@bhatele
Copy link
Member

bhatele commented Feb 24, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants