Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
all: tests fail on AppliedMicro X-Gene ARM64 processor #11957
Comments
|
Can you please include as much detail as possible. Does it build pass without using task set ? Thanks Dave
|
ikitayama
commented
Jul 31, 2015
|
No it did not, without the taskset twice the build stopped at: Testing packages.ok archive/tar 0.082s |
ikitayama
commented
Jul 31, 2015
|
Is there a way to skip testing as an interim solution to complete the build process? |
Yes, use Can I ask you to please include more information, as much as possible, insane amounts, the entire output if possible via a gist. Thanks Dave |
|
Which operating system are you using, which version, can you show uname -a, lsb_release -a (or equivalent if you are not in a debian world), etc. |
|
Please take a look at https://github.com/golang/go/blob/master/CONTRIBUTING.md, and let us know your information. Otherwise, this issue never gets anywhere. |
mikioh
changed the title from
Native build fails on AppliedMicro X-Gene
to
all: tests fails on AppliedMicro X-Gene ARM64 processor
Jul 31, 2015
mikioh
changed the title from
all: tests fails on AppliedMicro X-Gene ARM64 processor
to
all: tests fail on AppliedMicro X-Gene ARM64 processor
Jul 31, 2015
ikitayama
commented
Jul 31, 2015
|
I've put information as much as I can, see the gist link below. |
|
Thank you. The arm64 builders on the build.golang.org dashboard are identical machines (I suspect we all have the same development hardware kit, in the same cheap black case), which do not replicate your results. Can you help me by explaining what you see and more details about your operating system. Both arm64 builders I run are running Ubuntu 14.04. |
|
Oh, here is one thing
^ please don't do that. You will be overwriting the toolchain you are using to rebuild. I recommend this procedure
Then copy the resulting .tgz file to your arm64 host and unextract it to $HOME
This is the process that the builders use and I think you will find success with it. |
ikitayama
commented
Jul 31, 2015
|
I am on Fedora release 22, Kernel version is 4.0.8-300.fc22.aarch64. All packages are synched daily. I was using the toolchain built on my Mac OS X, is this not supported at all? I will try to built it fresh on a linux/amd64 machine and see if there's any difference. |
Yes, that is supported, there is no problem in building the bootstrap environment on a mac. I believe the problem is you have set
Which is causing the bootstrap environment to be overwritten during the build process. |
ikitayama
commented
Jul 31, 2015
|
I learned the setting from the GoArm Wiki, recipe is described at the bottom of the page. Building Go from all.bash fails even in the non-parallel set-up. Make.bash fails also in parallel mode. |
ikitayama
commented
Jul 31, 2015
|
Output of taskset 1 make.bash is below: |
|
I am sorry but I cannot help you if you use taskset. That is not how go should be built.
|
ikitayama
commented
Jul 31, 2015
|
OK. I'll drop the trick from now on and tried to build go without it. |
ikitayama
commented
Jul 31, 2015
|
make.bash worked this time. $ go version Thank you very much for your support, Dave. |
|
I'm glad to hear that. You may want to try all.bash to also run the tests on your system. If you want to raise an issue about the taskset failure that would be fine, but it is not a priority for the upcoming 1.5 release.
|
ikitayama
commented
Jul 31, 2015
|
Will do that next week. How do we work around the lack of memory issue, I think that's preventing |
|
All the builders on the dashboard are mustang machines, we have no problems with available memory.
|
|
I removed the recommendation on the wiki page to set GOROOT=GOROOT_BOOTSTRAP. That is not supported. As far as I can tell, this issue is fixed, so closing. |
ianlancetaylor
closed this
Jul 31, 2015
ikitayama
commented
Aug 3, 2015
|
I'll report back the all.bash results on Fedora 22 here when I am granted access to a 32GB Mustang. |
|
Thank you. To repeat, 512mb per core is sufficient for a successful build. On Mon, 3 Aug 2015 10:19 Itaru Kitayama notifications@github.com wrote:
|
ikitayama
commented
Aug 4, 2015
|
all.bash went ok this morning without an issue on a 32GB of Mustang (Fedora 21) in the Linaro server lab. The full log of the build and tests: |
ikitayama commentedJul 31, 2015
I've been trying to build go natively on X-Gene, however:
$ taskset 1 ./all.bash
fails.