← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1348818] Re: Unittests do not succeed with random PYTHONHASHSEED value

 

** Also affects: trove
   Importance: Undecided
       Status: New

** Changed in: trove
    Milestone: None => juno-3

** Changed in: trove
     Assignee: (unassigned) => Nikhil Manchanda (slicknik)

** Changed in: trove
   Importance: Undecided => Critical

** Changed in: trove
   Importance: Critical => High

** Changed in: trove
       Status: New => Triaged

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

Title:
  Unittests do not succeed with random PYTHONHASHSEED value

Status in OpenStack Key Management (Barbican):
  Confirmed
Status in OpenStack Telemetry (Ceilometer):
  Triaged
Status in Cinder:
  In Progress
Status in Designate:
  In Progress
Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Committed
Status in Orchestration API (Heat):
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Bare Metal Provisioning Service (Ironic):
  Fix Committed
Status in OpenStack Identity (Keystone):
  In Progress
Status in OpenStack Neutron (virtual network service):
  In Progress
Status in OpenStack Compute (Nova):
  New
Status in Python client library for Neutron:
  In Progress
Status in OpenStack Data Processing (Sahara, ex. Savanna):
  In Progress
Status in Openstack Database (Trove):
  Triaged
Status in Web Services Made Easy:
  New

Bug description:
  New tox and python3.3 set a random PYTHONHASHSEED value by default.
  These projects should support this in their unittests so that we do
  not have to override the PYTHONHASHSEED value and potentially let bugs
  into these projects.

  To reproduce these failures:

  # install latest tox
  pip install --upgrade tox
  tox --version # should report 1.7.2 or greater
  cd $PROJECT_REPO
  # edit tox.ini to remove any PYTHONHASHSEED=0 lines
  tox -epy27

  Most of these failures appear to be related to dict entry ordering.

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


References