Hi,
just noticed that the matrix jobs for the smart proxy, both for PR's and
develop branch is/will fail since the release of Puppet 3.4.0. The jobs
which should use puppet 3.2 actually uses latest and when it will use 3.4
will fails some 20 tests. This also happens locally if you install
gem:puppet-3.4.0
To summarise:
Jenkins:
- test_proxy_develop_pull_request fix 3.2 to actually use 3.2 and add new
jobb for 3.4
- test_proxy_develop fix 3.2 to actually use 3.2 and add new jobb for 3.4
smart-proxy:
- Fixa failing tests in: puppet_environment_test and puppet_class_test
(all fails on NoMethodError: undefined method `mode=' for
#<Puppet::Settings::AutosignSetting:0x007fed9c934928> )
See:
http://ci.theforeman.org/job/test_proxy_develop_pull_request/187/puppet=3.2,ruby=2.0.0/console
Should I write an issue on the failing tests and/or for the CI setup?
Merry X-Mas // Rickard
Ok,
Then there is only the issue that the job:
test_proxy_develop/puppet=3.2,ruby=2.0.0 actually uses *puppet (3.4.1) *(the
same goes for test_proxy_develop_pull_request)
// Rickard
···
On Thu, Jan 2, 2014 at 10:25 AM, Dominic Cleal wrote:
Hi Rickard,
On 24/12/13 21:48, Rickard von Essen wrote:
Hi,
just noticed that the matrix jobs for the smart proxy, both for PR’s and
develop branch is/will fail since the release of Puppet 3.4.0. The jobs
which should use puppet 3.2 actually uses latest and when it will use
3.4 will fails some 20 tests. This also happens locally if you install
gem:puppet-3.4.0
To summarise:
Jenkins:
- test_proxy_develop_pull_request fix 3.2 to actually use 3.2 and add
new jobb for 3.4
- test_proxy_develop fix 3.2 to actually use 3.2 and add new jobb for
3.4
smart-proxy:
- Fixa failing tests in: puppet_environment_test and puppet_class_test
(all fails on NoMethodError: undefined method `mode=’ for
#Puppet::Settings::AutosignSetting:0x007fed9c934928 )
See:
http://ci.theforeman.org/job/test_proxy_develop_pull_request/187/puppet=3.2,ruby=2.0.0/console
Should I write an issue on the failing tests and/or for the CI setup?
Don’t worry about it for now, it’s a known and fixed issue in Puppet
3.4.0/1 (https://tickets.puppetlabs.com/browse/PUP-1015), and they’re
planning a 3.4.2 release imminently which should get this working again.
Thanks,
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Yes, that was intentional - I wanted it to use the very latest, where
the version is ~> 3.2, just so we find issues like this ASAP. Sorry for
the disruption, hopefully it'll go away in a few days…
···
--
Dominic Cleal
Red Hat Engineering
On 02/01/14 13:25, Rickard von Essen wrote:
Ok,
Then there is only the issue that the job:
/test_proxy_develop/puppet=3.2,ruby=2.0.0/ actually uses /puppet
(3.4.1) /(the same goes for /test_proxy_develop_pull_request)/
// Rickard
On Thu, Jan 2, 2014 at 10:25 AM, Dominic Cleal <dcleal@redhat.com > mailto:dcleal@redhat.com> wrote:
Hi Rickard,
On 24/12/13 21:48, Rickard von Essen wrote:
> Hi,
>
> just noticed that the matrix jobs for the smart proxy, both for
PR's and
> develop branch is/will fail since the release of Puppet 3.4.0. The
jobs
> which should use puppet 3.2 actually uses latest and when it will use
> 3.4 will fails some 20 tests. This also happens locally if you install
> gem:puppet-3.4.0
>
> To summarise:
> Jenkins:
> - test_proxy_develop_pull_request fix 3.2 to actually use 3.2
and add
> new jobb for 3.4
> - test_proxy_develop fix 3.2 to actually use 3.2 and add new jobb
for 3.4
> smart-proxy:
> - Fixa failing tests in: puppet_environment_test and
puppet_class_test
> (all fails on NoMethodError: undefined method `mode=' for
> #<Puppet::Settings::AutosignSetting:0x007fed9c934928> )
>
> See:
>
http://ci.theforeman.org/job/test_proxy_develop_pull_request/187/puppet=3.2,ruby=2.0.0/console
>
> Should I write an issue on the failing tests and/or for the CI setup?
Don't worry about it for now, it's a known and fixed issue in Puppet
3.4.0/1 (https://tickets.puppetlabs.com/browse/PUP-1015), and they're
planning a 3.4.2 release imminently which should get this working again.
Thanks,
--
Dominic Cleal
Red Hat Engineering
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev%2Bunsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
