You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2012/09/26 10:20:09 UTC
[jira] [Closed] (BUILDR-427) buildr 1.4.0rc3 Windows 7 spec
failures
[ https://issues.apache.org/jira/browse/BUILDR-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald closed BUILDR-427.
-------------------------------
Resolution: Fixed
Last time I checked we were all green on windows
> buildr 1.4.0rc3 Windows 7 spec failures
> ---------------------------------------
>
> Key: BUILDR-427
> URL: https://issues.apache.org/jira/browse/BUILDR-427
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: Microsoft Windows 7 Professional 6.1.7600 N/A Build 7600
> ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]
> Reporter: Will Rogers
> Assignee: Peter Donald
> Fix For: 1.4.8
>
> Attachments: specs_buildr_1.4.0rc3.html
>
>
> I ran buildr's tests ("rake spec") and got 52 failures. Output attached.
> Many of the problems appear to be Windows path issues (especially the
> URI specs). There are some failures under "Buildr::Application gems"
> that look like more fixable gem version mismatch problems, though,
> e.g.:
> "should return one entry for each gem specified in buildr.yaml
> can't activate rspec (= 1.3.0, runtime) for [], already activated
> rspec-1.2.9 for []"
> ...and it looks like calling File.utime throws a Permission denied
> error every time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira