Re: [openstack-dev] [heat][ci][infra] telemetry test broken on oslo.messaging stable/queens
On Tue, Jun 05, 2018 at 10:47:17AM -0400, Ken Giusti wrote: > Hi, > > The telemetry integration test for oslo.messaging has started failing > on the stable/queens branch [0]. > > A quick review of the logs points to a change in heat-tempest-plugin > that is incompatible with the version of gabbi from queens upper > constraints (1.40.0) [1][2]. > > The job definition [3] includes required-projects that do not have > stable/queens branches - including heat-tempest-plugin. > > My question - how do I prevent this job from breaking when these > unbranched projects introduce changes that are incompatible with > upper-constrants for a particular branch? Tempest and plugins should be installed in a venv to isolate it's requirements from the rest of what devstack is installing during the job. This should be happening by default, the only place it gets installed on system python and where there is a potential conflict is if INSTALL_TEMPEST is set to True. See: https://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/tempest#n57 That flag only exists so we test tempest coinstallability in the gate, as well as for local devstack users. We don't install branchless projects on system python in stable jobs exactly because they're is a likely conflict between the stable branch's requirements and master's (which is what branchless projects follow). -Matt Treinish > > I've tried to use override-checkout in the job definition, but that > seems a bit hacky in this case since the tagged versions don't appear > to work and I've resorted to a hardcoded ref [4]. > > Advice appreciated, thanks! > > [0] https://review.openstack.org/#/c/567124/ > [1] > http://logs.openstack.org/24/567124/1/check/oslo.messaging-telemetry-dsvm-integration-rabbit/e7fdc7d/logs/devstack-gate-post_test_hook.txt.gz#_2018-05-16_05_20_05_624 > [2] > http://logs.openstack.org/24/567124/1/check/oslo.messaging-telemetry-dsvm-integration-rabbit/e7fdc7d/logs/devstacklog.txt.gz#_2018-05-16_05_19_06_332 > [3] > https://git.openstack.org/cgit/openstack/oslo.messaging/tree/.zuul.yaml?h=stable/queens#n250 > [4] https://review.openstack.org/#/c/572193/2/.zuul.yaml signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [heat][ci][infra] telemetry test broken on oslo.messaging stable/queens
Excerpts from Ken Giusti's message of 2018-06-05 10:47:17 -0400: > Hi, > > The telemetry integration test for oslo.messaging has started failing > on the stable/queens branch [0]. > > A quick review of the logs points to a change in heat-tempest-plugin > that is incompatible with the version of gabbi from queens upper > constraints (1.40.0) [1][2]. > > The job definition [3] includes required-projects that do not have > stable/queens branches - including heat-tempest-plugin. > > My question - how do I prevent this job from breaking when these > unbranched projects introduce changes that are incompatible with > upper-constrants for a particular branch? Aren't those projects co-gating on the oslo.messaging test job? How are the tests working for heat's stable/queens branch? Or telemetry? (whichever project is pulling in that tempest repo) > > I've tried to use override-checkout in the job definition, but that > seems a bit hacky in this case since the tagged versions don't appear > to work and I've resorted to a hardcoded ref [4]. > > Advice appreciated, thanks! > > [0] https://review.openstack.org/#/c/567124/ > [1] > http://logs.openstack.org/24/567124/1/check/oslo.messaging-telemetry-dsvm-integration-rabbit/e7fdc7d/logs/devstack-gate-post_test_hook.txt.gz#_2018-05-16_05_20_05_624 > [2] > http://logs.openstack.org/24/567124/1/check/oslo.messaging-telemetry-dsvm-integration-rabbit/e7fdc7d/logs/devstacklog.txt.gz#_2018-05-16_05_19_06_332 > [3] > https://git.openstack.org/cgit/openstack/oslo.messaging/tree/.zuul.yaml?h=stable/queens#n250 > [4] https://review.openstack.org/#/c/572193/2/.zuul.yaml __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [heat][ci][infra] telemetry test broken on oslo.messaging stable/queens
Hi, The telemetry integration test for oslo.messaging has started failing on the stable/queens branch [0]. A quick review of the logs points to a change in heat-tempest-plugin that is incompatible with the version of gabbi from queens upper constraints (1.40.0) [1][2]. The job definition [3] includes required-projects that do not have stable/queens branches - including heat-tempest-plugin. My question - how do I prevent this job from breaking when these unbranched projects introduce changes that are incompatible with upper-constrants for a particular branch? I've tried to use override-checkout in the job definition, but that seems a bit hacky in this case since the tagged versions don't appear to work and I've resorted to a hardcoded ref [4]. Advice appreciated, thanks! [0] https://review.openstack.org/#/c/567124/ [1] http://logs.openstack.org/24/567124/1/check/oslo.messaging-telemetry-dsvm-integration-rabbit/e7fdc7d/logs/devstack-gate-post_test_hook.txt.gz#_2018-05-16_05_20_05_624 [2] http://logs.openstack.org/24/567124/1/check/oslo.messaging-telemetry-dsvm-integration-rabbit/e7fdc7d/logs/devstacklog.txt.gz#_2018-05-16_05_19_06_332 [3] https://git.openstack.org/cgit/openstack/oslo.messaging/tree/.zuul.yaml?h=stable/queens#n250 [4] https://review.openstack.org/#/c/572193/2/.zuul.yaml -- Ken Giusti (kgiu...@gmail.com) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
