Failed
gpkit.tests.t_examples.TestExamples.test_docstringparsing_mosek_cli (from gpkit.tests.t_examples.TestExamples-20240103165649)
Failing for the past 1 build
(Since Failed
)
Error Message
Solver failed for an unknown reason. Relaxing constraints/constants, bounding variables, or using a different solver might fix it. Running `.debug()` or increasing verbosity may pinpoint the trouble.
Stacktrace
Traceback (most recent call last): File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\solvers\mosek_cli.py", line 86, in optimize for logline in check_output(["mskexpopt", filename, "-sol", File "C:\Miniconda3\lib\subprocess.py", line 421, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "C:\Miniconda3\lib\subprocess.py", line 526, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['mskexpopt', 'C:\\Users\\jenkins\\AppData\\Local\\Temp\\tmpn6zseg4i\\gpkit_mosek', '-sol', 'C:\\Users\\jenkins\\AppData\\Local\\Temp\\tmpn6zseg4i\\gpkit_mosek.sol']' returned non-zero exit status 1001. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\constraints\gp.py", line 207, in solve solver_out = solverfn(c=self.cs, A=self.A, meq_idxs=self.meq_idxs, File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\solvers\mosek_cli.py", line 95, in optimize raise UnknownInfeasible() from e gpkit.exceptions.UnknownInfeasible The above exception was the direct cause of the following exception: Traceback (most recent call last): File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\tests\helpers.py", line 55, in test testfn(name, import_dict, path)(self) File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\tests\helpers.py", line 90, in test imported[name] = importlib.import_module(name) File "C:\Miniconda3\lib\importlib\__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\docs\source\examples\docstringparsing.py", line 48, in <module> print(c.solve(verbosity=0).table()) File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\constraints\prog_factories.py", line 133, in solvefn result = progsolve(solver, verbosity=verbosity, **kwargs) File "C:\Users\jenkins\workspace\CE_gpkit_Push_unit_tests\buildnode\windows10x64\optimizer\mosek\gpkit\constraints\gp.py", line 245, in solve raise infeasibility.__class__(msg) from infeasibility gpkit.exceptions.UnknownInfeasible: Solver failed for an unknown reason. Relaxing constraints/constants, bounding variables, or using a different solver might fix it. Running `.debug()` or increasing verbosity may pinpoint the trouble.
Standard Output
Warning: SignomialConstraint x + y >= z became the tautological constraint 0 <= 1 + x after substitution.