leanprover / leanprover/lean-eval
There's needs to be a way to submit with much higher memory limit
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 46
- Forks
- 39
- Avg merge
- 54m
- Merged PRs (30d)
- 80
Description
My submission for zhang_bounded_prime_gaps OOMs during submission:
https://github.com/leanprover/lean-eval-submissions/actions/runs/35150842192
https://github.com/leanprover/lean-eval-submissions/actions/runs/35158364131
While for this particular problem it might be possible to squeeze it into something that would pass on a 16GB machine, it is definitely the case that for a large fraction of yet unsolved problems it would not be possible. For example, FLT is in the v1, and I do not believe that any submission for FLT can possibly be replayed on a 16GB instance.
There needs to be a way to submit solutions that cannot be replayed on a 16GB machine.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked GitHub Actions runs and the submission replay workflow to understand where the 16GB limit is imposed. Define the supported path for submissions that need more memory, including how they are submitted and replayed. Done means a high-memory submission can be replayed reliably without the current memory limit blocking it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100