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

marl: init at 1.0.0 #106042

Merged
merged 1 commit into from Dec 6, 2020
Merged

marl: init at 1.0.0 #106042

merged 1 commit into from Dec 6, 2020

Conversation

breakds
Copy link
Contributor

@breakds breakds commented Dec 6, 2020

Motivation for this change

This pull request packages a modern fiber scheduler library for C++, called marl.
I have been using this package with nix-shell for a few projects which verifies that the package works as expected.

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.

@RaghavSood
Copy link
Member

Result of nixpkgs-review pr 106042 run on x86_64-linux 1

1 package built:
  • marl

@breakds
Copy link
Contributor Author

breakds commented Dec 6, 2020

Result of nixpkgs-review pr 106042 run on x86_64-linux 1

1 package built:

Does this suggest any issue found in nixpkgs-review? I ran the command locally and didn't see issues.

@RaghavSood
Copy link
Member

RaghavSood commented Dec 6, 2020

Does this suggest any issue found in nixpkgs-review? I ran the command locally and didn't see issues.

Nope, this just means that the review tool was able to build the package successfully

nixpkgs-review is more useful when testing existing packages that are used by other packages in the tree and helping make sure they still compile - since this is a new addition, we only get a single built package, which can then be inspected (via the result symlink)

In this case, I used it to just easily pull your changes, apply them to the master branch, build the package, and then check that the include and lib folders contain the expected header and cmake files.

The command in the issue template (nix-shell -p nixpkgs-review --run "nixpkgs-review wip") only works with WIP changes - once you have opened the PR, you can use nixpkgs-review pr 106042 to build the package and any downstream packages locally, and add nixpkgs-review pr --post-result 106042 if you want to build and automatically post the results as a comment (requires a github token configured)

@RaghavSood RaghavSood merged commit 6dfa0d8 into NixOS:master Dec 6, 2020
@breakds
Copy link
Contributor Author

breakds commented Dec 6, 2020

Does this suggest any issue found in nixpkgs-review? I ran the command locally and didn't see issues.

Nope, this just means that the review tool was able to build the package successfully

nixpkgs-review is more useful when testing existing packages that are used by other packages in the tree and helping make sure they still compile - since this is a new addition, we only get a single built package, which can then be inspected (via the result symlink)

In this case, I used it to just easily pull your changes, apply them to the master branch, build the package, and then check that the include and lib folders contain the expected header and cmake files.

The command in the issue template (nix-shell -p nixpkgs-review --run "nixpkgs-review wip") only works with WIP changes - once you have opened the PR, you can use nixpkgs-review pr 106042 to build the package and any downstream packages locally, and add nixpkgs-review pr --post-result 106042 if you want to build and automatically post the results as a comment (requires a github token configured)

Thanks a lot for the detailed explanation and prompt answer. I'll take a note and add such a comment explaining what have been built next time.

Appreciate the help!

@breakds breakds deleted the marl branch December 6, 2020 06:30
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

2 participants