The test failures are different if I run autotest or rake spec. Suuuweeeet!
After touching all the specs, I got some failures the first time autotest
loads but they pass on subsequent runs, so there is still something subtle
with timing and state effecting the results.
The end result is I have one test that doesn't pass under any circumstance
so far:
1)
'Puppet::Type::File when writing files should fail if no backup can be
performed' FAILED
expected: "bar\n",
got: "foo" (using ==)
./spec/integration/type/file.rb:54:
/Users/andrew/git/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:22:in
`run'
/Users/andrew/git/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in
`each'
/Users/andrew/git/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in
`run'
That looks like a brand new test, can anyone else confirm this works for
them? Looks suspicious...
On Mon, Aug 10, 2009 at 8:13 AM, Markus <[email protected]> wrote:
>
> Andrew --
>
> There are some know issues with the testing setup that can cause
> problems similar to this. They are sporadic because they stem from a
> failure to isolate tests (allowing the consequences of some tests to
> effect others later in the run). They are tedious to track down because
> the order in which the tests are run depends on several factors,
> including the time stamp on the files in the spec directory.
>
> To help find (and fix) this particular problem, capture the timestamps
> of all files in the spec directory (e.g. with something like
>
> ls -l $(find spec -name '*.rb') > spec_file_times
>
> and capturing full results of the spec run
>
> rake spec > rake_spec_results
>
> and then attaching them to a ticket w. a description of the symptoms.
>
>
> To just work around the problem (either after capturing the diagnostic
> information or instead, if you're in a hurry) just use
>
> touch $(find spec -name '*.rb)
>
> to set all the spec files to the same time. This should make the
> symptoms go away for you.
>
> -- Markus
>
>
>
> On Mon, 2009-08-10 at 00:14 -0600, Andrew Shafer wrote:
> > I have failures running specs against master on OS X.
> >
> > Is anyone else seeing failures running all the specs?
> >
> > Some appear to be some assumptions about tmp files, and some seem to
> > be changes in behavior
> >
> >
> > 'Puppet::Type::File when writing files should fail if no backup can be
> > performed' FAILED
> > expected: "bar\n",
> > got: "foo" (using ==)
> >
> > Puppet::Error in 'Puppet::SSL::CertificateRequest should be able to
> > save CSRs'
> > Cannot save luke.madstop.com; parent
> > directory /tmp/csr_integration_testing.36653.0/ssl/ca/requests does
> > not exist
> >
> > Puppet::Error in 'Puppet::SSL::CertificateRequest should be able to
> > find saved certificate requests via the Indirector'
> > Cannot save luke.madstop.com; parent
> > directory /tmp/csr_integration_testing.36653.0/ssl/ca/requests does
> > not exist
> >
> > Puppet::Error in 'Puppet::SSL::CertificateRequest should save the
> > completely CSR when saving'
> > Cannot save luke.madstop.com; parent
> > directory /tmp/csr_integration_testing.36653.0/ssl/ca/requests does
> > not exist
> >
> > 'Puppet::Util::Settings should be able to make needed directories'
> > FAILED
> > expected directory?("/tmp/main.36653.0") to return true, got false
> >
> > Errno::ENOENT in 'Puppet::Util::Settings should make its directories
> > with the corret modes'
> > No such file or directory - /tmp/main.36653.0
> >
> > Puppet::Error in 'Puppet::SSL::CertificateRevocationList should be
> > able to read in written out CRLs with no revoked certificates'
> > Cannot save ca; parent
> > directory /tmp/ca_integration_testing.36653.0/ssl/ca does not exist
> >
> > Puppet::Error in 'Puppet::Type::MetaParamNoop should accept true as a
> > value'
> > Invalid parameter source(:source)
> >
> > Puppet::Error in 'Puppet::Type::MetaParamNoop should accept false as a
> > value'
> > Invalid parameter source(:source)
> >
> > >
> --
> Markus <[email protected]>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
