-
Notifications
You must be signed in to change notification settings - Fork 23
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
pip install fails to build c simulator #41
Comments
Specifically, we should have two tests that are triggered in GitHub Actions:
from qokit.fur import get_available_simulator_names
assert 'c' in get_available_simulator_names('x')
assert 'c' in get_available_simulator_names('xyring')
assert 'c' in get_available_simulator_names('xycomplete')
import dumpy as np
from qokit import get_qaoa_labs_objective
theta = np.random.uniform(0,1,280)
f = get_qaoa_labs_objective(20, 140)
# timer start
f(theta)
# timer end
assert time_elapsed < 5 # seconds Make sure that these tests are decorated properly to be only run in Github actions |
@alex124585, may I ask if there's been any progress on this? |
I believe import dumpy as np should be import numpy as np |
after run pip install . in omniq I am getting >>> get_available_simulator_names() |
Huh! Can you please add the test to confirm this is also the case in GitHub actions? |
I just did an install in a clean OmniQ instance and the simulator was not built correctly. Reopening this issue.
from qokit.fur import get_available_simulator_names
print(get_available_simulator_names("x")) gives |
Running
pip install .
fails to build c simulator on OmniQ.As an additional fix, Github actions should check that c simulator is built correctly
The text was updated successfully, but these errors were encountered: