yahoo-eng-team team mailing list archive

[Rob Cresswell <rcresswe@xxxxxxxxx>]

I think we can close this now. It doesn't appear to be a current issue.

** Changed in: horizon
    Milestone: None => newton-rc1

** Changed in: horizon
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1587698

Title:
  Improve reliability of gate's npm-run-test

Status in OpenStack Dashboard (Horizon):
  Fix Released

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.app.core.images' a test would
  just load 'horizon.app.core' which would load ALL dependent modules,
  then have to destroy them.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1587698/+subscriptions