Skip to content
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

buildGoModule: change doCheck default to true #94632

Merged
merged 3 commits into from Aug 10, 2020
Merged

buildGoModule: change doCheck default to true #94632

merged 3 commits into from Aug 10, 2020

Conversation

zowoq
Copy link
Contributor

@zowoq zowoq commented Aug 4, 2020

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@@ -13,6 +13,8 @@ buildGoModule rec {

vendorSha256 = "05vnysr5r3hbayss1pyifgp989kjw81h95iack8ady62k6ys5njl";

doCheck = false;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do you plan to enable them?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By checking them and making PRs but not all at once. I wanted this to be a no-rebuild PR so it's an easy merge.

I wanted to flip the default now while it isn't to much trouble and so it applies to buildGoPackage -> buildGoModule changes and new packages.

Copy link
Member

@Mic92 Mic92 Aug 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you checked what the success rate of checks for go packages in general is? I am asking because this will also affect out-of-tree packages.

Copy link
Contributor Author

@zowoq zowoq Aug 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently it's barely used and doesn't get mentioned during PR reviews.

Making this opt out (same as buildRustPackage) will be better long term.

I am asking because this will also affect out-of-tree packages.

Yeah, I think now is a good time to do this with vendorSha changes also affecting those packages.

@kalbasit
Copy link
Member

kalbasit commented Aug 9, 2020

@zowoq I think you got enough approvals. Please rebase and make sure no new Go packages were added that will be affected by this change and merge.

@zowoq zowoq merged commit b004e48 into NixOS:master Aug 10, 2020
@zowoq
Copy link
Contributor Author

zowoq commented Aug 10, 2020

There were seven additional packages using buildGoModule since I opened this PR, we will probably have a couple that passed ofborg prior to this but get merged after this change and end up broken. I'll keep checking for the next couple of weeks.

@zowoq zowoq deleted the gomodule-check branch August 10, 2020 06:53
@georgyo georgyo mentioned this pull request Aug 22, 2020
10 tasks
emilylange added a commit to emilylange/nixpkgs that referenced this pull request Apr 5, 2023
They run just fine.
Seems to be a leftover from NixOS#94632 (cea7cd9), which changed the default of `doCheck` from `false` to `true`
@antonmosich antonmosich mentioned this pull request Sep 28, 2023
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants