Source: ortools Version: 8.2+ds-6 Severity: important X-Debbugs-Cc: sm...@smurf.noris.de
ORtools needs to be built with optimization enabled. Otherwise it will (a) be slow and (b) crash when the model cannot be solved for whatever reason. Both are pretty bad for production code – as is spewing stderr with warnings which the user cannot do anything about. $ PYTHONPATH=. python3 example/test.py WARNING: Logging before InitGoogleLogging() is written to STDERR W0810 23:10:46.108398 22366 lp_solver.cc:152] ****************************************************************** * WARNING: Glop will be very slow because it will use DCHECKs * * to verify the results and the precision of the solver. * * You can gain at least an order of magnitude speedup by * * compiling with optimizations enabled and by defining NDEBUG. * ****************************************************************** F0810 23:10:46.571289 22366 linear_solver.cc:1692] No solution exists. MPSolverInterface::result_status_ = MPSOLVER_INFEASIBLE *** Check failure stack trace: *** Aborted (core dumped) $ -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (700, 'testing'), (650, 'stable'), (600, 'oldstable'), (500, 'stable-security'), (500, 'unstable'), (450, 'focal'), (350, 'oldoldstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
