Opened 7 years ago
Closed 7 years ago
#16440 closed enhancement (fixed)
GAP 4.7.5
Reported by: | vbraun | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | sage-6.3 |
Component: | packages: standard | Keywords: | |
Cc: | dimpase, fbissey, ppurka | Merged in: | |
Authors: | Volker Braun | Reviewers: | Dima Pasechnik |
Report Upstream: | N/A | Work issues: | |
Branch: | 8026003 (Commits, GitHub, GitLab) | Commit: | 8026003db0cdb48773dce8d38ccf77e303ba4690 |
Dependencies: | Stopgaps: |
Description (last modified by )
- http://boxen.math.washington.edu/home/vbraun/upstream/libgap-4.7.5.tar.gz
- http://boxen.math.washington.edu/home/vbraun/upstream/gap-4.7.5.tar.bz2
- http://boxen.math.washington.edu/home/vbraun/upstream/gap_packages-4.7.5.tar.bz2
- http://boxen.math.washington.edu/home/vbraun/upstream/database_gap-4.7.5.tar.bz2
Change History (21)
comment:1 Changed 7 years ago by
- Component changed from PLEASE CHANGE to packages: standard
- Description modified (diff)
- Type changed from PLEASE CHANGE to enhancement
comment:2 Changed 7 years ago by
- Branch set to u/vbraun/gap_4_7_5
comment:3 Changed 7 years ago by
- Commit set to fbddb40d957e1a83357595abd431798a274655f7
- Description modified (diff)
comment:4 Changed 7 years ago by
- Status changed from new to needs_review
comment:5 Changed 7 years ago by
- Cc dimpase added
comment:6 Changed 7 years ago by
- Commit changed from fbddb40d957e1a83357595abd431798a274655f7 to 03ad42a4805da7a44fc29b2e890532b825e5a630
Branch pushed to git repo; I updated commit sha1. New commits:
03ad42a | Increase GAP pool
|
comment:7 Changed 7 years ago by
does "gap: cannot extend the workspace any more!" stuff really break the docbuild? I remember seeing on sage-develop statements to the contrary.
comment:8 Changed 7 years ago by
Well according to strace it does. Gap has some warnings and some hard errors for low memory, and this one is apparently a hard error. I looked at the source and it means that sbrk failed, so its not unsurprising.
comment:9 follow-up: ↓ 11 Changed 7 years ago by
Well, the whole idea of importing (=running) code just to build its documentation is a very bad idea anyway (though of course "powerful"), but that's a different story...
I'll give it a try, but I can't imagine I'm actually running out of (virtual) memory in my docbuild-broken upgraded installation.
comment:10 Changed 7 years ago by
You are not necessarily running out of virtual memory, sbrk can fail for other reasons.
comment:11 in reply to: ↑ 9 ; follow-up: ↓ 12 Changed 7 years ago by
Replying to leif:
I'll give it a try, but I can't imagine I'm actually running out of (virtual) memory in my docbuild-broken upgraded installation.
Great! That triggers the rebuild of all of Sage for no (real) reason!
Praise the "new workflow" which makes everything so much easier!
comment:12 in reply to: ↑ 11 ; follow-up: ↓ 13 Changed 7 years ago by
Replying to leif:
Replying to leif:
I'll give it a try, but I can't imagine I'm actually running out of (virtual) memory in my docbuild-broken upgraded installation.
Great! That triggers the rebuild of all of Sage for no (real) reason!
happens to me too...
Praise the "new workflow" which makes everything so much easier!
developing software of the future on the hardware of the past :-)
comment:13 in reply to: ↑ 12 Changed 7 years ago by
Replying to dimpase:
Replying to leif:
Replying to leif:
I'll give it a try, but I can't imagine I'm actually running out of (virtual) memory in my docbuild-broken upgraded installation.
Great! That triggers the rebuild of all of Sage for no (real) reason!
happens to me too...
At least it fixed the issue for me... (I didn't recall I had gap_packages
installed into the installation.)
(Although probably it was really the Maxima upgrade to 5.33 which fixed it, or one of the other 50 tickets that got pulled in by pulling the branch here... ;-) )
comment:14 Changed 7 years ago by
- Cc fbissey added
comment:15 Changed 7 years ago by
- Cc ppurka added
I am running tests with --optional=sage,database_gap,gap_packages
, and seeing few errors. E.g.
sage -t --long src/sage/combinat/sloane_functions.py ********************************************************************** File "src/sage/combinat/sloane_functions.py", line 372, in sage.combinat.sloane_functions.A000001._eval Failed example: sloane.A000001._eval(51) # optional - database_gap Expected nothing Got: 1 **********************************************************************
There are also errors in src/sage/coding/linear_code.py
related to guava
.
Are they for a separate ticket?
comment:16 Changed 7 years ago by
The guava failures are #14979
comment:17 Changed 7 years ago by
- Commit changed from 03ad42a4805da7a44fc29b2e890532b825e5a630 to 8026003db0cdb48773dce8d38ccf77e303ba4690
Branch pushed to git repo; I updated commit sha1. New commits:
8026003 | fix doctest failures except the guava one (see #14979)
|
comment:19 Changed 7 years ago by
the tarfiles are gone here!
In fact, http://boxen.math.washington.edu/home/
is almost empty now...
comment:20 Changed 7 years ago by
- Reviewers set to Dima Pasechnik
comment:21 Changed 7 years ago by
- Branch changed from u/vbraun/gap_4_7_5 to 8026003db0cdb48773dce8d38ccf77e303ba4690
- Resolution set to fixed
- Status changed from positive_review to closed
New commits:
update to gap 4.7.5
the osx 10.4 fix is now upstream
the sparc bugfix is now upstream