Tests on Foreman core won't run right now due to
Bug #8747: google-api-client 0.8.0 causing undefined method `logger' for #<Foreman::Application:0x00000006efc800> - Foreman, which causes an error on
Rails startup.
Hopefully a new google-api-client will be released to fix the issue, but
if that doesn't come in the next couple of days then we could pin it
temporarily.
I'm out for a couple of weeks after today, so if a new gem is released,
could somebody please hit Build Now on test_develop
(http://ci.theforeman.org/job/test_develop/)? If that goes green, PRs
that are "pending" will start running tests automatically a while after.
···
--
Dominic Cleal
Red Hat Engineering
I can do it.
Shouldn't we pin it for now and change it later if there is a new gem
released?
I can pin it on Sunday if you prefer to wait.
···
On Thu, Dec 18, 2014 at 11:14 AM, Dominic Cleal wrote:
>
> Tests on Foreman core won't run right now due to
> http://projects.theforeman.org/issues/8747, which causes an error on
> Rails startup.
>
> Hopefully a new google-api-client will be released to fix the issue, but
> if that doesn't come in the next couple of days then we could pin it
> temporarily.
>
> I'm out for a couple of weeks after today, so if a new gem is released,
> could somebody please hit Build Now on test_develop
> (http://ci.theforeman.org/job/test_develop/)? If that goes green, PRs
> that are "pending" will start running tests automatically a while after.
>
> --
> 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/d/optout.
>
Thanks. Personally I prefer to wait these things out to avoid churn,
unless it coincides with a Foreman release (it doesn't). Most gem
maintainers are pretty responsive if a new release has broken things.
···
--
Dominic Cleal
Red Hat Engineering
On 18/12/14 10:33, Ori Rabin wrote:
I can do it.
Shouldn’t we pin it for now and change it later if there is a new gem
released?
I can pin it on Sunday if you prefer to wait.
On Thu, Dec 18, 2014 at 11:14 AM, Dominic Cleal <dcleal+g@redhat.com > mailto:dcleal+g@redhat.com> wrote:
Tests on Foreman core won't run right now due to
http://projects.theforeman.org/issues/8747, which causes an error on
Rails startup.
Hopefully a new google-api-client will be released to fix the issue, but
if that doesn't come in the next couple of days then we could pin it
temporarily.
I'm out for a couple of weeks after today, so if a new gem is released,
could somebody please hit Build Now on test_develop
(http://ci.theforeman.org/job/test_develop/)? If that goes green, PRs
that are "pending" will start running tests automatically a while after.
--
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/d/optout.
–
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Thanks. Personally I prefer to wait these things out to avoid churn,
> unless it coincides with a Foreman release (it doesn't). Most gem
> maintainers are pretty responsive if a new release has broken things.
We're trying to get a Katello 2.1 RC out before the holidays, I think
we'd appreciate it if you'd pin the gem as it's affecting our tests.
···
On Thu, Dec 18, 2014 at 10:35:12AM +0000, Dominic Cleal wrote:
–
Dominic Cleal
Red Hat Engineering
On 18/12/14 10:33, Ori Rabin wrote:
I can do it.
Shouldn’t we pin it for now and change it later if there is a new gem
released?
I can pin it on Sunday if you prefer to wait.
On Thu, Dec 18, 2014 at 11:14 AM, Dominic Cleal <dcleal+g@redhat.com > > mailto:dcleal+g@redhat.com> wrote:
Tests on Foreman core won't run right now due to
http://projects.theforeman.org/issues/8747, which causes an error on
Rails startup.
Hopefully a new google-api-client will be released to fix the issue, but
if that doesn't come in the next couple of days then we could pin it
temporarily.
I'm out for a couple of weeks after today, so if a new gem is released,
could somebody please hit Build Now on test_develop
(http://ci.theforeman.org/job/test_develop/)? If that goes green, PRs
that are "pending" will start running tests automatically a while after.
--
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/d/optout.
–
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
–
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/d/optout.
–
Stephen Benjamin
Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters
I've merged it, and Stephen has opened a PR to revert it [1] with a
link to the relevant PR in google-api-client. If they do a new release
tomorrow I can do the revert, after that I'm out until after new year.
