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

Please, pass own test suite inside the Nixpkgs #618

Open
Anton-Latukha opened this issue Jun 5, 2020 · 4 comments
Open

Please, pass own test suite inside the Nixpkgs #618

Anton-Latukha opened this issue Jun 5, 2020 · 4 comments

Comments

@Anton-Latukha
Copy link
Collaborator

Anton-Latukha commented Jun 5, 2020

In Nixpkgs hnix currently still needs dontCheck.

When it passes test suite - rm dontCheck in hnix there in Nixpkgs.

@Anton-Latukha Anton-Latukha mentioned this issue Jun 15, 2020
3 tasks
@sjakobi
Copy link
Member

sjakobi commented Jul 8, 2020

For reference: https://github.com/NixOS/nixpkgs/blob/1ceecdd109d0c30fd48fc6af295d9c8b05d6c6c6/pkgs/development/haskell-modules/configuration-common.nix#L205-L210.

  # 2020-06-05: HACK: does not passes own build suite - `dontCheck` We should
  # generate optparse-applicative completions for the hnix executable.  Sadly
  # building of the executable has been disabled for ghc < 8.10 in hnix.
  # Generating the completions should be activated again, once we default to
  # ghc 8.10.
  hnix = dontCheck super.hnix;

Does "build suite" refer to nix build BTW?

@Anton-Latukha
Copy link
Collaborator Author

Anton-Latukha commented Jul 9, 2020

Oh, I meant test suite. I put that message before, like a month ago (2020-06-05).

Well, after 0.9.0 maralorn and I made PRs in parallel, and I saw that his solution is more detailed.

He addressed the GHC 8.10 set in Nixpkgs, so HNix does build with executable and completions for GHC > 8.10 in Nixpkgs distribution.

But I overlooked - he attached his message to the end of mine previous message - and now the overall message is a mess.

The test suite of course passes in our default.nix.
And I remember that there is Nixpkgs problem but already forgot why dontCheck not passing right in Nixpkgs there

Inside Nixpkgs HNix is imported not from our default.nix here, but from Hackage and put directly inside Nixpkgs and that allows test Hydra CI build and run test suite inside it that environment. Basically our configuration and dependencies of our HNix default.nix derivation different to the HNix derivation inside Haskell-Nixpkgs infrastructure, and that is where the detail is.

@Anton-Latukha
Copy link
Collaborator Author

Anton-Latukha commented Jul 9, 2020

After every release, I go and during my civil duty batch Haskell packages clean-up work I test and sneak-in a proper HNix overrides into Nixpkgs, so that HNix always works there. I to that degree keep our name from popping in Nixpkgs repo, community and in the community talk - to a beyond radar minimum.

@layus
Copy link
Collaborator

layus commented Jun 14, 2021

@expipiplus1 Still pending on #903 to remove network access in the way we use the store. Then I guess it is just a matter of finding the few remaining tests that still use the network (there should be none) and the problem would be solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants