On 12/27/2015 08:48 PM, Darragh Bailey wrote:
On 26 Dec 2015 12:55, "Jeremy Stanley" mailto:fu...@yuggoth.org>> wrote:
>
> Presumably we could rename our tox macro so that it doesn't shadow
> the recently added tox builtin, but this problem will occur any time
> support for another plugin is
On 26 Dec 2015 12:55, "Jeremy Stanley" wrote:
>
> Presumably we could rename our tox macro so that it doesn't shadow
> the recently added tox builtin, but this problem will occur any time
> support for another plugin is added which uses the same name as
> something in our existing configuration so
On 2015-12-26 08:43:39 +0100 (+0100), Andreas Jaeger wrote:
[...]
> WARNING:jenkins_jobs.registry:You have a macro ('tox') defined for 'builder'
> component type that is masking an inbuilt definition
>
> Can we cut this noise down, please?
[...]
Presumably we could rename our tox macro so that it
I see now lots of these warning for the project-config-layout gate:
http://logs.openstack.org/40/261540/2/check/gateaproject-config-layout/57a6dd6/console.html
WARNING:jenkins_jobs.registry:You have a macro ('tox') defined for
'builder' component type that is masking an inbuilt definition
Ca
