-
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
All kinds of errors in tst/testinstall/opers #970
Comments
I do not see any diffs or errors on my current master branch. Are you sure the method from #563 is in your I was the one who put these into testinstall in order to have better code coverage of Nevertheless, it probably should be moved to teststandard and testinstall could check some smaller examples with the particular method. |
I've checked that in the currently running nightly test of master branch with the set of packages from GAP 4.8.6 testinstall.g runs with zero diffs. It took 43s without packages and 75s with packages (and the slowdown is worrying). |
I'm at a loss here. I have now reset the branch to upstream/master and cherry-picked the changes on it again. It goes from my |
Just to add the remark that even creating a new branch off master causes the same problems (#972) |
I may be onto something, and it seems to be package-dependent. Investigation in progress. |
Nothing so far. What I've seen is
on our new slave with all packages loaded. But I can't reproduce this after several runs of |
@hulpke I have played around with your branch a little bit. I might be completely off here (in which case I am sorry), but to me the culprit seems to be the following:
Now, here |
@hungaborhorvath I'm just completely puzzled why the test did not complain about a subgroup lattice computation, but actually gives the subsequent command (which has nothing to do with subgroup lattice)? In any case -- thank you very much. |
@hulpke also, I can't see the problem with |
after merging the master branch, I get all kinds of errors in files in testinstall/opers, (and these also cause tests for #968 to fail).
For example (after an update to the master branch)
Why do these rather specific tests need to be part of testinstall (and not of teststandard)?
Why was this merged if there are still obvious errors arising?
The text was updated successfully, but these errors were encountered: