yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1714117

Title:
  unittests: ec2 tests escape to network

Status in cloud-init:
  Fix Released

Bug description:
  On Aug 10, 2017 the nightly and CI tests began taking 20 additional
  minutes. The additional time is occurring during the tox run,
  specifically during the 'py27' and 'xenial' environments. Here are
  comparisons of run times:

  Aug 8: 1 min 52 seconds
  Aug 9: 1 min 47 seconds
  Aug 10: 19 mins

  These tests are run at ~23:40 UTC each day, therefore a change would
  have occurred during the day resulting in the end-of-day run to see
  the effect.

  From the Aug 10 run these two tox environments are adding a huge amount of time:
  py27: Ran 980 tests in 525.871s
  xenial: Ran 980 tests in 518.678s

  Here are timing results from the Aug 9 run:
  py27: Ran 978 tests in 9.051s
  xenial: Ran 978 tests in 14.122s

  Per the git log I believe it is tied to this revision:
  https://git.launchpad.net/cloud-init/commit/?id=d5f855dd96ccbea77f61b0515b574ad2c43d116d

  Which added two new tests:
  test_ec2_local_returns_false_on_bsd
  test_ec2_local_performs_dhcp_on_non_bsd
  hence the increase the number of tests run. I am not however, saying that these two tests are the cause of the additional test time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1714117/+subscriptions