-
Notifications
You must be signed in to change notification settings - Fork 31
Path issue when running tests #71
Comments
I noticed that the path issue can be resolved by replacing I've installed it from source, so This might not be to everyone's tastes: ligo_cmd = "ligo"
with Popen(f"{ligo_cmd} changelog", stdout=PIPE, stderr=PIPE, shell=True) as changelog_command:
changelog = changelog_command.stdout.read().decode()
assert " 0.7.1 " in changelog I haven't imposed a maximum version. Anyway, after that, I see there are failures in the tests, eg:
|
This repo uses symlinks to bring reusable files into example projects. When running Ligo as a docker container, its PWD should be a parent directory not only for the example code directory, but for all linked directories as well. |
Upon trying to run the tests in eg
single_asset
, there is an issue with the paths during the importing of different.mligo
files:Here I've installed the smart-contracts directory as a submodule within
/home/owen/tezos/fa2-demo/
.I had first tried running the tests in
smart-contracts/nft_assets
, but had some Python errors there too, intezos_fa2_nft_tests/test_fa2.py
where the reference topytezos.rpc.errors
must've been out of date − happy to submit a PR for that once I can get these tests running :) (same LIGO path issue).The errors occur as soon as relative paths are used, eg in
fa2_single_token.mligo
:… #include "../fa2/fa2_interface.mligo"
I was invoking the test from
~/tezos/fa2-demo/smart-contracts/single_asset
The text was updated successfully, but these errors were encountered: