-
Notifications
You must be signed in to change notification settings - Fork 130
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
Enable and Fix Environment Examples in CMake CI #642
Enable and Fix Environment Examples in CMake CI #642
Conversation
Codecov Report
@@ Coverage Diff @@
## development #642 +/- ##
===============================================
- Coverage 88.68% 88.63% -0.06%
===============================================
Files 131 131
Lines 7934 7934
===============================================
- Hits 7036 7032 -4
- Misses 898 902 +4
Continue to review full report at Codecov.
|
Looks like the CI is broken on this |
fa20351
to
6f1ef6b
Compare
I am revisiting this pull request.
but running the Python files direcrtly doesn't work. So I had to follow the approach we did when we copied However, I am now stuck with this error:
|
That's a strange one. Looks like maybe a problem with missing / bad plugin? If you disable |
Got the same error :(
|
Never mind.. when I installed:
I no longer got the error.... Now fixing other errors :) |
@ChrisCummins : do you know why the pre-commit job is failing? It seems to be not related to this PR: |
Copy the I broke it yesterday, should be fixed now 🙂 |
Ah, sorry, I was confused! The |
5ac4fea
to
4c1009f
Compare
The CI is failing with I was able to mitigate that on my local machine by adding those arguments when calling
I am not sure why it still fails on CI. Any idea @ChrisCummins ? |
Hmm, not sure about this one. Will have to take a look on Tuesday. Cheers, |
OK. I fixed it in this commit 0077632 by choosing a different name for the registered environment in (Perhaps the error is due to |
Ah, that makes sense. Every environment you register must have a unique name. So if two tests register Cheers, |
try Path instead of runfiles_path to see if CI passes add test without bazel revert commits to bazel tests and update without_bazel test revert name change dont throw errors on UserWarning enable import tests by adding __init__ file avoid importing tests as it causes pytest to throw an error rename env to example-v1 to avoid warning fix test_observation_space get example_unrolling_service to work without bazel avoid 'WARNING: unrolling-v1 environment already exists' error build loop_unroller from within python if it is not found don't include the CMake for standalone build mv clang-10 to clang sometimes clang-10 doesn't exist so handle that
5ce9316
to
e229d5f
Compare
@ChrisCummins ,
do you know a fix for that? (Full log should be here: https://github.com/facebookresearch/CompilerGym/runs/6865005685?check_suite_focus=true) |
Yep. The LLVM binaries we use for CompilerGym don't know about the system libraries, we need to figure them out ourselves. To do this, call compiler_gym.envs.llvm.get_system_library_flags() and append the list of flags it returns to your clang invocation(s). Cheers, |
…st-examples-macos till we build them in bazel
I have removed the explicit run of python examples in CI, and ensured that they run in pytest instead. I have disabled the tests cases in Linux and MacOS bazel builds for now (hopefully will fix that with #707 ). The Pull Request should be ready now for review @ChrisCummins |
LGTM. Many thanks for pushing on this @mostafaelhoushi. Feel free to merge when you're happy with it. Cheers, |
Fixes #631
example_without_bazel_test.py
scriptsenv_tests.py
are invoked in CMake CI by copying them intoenv_without_bazel_test.py
loop_unroller
andopt_loops
binaries in CI #707 )