On Fri, Jul 10, 2020 at 1:19 PM Alastair Neil wrote:
>
> I'm not sure how I would check do you have suggestions? Also, is there a way
> to just run the failing test rather than redoing the whole build?
> Documentation on the build process seems sparse.
To run the time package tests as the buil
I'm not sure how I would check do you have suggestions? Also, is there a
way to just run the failing test rather than redoing the whole build?
Documentation on the build process seems sparse.
On Friday, 10 July 2020 15:54:02 UTC-4, David Riley wrote:
>
> On Jul 10, 2020, at 3:02 PM, Alastair N
On Jul 10, 2020, at 3:02 PM, Alastair Neil wrote:
>
>
> It's an old but not an especially slow machine: dual 8 core E5-2670 Xeon
> with 64 GB Ram.
> I wil try
> GO_TEST_TIMEOUT_SCALE=4
I've successfully built on an older and slower (pre-Nehalem) 8-core Xeon with a
similar RAM load just last
It's an old but not an especially slow machine: dual 8 core E5-2670 Xeon
with 64 GB Ram.
I wil try
GO_TEST_TIMEOUT_SCALE=4
On Friday, 10 July 2020 14:24:54 UTC-4, Ian Lance Taylor wrote:
>
> On Fri, Jul 10, 2020 at 11:17 AM > wrote:
> >
> > I am attempting to build go v 1.14.4 from the git re
On Friday, 10 July 2020 14:24:54 UTC-4, Ian Lance Taylor wrote:
>
> On Fri, Jul 10, 2020 at 11:17 AM > wrote:
> >
> > I am attempting to build go v 1.14.4 from the git repo. I first built
> version 1.4 without issue and the build itself seems fine however many of
> the tests fail, see the at
On Fri, Jul 10, 2020 at 11:17 AM wrote:
>
> I am attempting to build go v 1.14.4 from the git repo. I first built
> version 1.4 without issue and the build itself seems fine however many of the
> tests fail, see the attached log.
>
> The OS is latest CentOS 7, and go-1.4 was built using gcc 8.3
