-
Notifications
You must be signed in to change notification settings - Fork 18
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
Fix: Execution creation was not tested #558
Conversation
f700d21
to
6319dfd
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #558 +/- ##
==========================================
+ Coverage 35.44% 43.83% +8.38%
==========================================
Files 54 55 +1
Lines 4900 4944 +44
Branches 585 585
==========================================
+ Hits 1737 2167 +430
+ Misses 3140 2658 -482
- Partials 23 119 +96 ☔ View full report in Codecov by Sentry. |
45cb904
to
13ad705
Compare
I managed to get the VM working, only one blocking issue left: # FIXME: This import fails to work in a VM when using pytest
from aleph.sdk.chains.remote import RemoteAccount |
Is there a way to test this locally? I'm trying with |
I added doc to run the tests in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a few place were more documentation is needed. Otherwise look good to me, a part from the problem in the example that still fail. And also we should be able to disable test requiring root
8d1fc3e
to
689d672
Compare
Solution: Add a test that creates a new VM execution and checks that it starts properly.
Solution: Accept a `pathlib.Path` as argument and convert as string.
Co-authored-by: Olivier Le Thanh Duong <[email protected]>
This tests that a VM from the aleph.im network can be downloaded and launched. Co-authored-by: ajin <[email protected]>
Solution: Modify hatch configuration to have the environmnent properly set up using the virtual environment builtin module https://hatch.pypa.io/1.3/plugins/environment/virtual/
It's a problem surfaced by another The visible problem was that the new exection test were hanging, inside the runtime, during the import at the line from aleph.sdk.chains.remote import RemoteAccount after some more investigative work, it was pin pointed to an inner import of eth_utils module (specifically eth_utils.network ) Second problem that made the first visible: in the runtime the pre-compiled bytecode, created during runtime creation in create_disk_image.sh was not used, which made the import of module slower. This surfaced the first problem. The cause of that second problem was that the init1.py code which run the user caude was not launched with the same optimization level as the pre-compiled bytecode and thus recompiled everything. (this is specified in the init1.py #! sheebang on the first line) Solution: Compile the bytecode with the same optimisation level (-o 2 ) as during run We haven't found out yet why the eth_utils.network import hang when it is not precompiler. But this fix the test hanging issue
…asyncio' Fix: async_sessionmaker was introduced in sqlachemy 2.0, ensure we have at least this version otherwhise it was using a older system package
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now
Failed to retrieve llama text: POST 504: 504 Gateway Time-outThe server didn't respond in time. |
Solution: Add a test that creates a new VM execution and checks that it starts properly.