-
Notifications
You must be signed in to change notification settings - Fork 17.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FAIL: quick.TestCheckEqual on MacOS 10.5 #476
Labels
Comments
You say in the instructions to checkout a release; however, your hg identify is returning that you are using tip. Were they one and the same at that point, or is that an error? I suggest checking tip out again, I am not seeing this error on my 10.5-{386, amd64} or 10.6-{386, amd64} |
Thanks for the answer. The output from "hg identify" is the one after I executed "hg pull -u". I did the following just right now again (sorry for german hg output...): ---- copy/paste from terminal ----- Stefans-MacBook-2:vaillant go>hg pull -u Hole von https://go.googlecode.com/hg/ Suche nach Änderungen Füge Änderungssätze hinzu Füge Manifeste hinzu Füge Dateiänderungen hinzu Fügte 27 Änderungssätze mit 51 Änderungen zu 41 Dateien hinzu 41 files updated, 0 files merged, 0 files removed, 0 files unresolved Stefans-MacBook-2:vaillant go>cd src Stefans-MacBook-2:vaillant src>./all.bash [many - many lines removed] /Users/vaillant/bin/gopack grc _test/testing/quick.a _gotest_.8 --- FAIL: quick.TestCheckEqual fIntptr: #16: failed on input (*int)(0x258a60). Output 1: (*int)(0x258a78). Output 2: (*int)(0x258aa0) FAIL make[2]: *** [test] Error 1 make[1]: *** [testing/quick.test] Error 2 make: *** [run] Error 2 Stefans-MacBook-2:vaillant go>cd .. Stefans-MacBook-2:vaillant go>hg id -i -r tip https://go.googlecode.com/hg/ 5b8076384e46 Stefans-MacBook-2:vaillant go>hg identify 5b8076384e46 tip ---------------- end of copy/paste ---------- I have not used hg before, so if I used it incorrectly, let me know. BTW: sieve1.go program runs succesfully. |
This is a very strange error. It suggests that there was memory corruption during the run. I have managed to reproduce it on Snow Leopard by syncing to the specific version you were using and then using export GOGC=0 to trigger extra garbage collections. The strangest part is that I can only reproduce it by running "make test" in testing/quick. If I run "gotest" (which is what "make test" eventually does) then it doesn't fail. Owner changed to r...@golang.org. Status changed to Accepted. |
http://golang.org/cl/190041 Status changed to Started. |
This issue was closed by revision da225c2. Status changed to Fixed. Merged into issue #-. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by stefan.vaillant:
The text was updated successfully, but these errors were encountered: