Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#41559 - [go] Performance regression with 1.3.1-1
Attached to Project:
Community Packages
Opened by H3g3m0n (H3g3m0n) - Thursday, 14 August 2014, 04:27 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 24 August 2014, 10:47 GMT
Opened by H3g3m0n (H3g3m0n) - Thursday, 14 August 2014, 04:27 GMT
Last edited by Alexander F. Rødseth (xyproto) - Sunday, 24 August 2014, 10:47 GMT
|
DetailsDescription:
With 1.3.1-1 'go build' takes quite a while to run (quite a few seconds) and I hear my CPU fans going nuts, with 1.3.0 it takes a few ms. This is quite painful since I use syntactic/vim-go for analysis every save. Downgrading to 1.3-1 fixed the issue. Don't know if this is upstream or a packaging issue. Additional info: * go-2:1.3-1-x86_64.pkg.tar.xz Steps to reproduce: go build |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Sunday, 24 August 2014, 10:47 GMT
Reason for closing: Upstream
Sunday, 24 August 2014, 10:47 GMT
Reason for closing: Upstream
Comment by Daniel Micay (thestinger) -
Thursday, 14 August 2014, 04:43 GMT
You should report this upstream, I highly doubt that it's a packaging issue.
Comment by Alexander F. Rødseth (xyproto) -
Sunday, 24 August 2014, 10:47 GMT
Nothing I can do about this. Please report upstream to the Go developers.