yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #52902
[Bug 1568708] Re: translation sync broken due to wrong usage of venv
Reviewed: https://review.openstack.org/330871
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=81c01d5041ef8f0ae04a6bd50d516050272bb8a6
Submitter: Jenkins
Branch: master
commit 81c01d5041ef8f0ae04a6bd50d516050272bb8a6
Author: YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>
Date: Fri Jun 17 12:34:08 2016 +0900
tox.ini: Stop using zuul-cloner for venv
This should fix translation job.
Closes-Bug: #1568708
Change-Id: Ife4779e763753839ef90e6657cfaf2823efc1851
** Changed in: networking-midonet
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1568708
Title:
translation sync broken due to wrong usage of venv
Status in networking-midonet:
Fix Released
Status in networking-ovn:
Confirmed
Status in neutron:
Fix Committed
Status in Sahara:
Fix Released
Status in Sahara mitaka series:
Fix Released
Bug description:
post jobs cannot use zuul-cloner and have no access currently to
upper-constraints. See how nova or neutron itself handle this.
Right now the sync with translations fails:
https://jenkins.openstack.org/job/neutron-fwaas-propose-translation-
update/119/console
Please fix venv tox environment.
To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1568708/+subscriptions
References