-
Notifications
You must be signed in to change notification settings - Fork 65
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
modernize cln tests and CI #259
Conversation
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.
Thanks!
Some queries inline.
@@ -69,4 +73,4 @@ jobs: | |||
- name: Run tests | |||
run: | | |||
cd watchtower-plugin/tests | |||
DEVELOPER=1 SLOW_MACHINE=1 poetry run pytest test.py --log-cli-level=INFO -s | |||
VALGRIND=0 SLOW_MACHINE=1 poetry run pytest test.py --log-cli-level=INFO -s |
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.
Is VALGRIND
enabled by default?
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.
i think so, but not sure when and where it's used to be honest
f76d3c9
to
481768a
Compare
Ah yes thanks github for changing the default branch name. |
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.
Looks like we are still facing several issues:
allow_broken_log
doesn't seem to be an option anymore: https://github.com/talaia-labs/rust-teos/actions/runs/9731968733/job/27975219502?pr=259#step:9:89gevent
doesn't seem to be installed so theclnrest
plugin is being killed on init: https://github.com/talaia-labs/rust-teos/actions/runs/9731968733/job/27975219502?pr=259#step:9:86- The
cln-grpc
plugin is missing needs to be passed a port, so it's also being killed on init: https://github.com/talaia-labs/rust-teos/actions/runs/9731968733/job/27975219502?pr=259#step:9:134
481768a
to
dd65ad8
Compare
@sr-gi clnrest and cln-grpc are just plugins to serve the rpc via REST and GRPC. They are not relevant for this project and can safely be ignored. I removed the functions mentioning DEVELOPER. I'm not sure how they were still used, i could not find any code for them anymore. Indeed allow_broken_log was removed in favor of broken_log which requires explicitly stating the expected broken log. Please check that the log lines i used are actually expected! |
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.
This works now, but the code needs to be properly formatted. Run black -l 120 watchtower-plugin/tests
locally.
Looks good otherwise, thanks for taking the time to fix this!
watchtower-plugin/tests/test.py
Outdated
@@ -123,7 +120,7 @@ def test_auto_retry_watchtower(node_factory, bitcoind, teosd): | |||
{}, | |||
{ | |||
"plugin": WT_PLUGIN, | |||
"allow_broken_log": True, | |||
"broken_log": r'plugin-watchtower-client: Data was send to an idle retier. This should have never happened. Please report!.*', |
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.
This made me realize that there was a typo on this logline. Would you care changing it here and on the plugin side?
retier -> retrier
dd65ad8
to
f6decde
Compare
done
done |
LGTM. Rust lint issues are unrelated. Any additional comment @mariocynicys? |
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.
One last comment on my end.
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 :)
Replaces #255
I think in your PR tests ran slow because you were running them on an ancient pyln-testing version. Just to make sure i added VALGRIND=0 as that can cause huge slowdowns but i don't know when valgrind actually runs in these tests.
I also assume you don't want CI to run on anything else than commit to the master branch. While testing with a PR all CI ran both for the feature branch and the PR kinda weird.
Also
developer: None
is not needed with a modernpyln-testing
version, as that is a default setting.