-
Notifications
You must be signed in to change notification settings - Fork 161
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
Diffs in AtlasRep standard tests #1617
Comments
Also notified @ThomasBreuer by email. |
I have found a setting (calling the test with TERM=xterm) which removes all Now in the stable-4.8 branch AtlasRep tests pass (https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-staging/jobs/331189400) but that can not be detected automatically because of the reasons explained above. In the stable-4.9 branch tests status is as follows:
with diffs being
Full logs can be viewed at https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-4.9-staging/jobs/327912054 P.S. @ThomasBreuer reported the regression with |
The
which should not depend on loaded packages. |
Of course not, we all should know that The example is part of the tutorial, and the point is to express that the group has the claimed structure. |
I see... Then perhaps the |
@ThomasBreuer AtlasReps tests still do not pass in the stable-4.10 branch, see for example the test log at https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-4.10-staging/jobs/438054207. For packages whose tests do not pass cleanly it's very easy to overlook when they become broken because of changes in GAP and/or other packages. Therefore, it will be very useful if AtlasRep tests can be fixed. First, even the following small changes in
Second, there is currently a diff when GAP is started with
It was discussed in #2109, and a "nice" option has been suggested there - is it suitable? Note that now they are supposed to pass for 87 packages at https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-4.10 and fail for 12 at https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-4.10-staging, so the coming GAP 4.10 will have package tests in the state like never before. But there is still a space to reduce the latter number even further down to 10 or less in GAP 4.10. |
@ThomasBreuer we have published GAP 4.10.0. Unfortunately, no new AtlasRep release appeared, so as you can see at https://travis-ci.org/gap-system/gap-docker-pkg-tests, it is one of the 6 packages (out of 103) for which we can not report that their tests pass. Furthermore, among those 6 packages there are two which are loaded by default (AtlasRep and CTbliLib) and it's quite unlucky that we do not check that they work as expected as thoroughly as for many other packages. Therefore, are you happy with the |
@ThomasBreuer the problem with Unfortunately, there is still no way now to detect whether tests pass or fail automatically for the package tests on Travis, so I am keeping AtlasRep in the "staging" tests:
Hence I am asking you to keep an eye on them and check that changes in GAP master and stable-4.10 branches do not break the test. If you would like to be notified when tests fail, rather than watch those tests yourself, there is a suggestion which I am reiterating: use
|
@alex-konovalov Concerning AtlasRep, I had already discussed with @fingolfin that I will provide a file in the abovementioned format (or a newer one if that is outdated by then) with the next released version of the package. (Besides that, |
@ThomasBreuer thanks - when you will be releasing AtlasRep update, please also note that it has the following warnings when it is loaded with
Perhaps TomLib and CTblLib should be made needed packages. |
@ThomasBreuer also AtlasRep uses obsolete
|
I wonder what the status of this is now... @ThomasBreuer perhaps we can briefly talk about this tomorrow? or next week, it's not urgent |
@fingolfin Yes, we can. Concerning the status with AtlasRep, the latest released version is 2.1.2, and the abovementioned problems should have disappeared in this version. (For the release of GAP 4.12.0 or 4.12.1, it will make sense to release AtlasRep 2.1.3, due to the changed address of the data server, and due to the new |
AtlasRep 2.1.1 is passing all test in the PackageDistro, see https://github.com/gap-system/PackageDistro/blob/data/reports/master/2022-07-01-03:21:56-6b7f6a77/report.md -- so this can be closed. Thanks @ThomasBreuer ! As to making 2.1.3 which requires GAP 4.12.0: that's no problem; I'd recommend to release it in early August, then we can merge it together with matrgrp and the new semigroups version around that time and include it with 4.12.0 |
The log below comes from Jenkins CI. It happens that AtlasRep's
tst/testall.g
file contains some tests that does not work when TERM = "dumb", the setting used in Jenkins CI.Those tests pass fine when
tst/testall.g
is read into a usual GAP session, and do not take much time. They automatically open and close some Browse package windows, and I understand that the developers of AtlasRep would like to keep them intst/testall.g
to run regularly. Therefore, it seems for me that the best solution would be to omit them if TERM = "dumb" and run otherwise.Additionally,
tst/testall.g
callsTest
, but does not analyse its returned value. This does not permit automated detection of test failures. As said in https://github.com/gap-system/gap/wiki/Status-of-standard-tests-in-GAP-packages, the automated detection of the result of the test is relying on lines containing the substringsor
(with exactly two spaces after
#I
), dependently on the test result. All that is needs is to calculatetestresult
and add the following linesto the end of the test.
The mentioned log file is below.
The text was updated successfully, but these errors were encountered: