Macaulay2 / Macaulay2/M2

assertion failing in check(4, "NumericalImplicitization") with LAPACK 3.10.0

Open
#2,230 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

arm build issue
Dominant language
Macaulay2
Stars
435
Forks
297
Avg merge
4d 20h
Merged PRs (30d)
11

Description

Today, the continuous integration tests on the arm64 Debian package started failing (full logs here and here):

 -- capturing check(4, "NumericalImplicitization")                           -- capture failed; retrying ...
 -- running   check(4, "NumericalImplicitization")                          
 ulimit -c unlimited; ulimit -t 700; ulimit -m 850000; ulimit -s 8192; ulimit -n 512;  cd /tmp/M2-23113-0/2-rundir/; GC_MAXIMUM_HEAP_SIZE=400M "/usr/bin/M2-binary" -q --int --no-randomize --no-readline --silent --stop --print-width 77 -e 'needsPackage("NumericalImplicitization",Reload=>true,FileName=>"/usr/share/Macaulay2/NumericalImplicitization.m2")' <"/tmp/M2-23113-0/1.m2" >>"/tmp/M2-23113-0/1.tmp" 2>&1
/tmp/M2-23113-0/1.tmp:0:1: (output file) error: Macaulay2 exited with status code 1
/tmp/M2-23113-0/1.m2:0:1: (input file)
M2: *** Error 1
 -- 3.62783 seconds elapsed
 -- capturing check(5, "NumericalImplicitization")                           -- 2.09619 seconds elapsed
 -- capturing check(6, "NumericalImplicitization")                           -- 2.58701 seconds elapsed
 -- capturing check(7, "NumericalImplicitization")                           -- 15.7876 seconds elapsed
 -- skipping  check(8, "NumericalImplicitization")                           -- 0.000084171 seconds elapsed
 -- capturing check(9, "NumericalImplicitization")                           -- 0.606022 seconds elapsed
 -- capturing check(10, "NumericalImplicitization")                          -- 0.070274 seconds elapsed
 -- capturing check(11, "NumericalImplicitization")                          -- 0.759777 seconds elapsed
/usr/share/Macaulay2/NumericalImplicitization/tests.m2:59:1-67:1: error:
 -- Points found: 12
 -- Points found: 15
 -- Points found: 15
 -- Points found: 15
 -- Points found: 16
 -- Points found: 16
 -- Points found: 16
 -- Points found: 16
 -- Running trace test ...
 -- stdio:7:1:(3): error: assertion failed
 -- 
stdio:1:1:(3): error: test(s) #4 of package NumericalImplicitization failed.

 cd /tmp/M2-2347-0/235-rundir/; GC_MAXIMUM_HEAP_SIZE=400M "/usr/bin/M2-binary" -q --int --no-randomize --no-readline --silent --stop --print-width 77 <"/tmp/M2-2347-0/234.m2" >>"/tmp/M2-2347-0/234.tmp"
/tmp/M2-2347-0/234.tmp:0:1: (output file) error: Macaulay2 exited with status code 1
/tmp/M2-2347-0/234.m2:0:1: (input file)
M2: *** Error 1

Comparing this to my amd64 machine, it looks like it's supposed to find 18 points:

i1 : needsPackage "NumericalImplicitization";

i2 : setRandomSeed 0;

i3 : R = CC[x_0..x_3];

i4 : I = ideal(random(2,R),random(3,R));
-- warning: experimental computation over inexact field begun
--          results not reliable (one warning given per session)

o4 : Ideal of R

i5 : F = random(R^1,R^{3:-3});

             1       3
o5 : Matrix R  <--- R

i6 : numericalImageDegree(F,I)
Sampling point in source ...
Tracking monodromy loops ...
Points found: 2
Points found: 4
Points found: 7
Points found: 9
Points found: 13
Points found: 15
Points found: 15
Points found: 17
Points found: 18
Points found: 18
Points found: 18
Points found: 18
Running trace test ...

o6 = 18

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing check(4, "NumericalImplicitization") from NumericalImplicitization/tests.m2, especially the assertion reported at lines 59–67, on the arm64 Debian environment with LAPACK 3.10.0. Compare the failing run with the amd64 output and the linked CI logs, then determine why numericalImageDegree finds different points. Done means the package test passes reliably on the affected environment without weakening the assertion.

Written by the indexing model from the issue text.

Assessment

Domain
backend, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.