Walletwasabi: Fix Windows CI

[nopara73]

Title says it. It's failing consistently.

[jmacato]

https://github.com/zkSNACKs/WalletWasabi/blob/452f61e0d7c51a31fb7c1f5f6832842940e64c7c/WalletWasabi.Tests/UnitTests/BitcoinCore/NodeBuildingTests.cs#L90 this is where Azure logs say it times out.. perhaps the node is taking too long to respond or has crashed way too early?

[molnard]

No, it is not the timeout, unfortunately. No matter how long will u set it is still failing.

@satwo did you found something?

Tried to fix here: https://github.com/zkSNACKs/WalletWasabi/pull/3589

[satwo]

Not yet- will work on it more this evening.

On Fri, May 15, 2020, 8:21 AM Dávid Molnár [e-mail] wrote:

No, it is not the timeout, unfortunately. No matter how long will u set it
is still failing.

@satwo https://github.com/satwo did you found something?

Tried to fix here: #3589
https://github.com/zkSNACKs/WalletWasabi/pull/3589

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zkSNACKs/WalletWasabi/issues/3660#issuecomment-629204453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABF2EWY5QU4R5MISCQYFMGDRRUXWDANCNFSM4NBLKBRQ
.

[molnard]

@satwo OK. Clue: if Knots started in a way that it will immediately jump into some processings, for example syncing on mainnet we might not get an answer from it until the processing finishes. I noticed something similar on computers with HDD.

Probably CI machines are not the fastest on, neither.

[stale[bot]]

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[molnard]

This issue is part of https://github.com/zkSNACKs/WalletWasabi/issues/4152 Closing this.