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

Try using plutus-1.38 for plutus-preprocessor #4855

Closed
wants to merge 1 commit into from

Conversation

lehins
Copy link
Collaborator

@lehins lehins commented Jan 24, 2025

Description

This is a test PR. DO NOT MERGE yet

Checklist

  • Commits in meaningful sequence and with useful messages
  • Tests added or updated when needed
  • CHANGELOG.md files updated for packages with externally visible changes

    New section is never added with the code changes. (See RELEASING.md)
  • Versions updated in .cabal and CHANGELOG.md files when necessary, according to the
    versioning process.
  • Version bounds in .cabal files updated when necessary

    If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
  • Code formatted (use scripts/fourmolize.sh)
  • Cabal files formatted (use scripts/cabal-format.sh)
  • hie.yaml updated (use scripts/gen-hie.sh)
  • Self-reviewed the diff

@lehins lehins force-pushed the lehins/upgrade-to-plutus-1.38 branch from 0b909da to 627312f Compare January 30, 2025 01:39
@lehins
Copy link
Collaborator Author

lehins commented Jan 30, 2025

Surprisingly the issue we've experienced previously with OOM on CI due to plutus-tx-plugin-1.38 is not happening in this PR. However, considering that we had it happen before and it was really getting in a way of development, I'll postpone the update until the test scripts has been fixed to not use so much memory. @zliu41 kindly offered to create a PR that will change our examples to use a much better way of writing scripts that should reduce both the size of the test scripts, as well as amount of RAM it takes to compile them.

@lehins lehins closed this Jan 30, 2025
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

Successfully merging this pull request may close these issues.

1 participant