New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go_1_10: init at 1.10 and set as default #35330
Conversation
Changes are minor from 1.9, so let's just set it as default straight.
@GrahamcOfBorg build docker direnv |
heading: "API check", | ||
fn: func(dt *distTest) error { | ||
if t.compileOnly { | ||
-return nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh looks like gofmt
has added this. I will remove it after borg's first trial.
Failure on x86_64-darwin (full log) Partial log (click to expand)
|
@Mic92 Don't you think we should also update |
@adisbladis Yes. I forgot about that. |
Success on aarch64-linux (full log) Partial log (click to expand)
|
Failure on x86_64-darwin (full log) Partial log (click to expand)
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
Fyi there is another open PR that does this #35311 |
@adisbladis oh, I have not checked for it. |
Success on aarch64-linux (full log) Partial log (click to expand)
|
@GrahamcOfBorg build go |
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
Success on x86_64-darwin (full log) Partial log (click to expand)
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on x86_64-darwin (full log) Partial log (click to expand)
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
@@ -179,7 +179,7 @@ stdenv.mkDerivation rec { | |||
homepage = http://golang.org/; | |||
description = "The Go Programming language"; | |||
license = licenses.bsd3; | |||
maintainers = with maintainers; [ cstrahan orivej wkennington ]; | |||
maintainers = with maintainers; [ cstrahan orivej velovix mic92 ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@velovix are you ok with that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, that's fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know that wkennington isn't interested in being a maintainer anymore?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@velovix he has his own fork of nixpkgs, he is working: https://triton.github.io/triton/
@GrahamcOfBorg build docker |
Success on aarch64-linux (full log) Partial log (click to expand)
|
Success on x86_64-darwin (full log) Partial log (click to expand)
|
Success on x86_64-darwin (full log) Partial log (click to expand)
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on x86_64-darwin (full log) Partial log (click to expand)
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
Success on x86_64-linux (full log) Partial log (click to expand)
|
Success on aarch64-linux (full log) Partial log (click to expand)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
we should probably only keep up to 3 concurrent releases of compilers |
@zimbatm We just dropped 1.6 and 1.7 earlier today (#35327) so once this is merged we have 1.8, 1.9 and 1.10 (+bootstrap). I would like to drop 1.8 before the 18.03 release too (only the 2 latest releases are supported by upstream) but dropping 1.8 is currently blocked by |
Hi, I noticed that Go 1.10 has a new "build caching" mechanism, briefly described at In Guix, I found that the new Go cache validator was not choosing to re-use built Go objects but instead rebuilt all the dependencies from scratch during each package build. |
@lfam It seems that Go 1.10 puts cached build output in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
@lfam there is a NixCon talk about incremental compilation https://www.youtube.com/watch?v=AED-dgCa9GU&index=8&list=PLgknCdxP89ReQzhfKwMYjLdwWsc7us8ns |
@velovix Interesting, I wouldn't expect that to work in the package build environment, although I really don't have strong knowledge of Nix compared to Guix. |
@lfam I may have misunderstood your question. Are you asking if nixpkgs can take advantage of Go's caching while building Go applications? |
@velovix Yes, that's what I'm wondering. We do it in Guix but it doesn't work anymore with Go 1.10 and I'm hoping to have a conversation with other people using Go with a functional package manager :) I know this is not the right forum for the discussion. Feel free to ping me on Freenode, user lfam. |
Changes are minor from 1.9, so let's just set it as default straight.
changelog: https://golang.org/doc/go1.10
Motivation for this change
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)