-
Notifications
You must be signed in to change notification settings - Fork 211
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
chore: make the test-ci-all work harder #4524
Conversation
72b5bba
to
7121ba5
Compare
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.
Verified just test-ci-all
works locally, but I'm seeing errors on back-compat.
22867 │ 00:00:25 Error: polling lightningd after 10 retries
22868 │ 00:00:25
22869 │ 00:00:25 Caused by:
22870 │ 00:00:25 0: connect to lightningd
22871 │ 00:00:25 1: No such file or directory (os error 2)
22872 │ ## FAILED: devimint_cli_test (FM: current, CLI: current, GW: v0.2.1)
I'll continue tweaking params on my end. Approving since I think it's safe to merge and followup.
@m1sterc001guy If you have a chance I'm curious if this resolves the issues you had locally.
For this one we should just increase the time. 10s is not a lot. 30s seems more reasonable. |
I bumped to 30 and now seeing networking errors with the bitcoind client
|
This way eliminate any dead time at the end, and things should go faster.
7121ba5
to
ba51945
Compare
@bradleystachurski All, right. I've lowered the default load again, and added ability to customize it locally:
drop a file in there like that, tune to your liking, reload the dev shell and it should do the job. |
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.
.shrc.local
is a solid solution. Making tweaks locally allowed just test-compatibility
to pass again 👍
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.
Didn’t test
@@ -288,7 +288,7 @@ pub async fn latency_tests(dev_fed: DevFed, r#type: LatencyTest) -> Result<()> { | |||
let fm_pay_stats = stats_for(fm_internal_pay); | |||
|
|||
println!("### LATENCY FM PAY: {fm_pay_stats}"); | |||
assert!(fm_pay_stats.median < Duration::from_secs(12)); | |||
assert!(fm_pay_stats.median < Duration::from_secs(15)); |
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.
Maybe latency tests should not run in parallel on the same machine? This hack may hide latency introduced from round trips that don't require much compute?
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.
Good callout 👍
Made an issue to make sure we keep track #4579.
No description provided.