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

Juvix Compiler Fails building it's own stdlib tests #3154

Open
mariari opened this issue Nov 7, 2024 · 1 comment · May be fixed by #3215
Open

Juvix Compiler Fails building it's own stdlib tests #3154

mariari opened this issue Nov 7, 2024 · 1 comment · May be fixed by #3215
Assignees
Labels
Milestone

Comments

@mariari
Copy link
Member

mariari commented Nov 7, 2024

Describe the bug

[6 of 6] Compiling Test
juvix: Maybe.fromJust: Nothing
CallStack (from HasCallStack):
  error, called at libraries/base/Data/Maybe.hs:150:21 in base:Data.Maybe
  fromJust, called at src/Juvix/Compiler/Core/Data/Module.hs:71:30 in juvix-0.6.6-63HcRSLJPON7XBeV31D9oO:Juvix.Compiler.Core.Data.Module
make[1]: *** [Makefile:6: build/Test] 錯誤 1
make[1]: 離開目錄「/home/taichi/Documents/Work/Repo/anoma-repos/juvix-stdlib/test」
make: *** [Makefile:21: test] 錯誤 2

Desktop (please complete the following information):

  • OS: [e.g. iOS] Arch Linux & ubunut
  • Juvix Version [e.g. 22] Juvix version 0.6.6-0961d87

To Reproduce
Steps to reproduce the behavior:

  1. Go to: juvix-stdlib [0080b1183ab55e5180e69bfc3987e4cd6edbc230]
  2. run: make test
  3. See error

Also see https://github.com/anoma/juvix-stdlib/actions/runs/11717091275/job/32636224379

for CI failure

Expected behavior
Haskell not to freakout

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

@lukaszcz lukaszcz added this to the 0.6.9 milestone Nov 15, 2024
@lukaszcz
Copy link
Collaborator

lukaszcz commented Dec 1, 2024

This happens because of the following bug:

If you change the standard library, but do not change the version quickcheck, then quickcheck depends on a different version of the standard library. Having two versions of the standard library in the same project causes an internal compiler inconsistency, because the package ids are not set correctly.

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

Successfully merging a pull request may close this issue.

3 participants