-
Notifications
You must be signed in to change notification settings - Fork 5
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 the l3node #41
Fix the l3node #41
Conversation
I think we should add a CI workflow to run the smoke test on the L3. It can be based on the current smoke test. Otherwise if we break the L3 support via espresso-dev-node or by breaking the bash script we won't know. |
smoke-test.bash
Outdated
echo "Smoke test succeeded" | ||
docker compose down | ||
|
||
# Testing the l3node |
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.
@ImJeremyHe Lets make it a separate github action workflow run and also test that the staker is working. Either set up a matrix to execute the script with 2 configurations or duplicate the workflow and modify it for the L3. I think both are fine.
- Remove docker caching that would only work on persitent runner
- Check staker confirms nodes
This reverts commit 670ae9e.
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, but wait for CI to pass
This PR:
Fix the L3 node
Currently, when enabling L3 node, we will run an L2 node without enabling the espresso mode.
Also add a simple test for l3 node in smoke-test
How to test this PR
Run the
./smoke-test.bash