-
Notifications
You must be signed in to change notification settings - Fork 525
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
Create DINFRA_milestone_2.md #1075
Conversation
Thanks for the delivery @rvalle starting my evaluation now. |
thanks @keeganquigley let me know if you need anything. |
@keeganquigley how is it going? did you get any troubles starting the whole cluster locally? |
Hi @rvalle apologies for the delay., and thanks for your patience since this project takes some time to set up. So far all the Docker packages are working and I can run it to simulate the deployment cycles, but am still running into some failing tests.
WARNING: Image for service zombietest was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating dinfra_zombietest_1 ... error
ERROR: for dinfra_zombietest_1 Cannot start service zombietest: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/ubuntu/dinfra/parachain/zombienet/config.yaml" to rootfs at "/home/zombienet/config.yaml": mount /home/ubuntu/dinfra/parachain/zombienet/config.yaml:/home/zombienet/config.yaml (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: for zombietest Cannot start service zombietest: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/ubuntu/dinfra/parachain/zombienet/config.yaml" to rootfs at "/home/zombienet/config.yaml": mount /home/ubuntu/dinfra/parachain/zombienet/config.yaml:/home/zombienet/config.yaml (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
error Command failed with exit code 1.
> ogate
$ yarn build
$ nest build
> acs-reactor
warning package.json: No license field
$ yarn build
warning package.json: No license field
$ yarn build:prepare
warning package.json: No license field
$ bash -c 'mkdir -p deps && cp -a ../dinfra-client-python deps && . ./venv/bin/activate && pip install -r requirements.txt'
cp: cannot stat '../dinfra-client-python': No such file or directory
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
Exit code: 1
Command: /home/ubuntu/.nvm/versions/node/v18.13.0/bin/node
Arguments: /home/ubuntu/.nvm/versions/node/v18.13.0/lib/node_modules/yarn/lib/cli.js run build:workspace
Directory: /home/ubuntu/dinfra/packages/acs-reactor
Output:
info Visit https://yarnpkg.com/en/docs/cli/workspaces for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. I'm running: |
Good to see that you got the cluster to run. Building the docker containers is more reliable, as there are no local dependencies, than building and testing locally. Note that the local build/test steps already run on Continuous Integration so we can always check the .gitlabci as source of truth, and the output of pipelines as for what to expect.
Your environment looks good to me. But I think you had some regression in your environment because some steps required for the docker build are now failing. I guess the root cause is that the project is very demanding in terms of disk space... perhaps you had to delete the project and then re-install it later, or perhaps you run out of disk space at some point and subsequent attempts failed. Let me know if this helps. When in doubt use the gitlabci as guide ensuring that the parachain submodule is checked out. |
Thanks for your help @rvalle looks great now. Everything works and the zombienet tests run now. The above commands worked; I will update the eval accordingly.
|
Everything is working now and you can find my final eval here. Great work and congrats! |
🪙 Please fill out the invoice form in order to initiate the payment process. Thank you! |
We noticed that this is the last milestone of your project. Congratulations on completing your grant! 🎊 |
@keeganquigley thanks for your review. |
Yes sorry, I forgot to mention that I did try to join the private Element chat but it kept giving me an error and wouldn't let me join for some reason, sorry about that. |
thanks for the info @keeganquigley most probably our homeserver needs an update or something. will review it. |
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#1622 and later updated payment destination in w3f/Grants-Program#1884