-
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
CTblLib: make sure that tests pass #1619
Comments
Also notified @ThomasBreuer by email. |
As @ThomasBreuer confirmed by email, these differences are harmless, so you may ignore them. |
My suggestion to @ThomasBreuer was to move tests which fail to another test files in
in |
I have found a setting (calling the test with TERM=xterm) which removes all Now in the stable-4.8 branch tests status is as follows:
and logs are at https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-staging/jobs/331189402 In the stable-4.9 branch tests status is as follows:
with logs available at https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-4.9-staging/jobs/327912057 |
I have noticed that CTbliLib tests have some more diffs when it is tested with the current GAP master branch - @ThomasBreuer please see the log at https://travis-ci.org/gap-system/gap-docker-pkg-tests-master-staging/jobs/415554743 (scroll till the end of the log file to see three log files and their explanation). For example, this one
does not occur in the tests under the stable-4.9 branch (e.g. https://travis-ci.org/gap-system/gap-docker-pkg-tests-stable-4.9-staging/jobs/415728861). |
@ThomasBreuer I have posted a comment about AtlasRep at #1617 - the same applies to CTblLib, of course. You can inspect the status of standard tests for CTblLib in GAP 4.10.0 release at https://travis-ci.org/gap-system/gap-docker-pkg-tests/jobs/453290388. |
@ThomasBreuer have you seen this issue? I have posted a new comment about AtlasRep in #1617, and want to remind about a similar problem here. The tests for CTblLib fail due to diffs, see e.g. most recent logs here:
for master and stable-4.10 branches respectively. They may be harmless, but that does not provide a relief - one can not rely on someone manually inspecting logs regularly to see if there are any new problems, and I do not feel comfortable that this is still the situation for some central packages in GAP. |
@ThomasBreuer the new release of CTblLib is picked up, and should appear in the next GAP release. The default test, specified in its
and it there will be any changes in GAP or in packages that will break CTblLib tests, we should be able to discover that easily. That's a good improvement for such a crucial package as CTblLib. I am looking forward for the ability to automatically detect test failures for AtlasRep too, as discussed in #1617. For now, AtlasRep are in "staging" test, where you can always check their status yourself - I hope you are keeping an eye on these: |
Below is the output of CTblLib tests with GAP 4.8.8 release candidate when GAP is loaded with default packages. It will be nice to clean up the diffs, which are of several kinds:
different formatting
different output (caused by SpinSym package?)
tests can be performed because of TERM = "dumb" (cf. Diffs in AtlasRep standard tests #1617)
In addition, it's not possible to detect whether tests passes or not automatically. There is an easy fix for that:
PackageInfo.g
specifies the testfiletst/testauto.g
, but that testfile only calls one testtst/docxpl.tst
. In this case, one could just specifytst/docxpl.tst
inPackageInfo.g
instead oftst/testauto.g
. Otherwise, for the compliance with automated failure detection one could follow #1617 or useTestDirectory
.The text was updated successfully, but these errors were encountered: