Improve reliability of gate's npm-run-test
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Critical
|
Matt Borland |
Bug Description
The npm-run-test job in the gate has shown itself to be less reliable lately. In particular it tends to hang until the timeout, after successfully completing the tests.
There have been similar failures in the past due to a variety of reasons. Most likely there's a memory problem with the reloading of modules over and over again in Chrome. One factor that had affected this was the loading of modules that were too 'high' in the hierarchy. For example, instead of using 'horizon.
Ideally we localize the tests loading only the modules needed.
Other options for assisting with the tests would be to reduce the number of dependencies within app.core, such as moving resource registrations out since they are not really needed as part of the core registrations (where common features are placed, esp. APIs).
This bug will remain in effect until npm-run-test appears to be fully stabilized.
Changed in horizon: | |
assignee: | nobody → Matt Borland (palecrow) |
status: | New → In Progress |
tags: | added: angularjs |
Changed in horizon: | |
status: | Fix Committed → Confirmed |
Do we have a citation for the memory / module loading assertion?