-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Beat itest [2/3]: document and fix itest flakes #9307
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
Changes from all commits
d72a0d5
fdddd54
c3cee82
6d1eb98
8e171ce
220c71d
9d79d8d
b73fecc
46ec0bc
dc1d0c7
1ba41fc
4d89b40
cb47db2
eea6671
da77c84
76dab6a
dadceec
097239e
86365c2
55b40e2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -9,6 +9,7 @@ import ( | |
| "github.com/lightningnetwork/lnd/lnrpc/routerrpc" | ||
| "github.com/lightningnetwork/lnd/lntest" | ||
| "github.com/lightningnetwork/lnd/lntest/node" | ||
| "github.com/lightningnetwork/lnd/lntest/wait" | ||
| "github.com/lightningnetwork/lnd/routing" | ||
| "github.com/stretchr/testify/require" | ||
| ) | ||
|
|
@@ -376,7 +377,7 @@ func runFeeEstimationTestCase(ht *lntest.HarnessTest, | |
| ) | ||
| feeReq = &routerrpc.RouteFeeRequest{ | ||
| PaymentRequest: payReqs[0], | ||
| Timeout: 10, | ||
| Timeout: uint32(wait.PaymentTimeout.Seconds()), | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. what is the flake here tho, we are just increasing the timeout to 60s ?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah the previous 10s will cause the payment to time out, updated the commit msg |
||
| } | ||
| } else { | ||
| feeReq = &routerrpc.RouteFeeRequest{ | ||
|
|
||
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.
Why does the windows build have no problem with this call tho, why are we not catching this nil case ?
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.
yeah when running in windows the behavior is quite different, which is why we skip some tests for the window build in the final PR, that being said, we don't really know why windows has this issue, and we now have somewhat a giant TODO list for the windows build.