check GLPK bound errors

[malb]

This should never happen:

sage: from sage.numerical.backends.generic_backend import get_solver
sage: p = get_solver(solver = "GLPK") 
sage: p.add_variable()
1
sage: p.variable_upper_bound(1)
sig_error() without sig_on()
...
------------------------------------------------------------------------
Unhandled SIGABRT: An abort() occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
------------------------------------------------------------------------
Aborted

Depends on #19525

CC: @mkoeppe @dimpase

Component: numerical

Author: Vincent Delecroix

Branch/Commit: 6503bc5

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/10232

[videlec]

comment:5

The method name changed

AttributeError: 'sage.numerical.backends.glpk_backend.GLPKBackend' object has no attribute 'variable_max'

But still (with #19525 applied)

sage: p.variable_upper_bound(1)
sig_error() without sig_on()
...
------------
Unhandled SIGABRT: An abort() occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
------------------------------------------------------------------------
Aborted

[videlec]

Dependencies: #19525

[videlec]

New commits:

6503bc5

Trac 10232: catch some errors in GLPK backend

[videlec]

Commit: 6503bc5

[videlec]

Author: Vincent Delecroix

[videlec]

Branch: u/vdelecroix/10232

[mkoeppe]

comment:10

I think the title of this ticket needs to be changed to be more specific.

[dimpase]

comment:12

I've never seen <double?> syntax. What does it do?

[videlec]

comment:13

Replying to @dimpase:

I've never seen <double?> syntax. What does it do?

It is a Cython cast with type checking: see the documentation.

[dimpase]

comment:14

OK

[videlec]

Reviewer: Dima Pasechnik

[vbraun]

Changed branch from u/vdelecroix/10232 to 6503bc5