Update Singular.jl to 0.28#5578
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5578 +/- ##
==========================================
+ Coverage 84.03% 84.28% +0.24%
==========================================
Files 738 746 +8
Lines 99958 103351 +3393
==========================================
+ Hits 83999 87107 +3108
- Misses 15959 16244 +285 🚀 New features to boost your workflow:
|
|
Folks, the "1.10, short, macOS, RPTU" run has been re-run for the 5th time. I don't think we'll see a different outcome. It always exceeds the 60 minutes run time limit. Even if by some miracle it finished in 55 minutes or whatever: on master this job takes less than 20 minutes. So something is definitely very wrong. |
|
I downloaded and filtered the log by worker, five of these excerpts end with The canceled message appears about 50 minutes later: Edit: I am re-running this again once more to look at the processes directly on the runner. |
|
After |
|
I can reproduce that on munk, julia 1.12, commit 5383878, from this branch here. Just running: There are two subprocesses (forks?) started when this testset is run: They are just waiting without any CPU load. I observed the same on the CI runner (two subprocesses below one of the workers) and tried to send unfortunately no further backtrace. All the other worker were finished with their jobs and in waiting in Attaching a debugger to the stuck process on munk give a backtrace deep inside libsingular with Interestingly once I detached the debugger the tests continued: (They were stuck for the whole night) Edit: And the one below that one: |
|
@hannes14 any ideas? |
|
no, that is about reading/writing ssi represented data to/from strings, which is currently only used from ssi.lib. |
Co-authored-by: Max Horn <max@quendi.de>
No description provided.