Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG Automatic install of classes fails #106

Closed
ngazagna opened this issue Dec 15, 2020 · 2 comments
Closed

BUG Automatic install of classes fails #106

ngazagna opened this issue Dec 15, 2020 · 2 comments

Comments

@ngazagna
Copy link

First, I have corrected in the benchmark solver files of benchmark_logreg_l2 in my branch FIX_utils_import

from benchopt.util import safe_import_context

by

from benchopt.utils.safe_import import safe_import_context

to solve a first bug which should be raised in an issue in all concerned benchmarks.

Then I still get this error because lightning cannot be installed automatically by the Benchmark class:

$ benchopt run ../benchmarks/benchmark_logreg_l2 
Installing Lightning in None:... failed
/home/nidham/phd/benchOpt/benchopt/benchmark.py:116: UserWarning: Some solvers were not successfully installed, and will thus be ignored. Use 'export BENCHO_RAISE_INSTALL_ERROR=true' to stop at any installation failure and print the traceback.
  warnings.warn(
/tmp/tmp02ch3slw: line 2: benchopt.benchmark.Benchmark: No such file or directory
@tomMoral
Copy link
Member

You should use the master version of the benchmark where I fixed all the import error: benchopt/benchmark_logreg_l2@4fc90c2

Also, if you want to see the install error, you can call BENCHO_RAISE_INSTALL_ERROR=1 benchopt run path/bench/logreg_l2.

Finally, it seems that you are calling the benchmark with an existing conda env that does not have the latest version of benchopt. You should use the -r flag that will reinstall everything to get rid of the line 2: benchopt.benchmark.Benchmark: No such file or directory error.

@tomMoral
Copy link
Member

Ok It was a bug on our side actually.
This should have been fixed by #108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants