[chef] Re: Re: Chef-DK build failure

[Daniel DeLeo < >]

On Saturday, June 27, 2015 at 10:54 AM, Jay Mundrawala wrote:

> The maintainers can retrigger, however you may need to rebase if a fix is 
> applied to chefdk

I think this failure is caused by a bug in the FFI library. We have made a 
change to ChefDK to pin the version of FFI to the not-broken one. Therefore 
if we were to re-run your build it would just fail the same way. If you pull 
our latest master and rebase your changes on top of it, then re-push (in this 
case you’ll have to force push), appveyor will build again automatically.

--  
Daniel DeLeo  
>  
> On Sat, Jun 27, 2015, 10:28 AM Joe Nuspl 
> <
 
>  
> (mailto:
 )>
>  wrote:
> > A process question…
> >  
> > I have a PR, https://github.com/chef/chef-dk/pull/441, but the AppVeyor ;
> > build is failing. This seems to be an ecosystem error and not due to my 
> > change:
> >  
> > > Installing chef 12.4.0 with native extensions
> > >  
> > > Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native 
> > > extension.
> > > …
> > > C:/Ruby200/lib/ruby/gems/2.0.0/gems/win32-eventlog-0.6.3/lib/win32/eventlog.rb:211:
> > >  [BUG] Segmentation fault
> >  
> >  
> >  
> >  
> > Once the upstream issue is resolved, do I need to retrigger the AppVeyor 
> > build (by pushing a dummy commit) or will it automatically happen?
> >  
> > Thanks.
> >  
> > Joe