Closed gap-package-distribution-bot[bot] closed 7 months ago
GAP tests are broken by this, but only because this includes a fix for a prior issue.
But now I figure out a way how to deal with this, hmm. Maybe first turn of testing against GAP 4.12.2 (there won't be a new 4.12 release at this point, so these tests are not very helpful anyway). Then ... adjust GAP master to work with the new GAPDoc, and then quickly afterwards merge this PR? ... Or perhaps disable the failing test on GAP master; then merge this; then re-enable a fixed version...
master
Testing: master/2024-02-26-21:41:02-b1d25088 vs master/2024-02-26-21:14:28-5e6683e8
Generated by Workflow: https://github.com/gap-system/PackageDistro/actions/runs/8055616116
In total, 158 packages were tested, out of which 153 succeeded, 1 failed and 4 were skipped.
1 package(s) failed tests also on the previous version.
153 package(s) succeeded tests also on the previous version.
4 package(s) skipped tests also on the previous version.
PackageInfo.g
] [README
] [website] [source archive]