De: "Jakub Cajka"
>> 1. You have a summary of the successes and failures at the end of the log
>> files
>> 2. each failed build run of a package ends with 'Done processing $spec
>> (failure)'
> Ah... missed that, I have been just quickly scanning the log's first few 100
> lines. What tool are
- Original Message -
> From: "nicolas mailhot" <nicolas.mail...@laposte.net>
> To: golang@lists.fedoraproject.org
> Sent: Tuesday, January 16, 2018 11:16:44 AM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
>
>
> - Mail
- Mail original -
De: "Jakub Cajka" <jca...@redhat.com>
À: golang@lists.fedoraproject.org
Envoyé: Mardi 16 Janvier 2018 10:16:19
Objet: Re: F28 System Wide Change: Golang 1.10a
>>> De: "Jakub Cajka"
>> From: "nicolas mailhot"
>
- Original Message -
> From: "nicolas mailhot" <nicolas.mail...@laposte.net>
> To: golang@lists.fedoraproject.org
> Sent: Monday, January 15, 2018 6:16:07 PM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
>
>
> - Mail original -
- Mail original -
De: "Jakub Cajka"
> If you don't share how, why it fails we can be just speculating(maybe it is
> bug in your > packaging, build setup). I wouldn't assume google in name == it
> always works ;).
I sent you the logs by PM ("only" 5 MiB compressed with xz -9). Did
- Original Message -
> From: "nicolas mailhot" <nicolas.mail...@laposte.net>
> To: golang@lists.fedoraproject.org
> Sent: Monday, January 15, 2018 3:47:00 PM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
>
> >De: "Jakub C
>De: "Jakub Cajka"
>> From: "nicolas mailhot"
> I'm not generally blaming it on outdated packages(although there are some),
> I'm mostly blaming it > on code that is not following best coding
> practices(https://tip.golang.org/doc/go1.10#test) or
> assume some not guaranteed/universal
- Original Message -
> From: "nicolas mailhot" <nicolas.mail...@laposte.net>
> To: golang@lists.fedoraproject.org
> Sent: Monday, January 15, 2018 2:48:36 PM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
> De: "Jakub Cajka"
>
De: "Jakub Cajka"
> Have you investigated the build failures to have such strong claim?
I, obviously hadn't have the time to investigate each failure
However, given the builds ran in parallel on the same computer, pointing to the
same repositories (with the exception of Go 1.9 forcing in one
aproject.org>
> Sent: Monday, January 15, 2018 2:22:26 PM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
> Hi,
>
> So, to be more scientific, I did a complete rebuild from scratch of my Go
> spec stash in rawhide, both with Go 1.10 and forcing the previous Go 1.9.2
> (ab
Hi,
So, to be more scientific, I did a complete rebuild from scratch of my Go spec
stash in rawhide, both with Go 1.10 and forcing the previous Go 1.9.2 (about
300 packages, some of which are not supposed to build yet because I still need
to finish the unbundling and bootstraping of docker in
Hi Jakub
I'm not sure if the package exists in devel, of if we're unbundling it from
some other package, or if we're executing unit tests previously ignored
The core dump does not stop the package build
Will investigate some more…
Regards,
--
Nicolas Mailhot
rg>
> Sent: Friday, January 12, 2018 4:32:22 PM
> Subject: Re: F28 System Wide Change: Golang 1.10a
>
> Hi,
>
> With the new Go 1.10 I get
>
> + echo
> /usr/share/gocode/src/github.com/hashicorp/go-discover/cmd/discover/main.go
> + install -m 0755 -vd
> /builddi
Hi,
With the new Go 1.10 I get
+ echo
/usr/share/gocode/src/github.com/hashicorp/go-discover/cmd/discover/main.go
+ install -m 0755 -vd
/builddir/build/BUILDROOT/golang-github-hashicorp-discover-0-0.5.0.20180108git7642001.fc28.llt.x86_64/usr/bin
install: creating directory
14 matches
Mail list logo
