-
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
Errors in testextra/grpperm.tst
in master branch
#3464
Milestone
Comments
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 20, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
changed the title
Errors in
Errors in May 20, 2019
estextra/grpperm.tst
in master branchtestextra/grpperm.tst
in master branch
I have added changes to #3451 (which also impacts some of the output) that resolve these (all harmless, even the assertion) problems. |
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 20, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 21, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 22, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 24, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 27, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 28, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
hulpke
added a commit
to hulpke/gap
that referenced
this issue
May 29, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves gap-system#3464
fingolfin
pushed a commit
that referenced
this issue
Jun 4, 2019
Test for running, n ot concrete output. Also change one assertion level higher so that it is not triggered by the (arbitrarily chosen level of) the automatic tests. (This is safer than ad-hoc quickly changing complicated but stable code.) This is a "be nice" assertion (that was never intended for automated tests), not a must have. This resolves #3464
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See e.g. this St Andrews-only link:
In these three diffs we have:
The text was updated successfully, but these errors were encountered: