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

terrapower / armi / 261 / 3
87%
master: 87%

Build:
DEFAULT BRANCH: master
Ran 10 Jul 2020 08:29PM UTC
Files 360
Run time 4min
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

10 Jul 2020 08:10PM UTC coverage: 77.443% (+0.05%) from 77.395%
TOXENV=cov,report

push

travis-ci-com

web-flow
Improve setting rename/migration functionality (#96)

* Improve setting rename/migration functionality

The previous mechanism for implicitly renaming old setting names to new
ones lived in settingsRules, which are difficult to extend from plugins.
As a result there were still a bunch of RENAMES for settings that have
since been removed from ARMI altogether. This includes a handful of
changes that allow these renames to live closer to the Settings to which
they apply, and therefore accessible to plugins. Changes include:

 - Introduction of ArmiPluginManager. This is a subclass of the pluggy
 version, which adds a counter that is incremented any time the set of
 registered plugins changes. This allows clients to safely cache things
 derived from the plugins, and invalidate those caches as necessary. We
 may instead want to go the route of simply locking the plugin manager
 and preventing future modification, but this should work well for now,
 and is more flexible.

 - Add getSettings() method to the App class. The corresponding logic
 used to be called through the Settings.__init__() method, which was
 pretty odd.

 - Add the oldNames instance attribute to the Setting class. This is
 used to handle setting renames in lieu of settingsRulese.RENAMES.

 - Add the SettingRenamer class to settingsIO, which distills the
 oldNames from the Setting instances and helps settingsIO perform
 migrations

 - Merge the protected and public sections of SettingsReader. This was a
 holdover from when the SettingsReader doubled as a setting definition
 reader as well, and now only served to complicate matters.

 - Migrate the contents of RENAMES to their respective settings

* Address reviewer comments

30982 of 40006 relevant lines covered (77.44%)

0.77 hits per line

Source Files on job 261.3 (TOXENV=cov,report)
  • Tree
  • List 0
  • Changed 15
  • Source Changed 15
  • Coverage Changed 14
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 478
  • Travis Job 261.3
  • 8f53a373 on github
  • Prev Job for TOXENV=cov,report on master (#256.3)
  • Next Job for TOXENV=cov,report on master (#260.3)
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