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

Use unlimited virtual memory when running msolve tests (autotools) #3436

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

d-torrance
Copy link
Member

Most of the tests fail using the default 400000 kB.

Closes: #3428

Here's a successful run of the tests after this change: https://github.com/d-torrance/M2/actions/runs/10552691192/job/29231880174

Most of the tests fail using the default 400000 kB.

Closes: Macaulay2#3428

[ci skip]
@d-torrance d-torrance requested a review from mahrud August 26, 2024 02:53
@mahrud
Copy link
Member

mahrud commented Aug 26, 2024

Perhaps you could request one of the authors to review? (In particular, I don't use the autotools build, and I'd rather not have to deal with it just to review this PR. If you're sure that it's correct then feel free to merge.)

@d-torrance d-torrance merged commit 3c22f56 into Macaulay2:development Aug 26, 2024
@mikestillman
Copy link
Member

We have the limit in for a reason, so that tests (mostly) don't need to be run on large memory machines. How much memory is the msolve executable taking?

@d-torrance
Copy link
Member Author

Ok, that makes sense. I'll do some experiments and find a finite upper bound.

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.

3 participants