-
Notifications
You must be signed in to change notification settings - Fork 63
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
Deprecate lead, trail, lm, lt, lc, valence and coeffs. #805
Conversation
Codecov Report
@@ Coverage Diff @@
## master #805 +/- ##
==========================================
+ Coverage 81.05% 81.08% +0.02%
==========================================
Files 52 52
Lines 17797 17792 -5
==========================================
Hits 14426 14426
+ Misses 3371 3366 -5
Continue to review full report at Codecov.
|
The OscarCI tests are exiting with signal 11 with no stack trace. Any idea what that is about? |
Very weird, looking at the timestamps does not help either:
Let's restart. |
There's a lot of "unsatisfiable requirements" (dependencies) as well. I don't know if that caused it somehow. |
I have decided to do map_coeffs in a separate series of PR's if we decide to rename that. This is getting too messy otherwise. Thus, I will finish this off as soon as 801 is merged. |
#801 is merged. How do we want to move forward? We can merge all the breaking things (+ the to be created PR for map_coeff) today or beginning of next week and immediately tag a new release. |
On Fri, Mar 19, 2021 at 02:03:00AM -0700, thofma wrote:
#801 is merged.
How do we want to move forward? We can merge all the breaking things (+ the to be created PR for map_coeff) today or beginning of next week and immediately tag a new release.
I'd rather do this earlier than later. There will be more of the same I
am sure, but we canot wait and let the PRs get stale.
I can lend a hand if you tell me what to do (only one exam today)
… --
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#805 (comment)
|
Please do not merge anything else until I have reviewed it. The order of merging here is potentially going to create some massive headaches. I am on it now and will let you know when everything is ok to go. |
e7b10d7
to
d2a5d43
Compare
@thofma I believe this is right to go, independently of everything else. But I have not tested that the deprecations in AA are sufficient for Hecke/Oscar, etc. I'll test Nemo and Hecke now, and if so will call it good. Just give me 30 mins or so to run the tests. |
Current failure is just #788 |
Nemo is fine, lots of yellow warnings, which is what I wanted to see. But tests pass. Waiting for Hecke tests now. |
Hmm, the Hecke tests just seem to have hung without running a single test. 10 mins and counting. Does it do that sometimes? |
It seemed to be hung in deprecated.jl |
Weird. Let me also try it locally. |
Looks like the same problem on restart of the tests. It displays:
Then it just hangs. Any idea what is happening here? It seems like the deprecations don't work with Hecke. |
Here's the trace when I hit CTRL-C:
|
Yeah, I just saw it locally. There is a recursion:
I think we can merge as is. |
Maybe. I'm trying the Hecke tests with this, the Nemo and Hecke patches all dev'd (so there are no deprecations activated). Let me check that works first. |
The issue is likely that Hecke currently defines leading_coefficient to be lead. |
I removed the method in Hecke locally and I am now running the tests. |
Naturally my Hecke PR already removes this method that is causing the recursion. |
Remarkably Hecke passes without any issues with this, the Nemo and Hecke PRs that I made. I'm surprised about that, but you can't help good luck! |
Nemo also. We should buy a lottery ticket! So if you want to go ahead and review and merge this PR, you are welcome to. Then I will rebase my multivariates on it while you review and merge #806 |
Thanks. I haven't set my VS Code editor up correctly yet. So it still uses tabs equal to 4 spaces and uses actual tabs not spaces. I just didn't find time for that yet. Still so many other problems with my new laptop. :-( |
0bb17bd
to
d2a5d43
Compare
Are all the Oscar CI runs strictly necessary? It looks like there's still about 3 hours of CI before we get an answer on this one! Can't we cut the Oscar CI runs down to a bare minimum? |
At the moment the backlog is for the normal "Run tests", which are just the usual AA tests, see https://github.com/Nemocas/AbstractAlgebra.jl/actions. The problem is that it runs the tests on every commit, but does not cancel the old runs. Do you know if one can make it cancel the old runs with GitHub Actions @benlorenz? |
Oh boy, it created a lot of combinations to check. We have to tweak this a bit I think. |
Ja |
I can't tweak it right now. You have tested it locally. Should we just merge? |
I'd say so. I've only tested it as far as Nemo and Hecke. I can't test it further in any easy manner right now. In particular I do not guarantee that the patches against Singular and Oscar are correct. They should be carefully reviewed before merging them. |
Technically I didn't test against the changes you made that I merged. But if you are confident of no typos... |
They were just whitespace anyhow, assuming you didn't delete a comma by accident |
I think it is not currently as useful as it could be. For example, it might be useful to know if Singular#deprecate_coeffs, Nemo#deprecate_coeffs, AA#deprecate_coeffs passes, but not with Oscar#master,Hecke#master if there are also deprecate_coeffs PRs for those packages. Somehow I really want to know where in the chain things broke. |
Also I guess now that we are maintaining master against master it is not likely that master against releases is going to pass due to package manager things. |
Yeah, it should probably disable the other tests if it finds a branch in a downstream package. I don't know how easy this is. I will mention it to Benjamin. |
I have made PRs against all the other repos.