Support #944
Release: CoCoALib-0.99550 (together with CoCoA-5.2.0)
Description
Everything related to making a CoCoALib release:
- Redmine Roadmap: close or postpone issue
- Redmine Release issues: check percentages, check timings
- Finalize
- make veryclean; make (full make, with all tests and examples and CoCoA-5..)
- tests: make valgrind
- CoCoA-5: make ManExamples
- create snapshot
- upload examples
- upload manual
- update webpage
- publish manual (arXiv? ResearchGate?)
- close release on Redmine
--> send message to facebook page
Related issues
History
#1 Updated by Anna Maria Bigatti over 7 years ago
- Copied from Support #754: Release: CoCoALib-0.99538 (together with CoCoA-5.1.2) added
#2 Updated by John Abbott over 7 years ago
Add also to check whether the CoCoA-5 tests pass with BackwardCompatible.cpkg5
#4 Updated by Anna Maria Bigatti over 7 years ago
- Subject changed from Release: CoCoALib-0.99544 (together with CoCoA-5.1.4) to Release: CoCoALib-0.99544 (together with CoCoA-5.1.6)
#5 Updated by Anna Maria Bigatti over 7 years ago
John Abbott wrote:
Add also to check whether the CoCoA-5 tests pass with
BackwardCompatible.cpkg5
OK, moved it to #850
#6 Updated by Anna Maria Bigatti over 7 years ago
- Status changed from Closed to In Progress
#7 Updated by Anna Maria Bigatti over 7 years ago
- Target version set to CoCoALib-0.99550 spring 2017
#8 Updated by Anna Maria Bigatti over 7 years ago
- Related to Support #851: Release: CoCoA-5.2.0 added
#10 Updated by Anna Maria Bigatti over 7 years ago
First run of valgrind (I had to reinstall valgrind on my mac...)
--test-BigInt3 ==87351== definitely lost: 16 bytes in 1 blocks --test-bug5 ==87397== definitely lost: 16 bytes in 1 blocks --test-bug7 ==87405== definitely lost: 20,496 bytes in 513 blocks --test-DenseUPolyRing1 ==87413== definitely lost: 16 bytes in 1 blocks --test-IsInteger1 ==87489== definitely lost: 880 bytes in 33 blocks --test-MachineInt1 ==87493== definitely lost: 16 bytes in 1 blocks --test-NumTheory1 ==87558== definitely lost: 16 bytes in 1 blocks --test-OrderedDomain2 ==87592== definitely lost: 1,128,528 bytes in 24,893 blocks --test-RandomSource2 ==87636== definitely lost: 16 bytes in 1 blocks --test-RandomSource3 ==87643== definitely lost: 16 bytes in 1 blocks --test-RingElem2 ==87663== definitely lost: 16 bytes in 1 blocks --test-RingElem4 ==87671== definitely lost: 16 bytes in 1 blocks --test-RingElem5 ==87695== definitely lost: 16 bytes in 1 blocks --test-RingHom1 ==87710== definitely lost: 16 bytes in 1 blocks --test-RingTwinFloat4 ==87743== definitely lost: 16 bytes in 1 blocks --test-RingTwinFloat5 ==87748== definitely lost: 16 bytes in 1 blocks --test-RingZmodN1 ==87760== definitely lost: 16 bytes in 1 blocks --test-symbol1 ==87799== definitely lost: 16 bytes in 1 blocks --test-utils1 ==87831== definitely lost: 16 bytes in 1 blocks
#11 Updated by Anna Maria Bigatti over 7 years ago
- Related to Feature #298: Valgrind: keep CoCoALib at 0 memory leaks added
#12 Updated by Anna Maria Bigatti over 7 years ago
Anna Maria Bigatti wrote:
First run of valgrind (I had to reinstall valgrind on my mac...)
[...]
The "16-byte leak" seems related to throwing/catching errors: is independent of the number of throws/catches and number of error values.
Now I investigate the others.
#13 Updated by John Abbott over 7 years ago
I'll do test-OrderedRing2
.... there is a leak in twinfloat.
I know where it is; now I just have to find a nice way of avoiding it.
#14 Updated by Anna Maria Bigatti over 7 years ago
- % Done changed from 0 to 30
Thanks John! Now we have only the "16bytes"
--test-BigInt3 ==90655== definitely lost: 16 bytes in 1 blocks --test-bug5 ==90709== definitely lost: 16 bytes in 1 blocks --test-bug7 ==90717== definitely lost: 16 bytes in 1 blocks --test-DenseUPolyRing1 ==90725== definitely lost: 16 bytes in 1 blocks --test-IsInteger1 ==90801== definitely lost: 16 bytes in 1 blocks --test-MachineInt1 ==90805== definitely lost: 16 bytes in 1 blocks --test-NumTheory1 ==90863== definitely lost: 16 bytes in 1 blocks --test-OrderedDomain2 ==90899== definitely lost: 16 bytes in 1 blocks --test-RandomSource2 ==90939== definitely lost: 16 bytes in 1 blocks --test-RandomSource3 ==90945== definitely lost: 16 bytes in 1 blocks --test-RingElem2 ==90967== definitely lost: 16 bytes in 1 blocks --test-RingElem4 ==90975== definitely lost: 16 bytes in 1 blocks --test-RingElem5 ==90982== definitely lost: 16 bytes in 1 blocks --test-RingHom1 ==91016== definitely lost: 16 bytes in 1 blocks --test-RingTwinFloat4 ==91044== definitely lost: 16 bytes in 1 blocks --test-RingTwinFloat5 ==91048== definitely lost: 16 bytes in 1 blocks --test-RingZmodN1 ==91060== definitely lost: 16 bytes in 1 blocks --test-symbol1 ==91092== definitely lost: 16 bytes in 1 blocks --test-utils1 ==91128== definitely lost: 16 bytes in 1 blocks
#15 Updated by Anna Maria Bigatti about 7 years ago
- Subject changed from Release: CoCoALib-0.99544 (together with CoCoA-5.1.6) to Release: CoCoALib-0.99550 (together with CoCoA-5.1.6)
#16 Updated by John Abbott about 7 years ago
- % Done changed from 30 to 40
I am hoping this can be completed very soon (within a week?).
I have just run make valgrind
in src/tests/
and all programs were clean :-)
[the reports for test-hilbert1
and test-GFan1
were slightly odd: "0 bytes leaked"]
ADDENDUM also make valgrind
for the examples says all programs are clean :-)
Just remember that the corresponding CoCoA-5 version is 5.2.0 (not 5.1.6 as in the title!)
#17 Updated by Anna Maria Bigatti almost 7 years ago
- Subject changed from Release: CoCoALib-0.99550 (together with CoCoA-5.1.6) to Release: CoCoALib-0.99550 (together with CoCoA-5.2.0)
- Description updated (diff)
- % Done changed from 40 to 50
#18 Updated by Anna Maria Bigatti almost 7 years ago
- Description updated (diff)
#19 Updated by Anna Maria Bigatti almost 7 years ago
- Description updated (diff)
#20 Updated by Anna Maria Bigatti almost 7 years ago
- Copied to Support #1056: Release: CoCoALib-0.99560 (together with CoCoA-5.2.2) added
#21 Updated by Anna Maria Bigatti almost 7 years ago
uploaded release, manual and examples
#23 Updated by Anna Maria Bigatti almost 7 years ago
published manual on ResearchGate
#24 Updated by Anna Maria Bigatti almost 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 90 to 100
- Estimated time changed from 4.00 h to 5.11 h