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

cseExpensive test failing #6237

Closed
erikd opened this issue Jun 25, 2024 · 1 comment · Fixed by #6448
Closed

cseExpensive test failing #6237

erikd opened this issue Jun 25, 2024 · 1 comment · Fixed by #6448

Comments

@erikd
Copy link
Contributor

erikd commented Jun 25, 2024

Summary

With both ghc-9.6 and ghc-9.10 this test is currectly failing with:

cseExpensive:                                                                        FAIL (5.54s)
      Test output was different from 'untyped-plutus-core/test/Transform/cseExpensive.uplc.golden'. It was:
      ((\cse_402 ->
          (\cse_403 ->
             (\cse_404 ->
                (\cse_405 ->
                   (\cse_406 ->
                      (\cse_407 ->
                         (\cse_408 ->
                            (\cse_409 ->
                               (\cse_410 ->
                                  (\cse_411 ->
                                     (\cse_412 ->
                                        (\cse_413 ->
                                           (\cse_414 ->
                                              (\cse_415 ->
                                                 (\cse_416 ->
                                                    (\cse_417 ->
                                                       (\cse_418 ->
                                                          (\cse_419 ->
                                                             (\cse_420 ->
                                                                (\cse_421 ->
                                                                   (\cse_422 ->
                                                                      (\cse_423 -><truncated>
      Use --accept or increase --size-cutoff to see full output.
      Use -p '/cseExpensive/' to rerun this test only.

At @effectfully 's suggestion, I will be commenting it out to get my PR merged.

map* tests also need to start using CSE again, this was turned off in #6249 and #6251.

Steps to reproduce the behavior

In the Plutus tree:

cabal build all
cabal test untyped-plutus-core-test

Since I am commenting out the invocation of this test, it may need to be uncommented first.

Actual Result

cseExpensive:                                                                        FAIL (5.54s)
      Test output was different from 'untyped-plutus-core/test/Transform/cseExpensive.uplc.golden'. It was:
      ((\cse_402 ->
          (\cse_403 ->
             (\cse_404 ->
                (\cse_405 ->
                   (\cse_406 ->
                      (\cse_407 ->
                         (\cse_408 ->
                            (\cse_409 ->
                               (\cse_410 ->
                                  (\cse_411 ->
                                     (\cse_412 ->
                                        (\cse_413 ->
                                           (\cse_414 ->
                                              (\cse_415 ->
                                                 (\cse_416 ->
                                                    (\cse_417 ->
                                                       (\cse_418 ->
                                                          (\cse_419 ->
                                                             (\cse_420 ->
                                                                (\cse_421 ->
                                                                   (\cse_422 ->
                                                                      (\cse_423 -><truncated>
      Use --accept or increase --size-cutoff to see full output.
      Use -p '/cseExpensive/' to rerun this test only.

Expected Result

Test should pass

Describe the approach you would take to fix this

No response

System info

OS: Linux (Debian Testing)
Git hash: 710645a (on my as yet unmerged branch)

@erikd
Copy link
Contributor Author

erikd commented Jun 25, 2024

After being merged to master the commit is 6357d23 .

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

Successfully merging a pull request may close this issue.

2 participants