I consistently fail at html/template. At one point I was hanging indefinitely on some other tests (net/http I think) due to goroutines never giving up control, setting GOMAXPROCS=2 fixed it. I'm not sure if that's still an issue though.
I have a 386 which is capable of SSE2, and I'm up to date with sources. On Fri, May 24, 2013 at 8:29 AM, <lu...@proxima.alt.za> wrote: >> which tests does it break? ?c compile -0. as 0 (which is incorrect), >> and print(2)'s %g and %f print -0. as 0. could this or other bits of >> non-ieee conformance in the system be the real issue? > > They could be significant, but only where floating point is involved, > the failures I noted do not have an obvious floating point component - > except when SSE2 is required and not available. > > So let's start with a show of hands. Who can consistently run the Go > build tests (run.rc --no-rebuild in $GOROOT/src after a successful > make.rc) without failure and what is the Plan 9 (i386) environment > applicable? > > Factors I believe are relevant are CPU type, including SSE2 > capabilities, which fork of Plan 9 (current Bell Labs > distribution/prior to the 21-bit Rune update (maybe), nix, 9atom, > 9front, are there others? I know 9vx is broken, sadly.), local > updates may be pertinent too. Also, I'm assuming, with Christopher, > that we're dealing with Go "tip", if it's an older version, that may > point us in some useful direction. > > Also, for the more adventurous, CL 7987044 (from memory - prompt me if > it's wrong) adds ARM capabilities, modulo some changes from Gorka I > have yet to identify. I will be going off topic for a while, I need > to rebuild the local ESXi instance and that will probably take longer > than the weekend, so I can't promise much help until I'm done. But I > will be interested in the outcome of this poll. > > If you can, pass the request on, there may be people this message > can't reach. > > Lucio. > >
