• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

terrapower / armi / 165
87%

Build:
DEFAULT BRANCH: master
Ran 29 Apr 2020 09:28PM UTC
Jobs 1
Files 348
Run time 27s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
165

push

travis-ci-com

web-flow
Add optional syncDbAfterWrite behavior and setting (#63)

* Add optional syncDbAfterWrite behavior and setting

The ARMI output database is created by the master node in parallel cases
and is actually written on a local scratch space during the run (for i/o
performance in large sweeps). There are some scenarios, however, where a
DB is needed by other MPI processes as they're doing their work (for
example, if a DB-derived history is needed). This feature just copies
the whole database from the local drive into the run's working directory
(often on a shared network drive) after every write.

This feature can be activted by setting the new syncDbAfterWrite user
setting to `true`.

Relatedly, MPI worker nodes now open the database with read-only
permissions after every DistributeState. This allows them to perform
DB-reading tasks during a run, now that the DB is available to them.

Also added optional Executer-level way to set a runPath.

30060 of 39166 relevant lines covered (76.75%)

0.77 hits per line

Jobs
ID Job ID Ran Files Coverage
3 165.3 (TOXENV=cov,report) 29 Apr 2020 09:28PM UTC 0
76.75
Travis Job 165.3
Source Files on build 165
Detailed source file information is not available for this build.
  • Back to Repo
  • Build #165
  • ddb39ab4 on github
  • Prev Build on master (#161)
  • Next Build on master (#164)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc