Just to add a bit more info to this, in case it's helpful -- this same patch had been backported to all our stable branches (pike, ocata, and even newton). The branches from pike and below were fine, but queens and master (which is pinned to queens) were failing. We also were able to make queens pass by changing a script that we were using to attempt to ensure that the requirements.txt from the appropriate branch was getting used: https://github.com/openstack/group-based-policy/blob/master/tools/tox_install.sh
In this case, we changed to what the other stable branches were doing, which was just a pip install: https://review.openstack.org/#/c/648962/ However, the same change didn't fix the master branch. Please don't hold the fact that I still use yahoo email, don't know to how use copy/paste hot-keys correctly, and work on a project that is pinned to stable/queens against me :-). cheers, -Thomas On Monday, April 8, 2019, 9:14:25 AM EDT, Thomas Bachman <[email protected]> wrote: Apparently I'm still learning how to use email (drat those hot-keys!). This is the patch: https://review.openstack.org/#/c/647475/ You can see that the patch initially passed CI on 3/25/2019, but then when the patch was going to be merged (no changes in the code), the merge job failed. The way it failed is also interesting -- the error in the pep8 job indicates that the DB migration script isn't available, which is part of the python code (i.e. suggesting that our repo's package isn't even installed?): http://logs.openstack.org/75/647475/1/gate/openstack-tox-pep8/5543fd1/job-output.txt.gz#_2019-03-28_23_14_40_267120 The py27 job suggests the same: http://logs.openstack.org/75/647475/1/gate/openstack-tox-py27/8a13368/job-output.txt.gz#_2019-03-28_23_14_59_087759 Does anyone know of any changes between 3/25/2019 and 3/28/2019 that would result in our package not being included? Again, please let me know if this is the wrong list for such issues, and thanks in advance for any/all help! cheers, -Thomas On Monday, April 8, 2019, 9:05:48 AM EDT, Thomas Bachman <[email protected]> wrote: I'm hoping that this is the right list for the topic, and apologize in advance if this is too broad an audience. Our project -- group-based-policy -- is behind the upstream master branches, and as a result, we've been pinning our master branch to the last supported release (in our case, stable/queens). This has been working for some time, but ran into troubles with this patch:
_______________________________________________ OpenStack-Infra mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
