-
Notifications
You must be signed in to change notification settings - Fork 6
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
Tests fail in stable-4.10 and master GAP branches #43
Comments
This is caused by some changes in the stable-4.10 branch: in the Travis tests, with the same set of packages, it failed first time at https://travis-ci.org/gap-packages/gap-docker-pkg-tests-stable-4.10-devel/jobs/434965129 but passed at https://travis-ci.org/gap-packages/gap-docker-pkg-tests-stable-4.10-devel/jobs/434578488 a day before. The same likely happened in the master branch, but was not noticed earlier because tests there are known to massively fail due to the method reordering. I suspect Wedderga may have wrongly assuming something, now revealed by |
Ah, the same pattern in master branch of GAP: passed at https://travis-ci.org/gap-packages/gap-docker-pkg-tests-master-devel/jobs/434372146, fails now at https://travis-ci.org/gap-packages/gap-docker-pkg-tests-master-devel/jobs/435114569. So this is new test failure, it was not sitting there for a while already. |
The first of the problems traced and reported in gap-system/gap#2892. The second one may not happen each run:
what, as a call with assertion level 1 show, may be pointing to an earlier problem:
|
Tests now pass both in stable-4.10 and master. |
Jenkins build of gap-stable-test #162 (Sep 27, 2018 5:55:48 PM) passed, and the next day it failed. There was the only new package (Forms) picked up, and the failed test was based on revision gap-system/gap@c94a364 with the following new commits:
With no packages:
With all and with default packages:
With default packages:
The text was updated successfully, but these errors were encountered: