I'm getting the following spec failures on master:
A full (integration spec) installation for platform `ios'
- generates documentation of all pods by default [ERROR:
Errno::ENOENT]
Pod::Downloader
for Git
- check's out a specific commit [FAILED]
Pod::Generator::Documentation
- returns reads correctly the Pod documentation [FAILED]
- returns the Pod documentation options [FAILED]
- creates the html [FAILED]
I'm wanting to merge master into my relative_pods_root so I can wrap
up changes there, but I'm weary to continue while I have test
failures. Are these failing for you as well?
On Mon, Mar 19, 2012 at 6:42 PM, Ben Scheirman <subdigi...@gmail.com> wrote: > I'm getting the following spec failures on master:
> A full (integration spec) installation for platform `ios' > - generates documentation of all pods by default [ERROR: > Errno::ENOENT]
> Pod::Downloader > for Git > - check's out a specific commit [FAILED]
> Pod::Generator::Documentation > - returns reads correctly the Pod documentation [FAILED] > - returns the Pod documentation options [FAILED] > - creates the html [FAILED]
> I'm wanting to merge master into my relative_pods_root so I can wrap > up changes there, but I'm weary to continue while I have test > failures. Are these failing for you as well?
I originally got an error because appledoc wasn't found on my system, but I installed it with homebrew (and added a relevant check for this in `rake bootstrap` for others).
Any other ideas? These were all passing about a week ago when I last fetched from origin.
On Mar 19, 2012, at 11:09 AM, Victor Ilyukevich wrote:
> Maybe you forgot to update submodules after last checkout?
> On Mon, Mar 19, 2012 at 6:42 PM, Ben Scheirman <subdigi...@gmail.com> wrote: > I'm getting the following spec failures on master:
> A full (integration spec) installation for platform `ios' > - generates documentation of all pods by default [ERROR: > Errno::ENOENT]
> Pod::Downloader > for Git > - check's out a specific commit [FAILED]
> Pod::Generator::Documentation > - returns reads correctly the Pod documentation [FAILED] > - returns the Pod documentation options [FAILED] > - creates the html [FAILED]
> I'm wanting to merge master into my relative_pods_root so I can wrap > up changes there, but I'm weary to continue while I have test > failures. Are these failing for you as well?
> I originally got an error because appledoc wasn't found on my system, but I installed it with homebrew (and added a relevant check for this in `rake bootstrap` for others).
> Any other ideas? These were all passing about a week ago when I last fetched from origin.
> On Mar 19, 2012, at 11:09 AM, Victor Ilyukevich wrote:
>> I've just run `rake spec` on the latest code from master and every test passes:
>> Maybe you forgot to update submodules after last checkout?
>> On Mon, Mar 19, 2012 at 6:42 PM, Ben Scheirman <subdigi...@gmail.com> wrote: >> I'm getting the following spec failures on master:
>> A full (integration spec) installation for platform `ios' >> - generates documentation of all pods by default [ERROR: >> Errno::ENOENT]
>> Pod::Downloader >> for Git >> - check's out a specific commit [FAILED]
>> Pod::Generator::Documentation >> - returns reads correctly the Pod documentation [FAILED] >> - returns the Pod documentation options [FAILED] >> - creates the html [FAILED]
>> I'm wanting to merge master into my relative_pods_root so I can wrap >> up changes there, but I'm weary to continue while I have test >> failures. Are these failing for you as well?
That fixed 3 of the specs. Now the remaining failure:
Pod::Generator::Documentation - creates the html [FAILED]
Bacon::Error: false.true?() failed spec/unit/generator/documentation_spec.rb:56:in `block (2 levels) in <top (required)>': Pod::Generator::Documentation - creates the html /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `call' /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `block in it' /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:54:in `it' spec/unit/generator/documentation_spec.rb:55:in `block in <top (required)>' spec/unit/generator/documentation_spec.rb:3:in `<top (required)>'
Errno::ENOENT: No such file or directory - /Users/ben/projects/CocoaPods/tmp/Pods/Documentation/JSONKit/html/index.htm l /Users/ben/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/pathname.rb:776:in `read': A full (integration spec) installation for platform `ios' - generates documentation of all pods by default /Users/ben/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/pathname.rb:776:in `read' spec/integration_spec.rb:150:in `block (3 levels) in <top (required)>' /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `call' /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `block in it' /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:54:in `it' spec/integration_spec.rb:138:in `block (2 levels) in <top (required)>' spec/integration_spec.rb:31:in `block in <top (required)>' spec/integration_spec.rb:30:in `each' spec/integration_spec.rb:30:in `<top (required)>'
> On Mar 19, 2012, at 5:13 PM, Ben Scheirman wrote:
>> My submodules are updated.
>> I originally got an error because appledoc wasn't found on my system, but I installed it with homebrew (and added a relevant check for this in `rake bootstrap` for others).
>> Any other ideas? These were all passing about a week ago when I last fetched from origin.
>> On Mar 19, 2012, at 11:09 AM, Victor Ilyukevich wrote:
>>> I've just run `rake spec` on the latest code from master and every test passes:
>>> Maybe you forgot to update submodules after last checkout?
>>> On Mon, Mar 19, 2012 at 6:42 PM, Ben Scheirman <subdigi...@gmail.com> wrote: >>> I'm getting the following spec failures on master:
>>> A full (integration spec) installation for platform `ios' >>> - generates documentation of all pods by default [ERROR: >>> Errno::ENOENT]
>>> Pod::Downloader >>> for Git >>> - check's out a specific commit [FAILED]
>>> Pod::Generator::Documentation >>> - returns reads correctly the Pod documentation [FAILED] >>> - returns the Pod documentation options [FAILED] >>> - creates the html [FAILED]
>>> I'm wanting to merge master into my relative_pods_root so I can wrap >>> up changes there, but I'm weary to continue while I have test >>> failures. Are these failing for you as well?
Oh wait, I just remember having similar failures, which was due to appledoc not being installed correct. Does your output look the same?
% ls -l ~/Library/Application\ Support/appledoc/ total 0 drwxr-xr-x 3 eloy wheel 102 8 dec 14:49 docset drwxr-xr-x 8 eloy wheel 272 8 dec 14:49 html
If not, then that's the problem. The instructions, that the homebrew formula prints, out are incorrect I think, but at the time I thought I had probably done something wrong.
Nonetheless, we should raise an exception if appledoc exits with a failure so that these problems are clear when someone runs into them.
>> We really need to make that work transparently.
>> On Mar 19, 2012, at 5:13 PM, Ben Scheirman wrote:
>>> My submodules are updated.
>>> I originally got an error because appledoc wasn't found on my system, but I installed it with homebrew (and added a relevant check for this in `rake bootstrap` for others).
>>> Any other ideas? These were all passing about a week ago when I last fetched from origin.
>>> On Mar 19, 2012, at 11:09 AM, Victor Ilyukevich wrote:
>>>> I've just run `rake spec` on the latest code from master and every test passes:
>>>> Maybe you forgot to update submodules after last checkout?
>>>> On Mon, Mar 19, 2012 at 6:42 PM, Ben Scheirman <subdigi...@gmail.com> wrote: >>>> I'm getting the following spec failures on master:
>>>> A full (integration spec) installation for platform `ios' >>>> - generates documentation of all pods by default [ERROR: >>>> Errno::ENOENT]
>>>> Pod::Downloader >>>> for Git >>>> - check's out a specific commit [FAILED]
>>>> Pod::Generator::Documentation >>>> - returns reads correctly the Pod documentation [FAILED] >>>> - returns the Pod documentation options [FAILED] >>>> - creates the html [FAILED]
>>>> I'm wanting to merge master into my relative_pods_root so I can wrap >>>> up changes there, but I'm weary to continue while I have test >>>> failures. Are these failing for you as well?
That folder doesn't exist on my machine. I must have missed the post install instructions from homebrew.
Looking at it now it seems as if the appledoc brew should be doing that linking step for us in the future.
I added a step in `rake bootstrap` so that others could know to install it if it's not present on their system. But we still should have the check for the error code.
> Oh wait, I just remember having similar failures, which was due to appledoc not being installed correct. Does your output look the same?
> % ls -l ~/Library/Application\ Support/appledoc/ > total 0 > drwxr-xr-x 3 eloy wheel 102 8 dec 14:49 docset > drwxr-xr-x 8 eloy wheel 272 8 dec 14:49 html
> If not, then that's the problem. The instructions, that the homebrew formula prints, out are incorrect I think, but at the time I thought I had probably done something wrong.
> Nonetheless, we should raise an exception if appledoc exits with a failure so that these problems are clear when someone runs into them.
> Eloy
> On 19 mrt. 2012, at 17:56, Ben Scheirman wrote:
>> That fixed 3 of the specs. Now the remaining failure:
>> Pod::Generator::Documentation >> - creates the html [FAILED]
>> Bacon::Error: false.true?() failed >> spec/unit/generator/documentation_spec.rb:56:in `block (2 levels) in <top (required)>': Pod::Generator::Documentation - creates the html >> /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `call' >> /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `block in it' >> /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:54:in `it' >> spec/unit/generator/documentation_spec.rb:55:in `block in <top (required)>' >> spec/unit/generator/documentation_spec.rb:3:in `<top (required)>'
>> Errno::ENOENT: No such file or directory - /Users/ben/projects/CocoaPods/tmp/Pods/Documentation/JSONKit/html/index.htm l >> /Users/ben/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/pathname.rb:776:in `read': A full (integration spec) installation for platform `ios' - generates documentation of all pods by default >> /Users/ben/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/pathname.rb:776:in `read' >> spec/integration_spec.rb:150:in `block (3 levels) in <top (required)>' >> /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `call' >> /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:57:in `block in it' >> /Users/ben/.rvm/gems/ruby-1.9.2-p180/gems/mocha-on-bacon-0.2.0/lib/mocha-on -bacon.rb:54:in `it' >> spec/integration_spec.rb:138:in `block (2 levels) in <top (required)>' >> spec/integration_spec.rb:31:in `block in <top (required)>' >> spec/integration_spec.rb:30:in `each' >> spec/integration_spec.rb:30:in `<top (required)>'
>> On Mar 19, 2012, at 11:21 AM, Eloy Durán wrote:
>>> Hey Ben, try:
>>> $ rm -rf spec/fixtures/banana-lib
>>> We really need to make that work transparently.
>>> On Mar 19, 2012, at 5:13 PM, Ben Scheirman wrote:
>>>> My submodules are updated.
>>>> I originally got an error because appledoc wasn't found on my system, but I installed it with homebrew (and added a relevant check for this in `rake bootstrap` for others).
>>>> Any other ideas? These were all passing about a week ago when I last fetched from origin.
>>>> On Mar 19, 2012, at 11:09 AM, Victor Ilyukevich wrote:
>>>>> I've just run `rake spec` on the latest code from master and every test passes:
>>>>> Maybe you forgot to update submodules after last checkout?
>>>>> On Mon, Mar 19, 2012 at 6:42 PM, Ben Scheirman <subdigi...@gmail.com> wrote: >>>>> I'm getting the following spec failures on master:
>>>>> A full (integration spec) installation for platform `ios' >>>>> - generates documentation of all pods by default [ERROR: >>>>> Errno::ENOENT]
>>>>> Pod::Downloader >>>>> for Git >>>>> - check's out a specific commit [FAILED]
>>>>> Pod::Generator::Documentation >>>>> - returns reads correctly the Pod documentation [FAILED] >>>>> - returns the Pod documentation options [FAILED] >>>>> - creates the html [FAILED]
>>>>> I'm wanting to merge master into my relative_pods_root so I can wrap >>>>> up changes there, but I'm weary to continue while I have test >>>>> failures. Are these failing for you as well?
