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
Listing meataxe matrices with zero rows is broken #26389
Comments
comment:2
Right. But I didn't see the failure from the doctest yet, even after I installed meataxe to my installation (on mac). Do you have a specific procedure likely to encounter the failure? |
comment:3
Replying to @kwankyu:
You may also have to run |
comment:4
Still no failure from
on mac, after |
Replying to @tscrim:
Question: Are you using a special branch? Or do you mean the test in When running the tests in This raises the question what kind of machine you are using. Anything special concerning endianness, size of long, I think I recall there can also be issues regarding whether char is signed or not? |
comment:6
Replying to @simon-king-jena:
No, I am running vanilla 8.4.beta7. It seems like you are running 8.4.beta6 or below (specifically, this was added in #25435).
I have seen this arise on multiple patchbots from multiple tickets (sardonis on 25477, sage4 on 12053, sage4 on 26400). I don't think I have anything special. I kinda recall there being a signed char issue, but I thought you had fixed that. |
comment:7
Replying to @kwankyu:
Maybe it is not something that shows up on macs (I am running Ubuntu 16.04 LTS). |
comment:8
Replying to @tscrim:
That would explain it: I got
OK, I'll try to see what I can do. EDIT: I'll use the current develop branch merged with the branch that introduces singular-4.1.1.p3. |
comment:9
After upgrading, I indeed get frequent errors with that test, namely twice the same test in the same file:
The error seems to indicate that the matrix contains items that do not belong to the underlying field. And that sounds pretty much like a memory corruption. I cannot dive into it at the moment (need to prepare a written exam to be held tomorrow), but at least I can confirm the problem. |
comment:10
The good thing is that it seems not to be caused by some obscure side-effect of other tests: I did
in three new Sage sessions. The first two times the test worked. The third time it failed. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:16
Please do not always change the ticket description. It makes me get a long mail (stating the old description but not the new one). Moreover it hides what you have actually changed (unless one clicks on the "diff" button). So please, when you dig further, write a comment. |
comment:17
Since its optional I don't really see this as a blocker; Though if a simple bugfix materializes really soon I'd consider merging it... |
Author: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
comment:20
Nice! So, the problem is just a corner case that was forgotten to be dealt with in my wrapper for SharedMeatAxe. That's a big relief. I thought it would be caused by a problem in SharedMeatAxe's memory management. |
New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:23
The mystery is why this bug suddenly shows up now. As far as I can tell (by looking at git history), this has been broken all the time since #12103. |
comment:25
Patchbot passed on sage4 which has |
Reviewer: Travis Scrimshaw |
comment:26
LGTM. Thank you Jeroen. |
Changed branch from u/jdemeyer/a_bug_likely_with_matrix_gfpn_dense_or_meataxe to |
comment:28
This should be re-targeted for 8.5. |
CC: @simon-king-jena
Component: interfaces: optional
Author: Jeroen Demeyer
Branch/Commit:
828b188
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/26389
The text was updated successfully, but these errors were encountered: