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
upgrade GAP to 4.11.1 or newer #31498
Comments
Changed keywords from none to upgrade, gap |
Commit: |
Author: Dima Pasechnik |
New commits:
|
Branch: u/dimpase/packages/gap4111 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
what remains is to fix this weird error - something is emitting that string of
but
|
comment:6
Replying to @dimpase:
Isn't that just the usual test failure output? It seems to me that the actual issue is the "..." wildcard on the first line - there is no newline before the "Status" line so it doesn't match. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
another test to fix:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:11
please review... |
comment:12
I won't lie, I am not quite ready for this in sage-on-gentoo. I have been under rather heavy stress so far this year and I am not doing as much as I want. |
comment:13
Tell me about it ;-) But I think we should have people bang away at this asap and not later in the release cycle. |
comment:14
Thanks! |
Reviewer: Volker Braun |
comment:16
There is a small merge conflict with #31489, and a failure
|
comment:18
these test_packages stuff is a mess. We have two different functions May we do it on another ticket? |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:20
I believe the test is fixed now. |
Dependencies: #31489 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:23
OK, now it depends on #31489 and should cleanly merge: the only change from #31489 is done in comment:22 |
comment:24
I have not merged the full branch of #31489 here, though. |
comment:26
rebased on 9.4.beta1 |
Changed dependencies from #31489 to none |
comment:28
Let's try to get this into the next beta. |
Changed reviewer from Volker Braun to Volker Braun, Travis Scrimshaw |
Changed branch from u/dimpase/packages/gap4111 to |
comment:30
I am a bit dumbfounded by this upgrade in a way. There are strange particulars to it in sage-on-gentoo. I cannot build the doc.
In sage-on-gentoo, I do separate gap packages and the source of error is more precisely ctbllib-1.3.1+ (I say + because there is a 1.3.2 now in its upstream and the result is the same with it). If I downgrade ctbllib to 1.2_p2 the documentation builds. The error message suggests to increase the memory limit. This is set somewhere in I am probably missing something but what? |
Changed commit from |
comment:31
Whats the output of GAP needs swap due to how they reserve the memory pool. |
comment:32
Replying to @vbraun:
568MB if I leave it to the default. With the changes for my last attempt, it should be 2001MB. But what puzzles me is the influence of |
upgrades our corresponding spkgs: * gap * gap_packages * libsemigroups * Previous upgrades: - #31498: GAP 4.11.1 - #29314: GAP 4.11, libsemigroup 1.0.9 * Upstream: Completely fixed; Fix reported upstream Closes #34391 URL: #35093 Reported by: Dima Pasechnik Reviewer(s): Gonzalo Tornaría, Matthias Köppe
the current GAP release is 4.11.1. Time to upgrade - previous upgrade
was in #29314.
Here we also upgrade libsemigroups, in lockstep with GAP, to 1.1.0.
GAP tarball is now hosted on GitHub; we also need to install more GAP packages to satsify needs of updated GAP package digraph and semigroups.
Finally, we fix a bug in TestSuite for abelian groups
CC: @antonio-rojas @embray @kiwifb @mkoeppe @slel @tobihan @videlec
Component: packages: standard
Keywords: upgrade, gap
Author: Dima Pasechnik
Branch:
82f3fa7
Reviewer: Volker Braun, Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/31498
The text was updated successfully, but these errors were encountered: