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
Speed up CI tests, replace delays with "signalling" #4244
Comments
Shall I make those notes here? |
@molnard Sure, you can. |
WalletWasabi.xml?
Probably this can be sped up.
Probably this can be sped up.
Try to reduce the delay to 1 ms. That will ensure Threadpool execution and the less delay possible. I am not sure about this have to try.
This is good, these are polling intervals. Can you change the timeout logic that is using TimeSpan and StopWatch of DateTimeOffset?
It depends, can we detect if tx in the mempool?
It depends, can we detect if tx in the mempool?
It depends, are we the ones who set 8 sec to registration timeout?
Strange timeout detection, also I would reduce the poll interval to 100 ms.
reduce the poll interval to 100 ms.
reduce the poll interval to 100 ms.
Same for all, reduce the poll interval to 100 ms.
Use a better timeout mechanism and reduce polling interval to 100ms
Use a better timeout mechanism, detect mempool if possible
Seems to be good.
Hmm why waiting here? It depends on the precision of GetLastWriteTimeUtc. Need to test it.
Probably this can be improved, low prio.
Waiting for expiration looks good.
idk might be OK.
Can we poll?
Can we poll?
Can we poll?
Can we detect instead of wait? |
#4245 is linked to this. |
|
@molnard I believe this issue should be closed. If there are some other flaky tests. We should file them to new issues, I guess. |
This issue is part of #4152 project.
I have searched for
Task.Delay(
in theWalletWasabi.Tests
project in VS Code. The results follow. It's moderate amount of results and I would like each occurrence either mark as "OK" or "makes tests unstable" (which would require a PR for fixing that).The text was updated successfully, but these errors were encountered: