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.

Sign up for GitHub

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

Jump to bottom

[19.03] nauty: disable cpu feature detection #59014

Merged
merged 1 commit into from Apr 5, 2019
Merged

[19.03] nauty: disable cpu feature detection #59014

merged 1 commit into from Apr 5, 2019

Conversation

timokau
Copy link
Member

@timokau timokau commented Apr 5, 2019

Motivation for this change

Backport of #58961.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • 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 nix-review --run "nix-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)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@timokau
nauty: disable cpu feature detection
62ad2cc 
(cherry picked from commit 7f22a42)
@timokau timokau changed the title nauty: disable cpu feature detection [19.03] nauty: disable cpu feature detection Apr 5, 2019
@globin globin merged commit 833d593 into NixOS:release-19.03 Apr 5, 2019
@timokau timokau deleted the nauty-features-backport branch April 5, 2019 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@7c6f434c 7c6f434c Awaiting requested review from 7c6f434c

Assignees
No one assigned
Labels
10.rebuild-darwin: 0 10.rebuild-linux: 1-10
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@timokau @globin @GrahamcOfBorg