PPC: pure ruby `rake test` fails
Reported by seydar | November 28th, 2009 @ 05:46 PM
We have a bunch of errors here: http://pastie.org/718298
recreation:
rake build
rake prepare; rake test
rake clean
rake prepare; rake test
A bunch of errors. After previous exploration in similar bugs, if we can fix #8 and #9 then most of those errors would go away.
Comments and changes to this ticket
-
seydar November 28th, 2009 @ 07:12 PM
This appears to be specific to Tiger/PPC/32bit computers. Maybe others though...
-
Michael Edgar November 28th, 2009 @ 07:26 PM
Big-endian specific.
Still looking at it, but priority is low.
-
Michael J. Edgar November 28th, 2009 @ 07:36 PM
- State changed from “new” to “open”
- Tag cleared.
-
Michael J. Edgar November 28th, 2009 @ 07:37 PM
- Title changed from “pure ruby `rake test` fails” to “PPC: pure ruby `rake test` fails”
-
seydar November 28th, 2009 @ 08:09 PM
- Assigned user cleared.
- State changed from “open” to “resolved”
We fixed this. Turns out big endian systems weren't being properly identified.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Rethink Version Control.- http://amp.carboni.ca/
Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.
Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.
Michael J. Edgar