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

zig: 0.6.0 -> 0.7.1 #105086

Closed
wants to merge 1 commit into from
Closed

zig: 0.6.0 -> 0.7.1 #105086

wants to merge 1 commit into from

Conversation

jshholland
Copy link
Contributor

Currently, the test suite fails with the following output: build.log

I'm not sure how to debug this; I was going to start by doing a binary search on the test suite since I split them out in commit
4a1fbd9 but I haven't got to this yet.

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.

@berbiche
Copy link
Member

Looking forward to this.
https://github.com/ifreund/river will finally run on Nix!

@andrewrk
Copy link
Member

Currently, the test suite fails with the following output: build.log

I think you have hit a legitimate bug that is fixed in the 0.7.x branch. Hopefully 0.7.1 should be released in a week or two. But I personally don't think you need to get the zig test suite passing to package up the release (although I understand if that is policy).

'';

checkPhase = ''
runHook preCheck
./zig test $src/test/stage1/behavior.zig
./zig build -Dskip-non-native \
Copy link
Member

Choose a reason for hiding this comment

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

why not ./zig build test -Dskip-non-native ? It runs all the tests below.

also you can speed things up considerably if you are willing to skip release tests: -Dskip-release

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was still a WIP PR; I split the tests up line-by-line because I was planning to disable them to track down which one was failing, and I needed to transfer them from one computer to another. I'm not sure on the general NixOS policy on skipping release tests, hence I left them in. IMO it's probably worth running them because binary caches exist and it feels safer.

@jshholland
Copy link
Contributor Author

At this point I think given there are only 5 more issues in the Zig 0.7.1 milestone, and seeing that the test failure is due to a bug that's been fixed in master, I'll take another look when 0.7.1 is out.

@jshholland
Copy link
Contributor Author

0.7.1 has now been released, and I have managed to successfully build with the current changes. Ready for review and merge from my end here now.

@jshholland jshholland marked this pull request as ready for review December 13, 2020 22:16
@jshholland jshholland changed the title zig: 0.6.0 -> 0.7.0 zig: 0.6.0 -> 0.7.1 Dec 13, 2020
@ofborg ofborg bot requested a review from andrewrk December 13, 2020 22:27
@thiagokokada
Copy link
Contributor

@jshholland Can you fix the merge conflict?

@jshholland
Copy link
Contributor Author

Looks like the merge conflict is because @miikka already updated the Zig package in 5b95e93, so I suppose this PR can be closed now.

@jshholland jshholland closed this Dec 30, 2020
@jshholland jshholland deleted the update-zig branch July 29, 2022 10:17
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

4 participants