-
Notifications
You must be signed in to change notification settings - Fork 53
[Bug] test failed #200
Comments
odd - I cloned latest and it seemed reasonably quick (but I do have an M1 pro) |
It's some kind of network issue? or db lock? |
I'm guessing it's a db lock issue. cc: @nitro-neal I know you're looking into similar cases (like for revocations). |
After read some docs, |
About time cost, I don't know if there was a db lock issue at now, but network access really cost times in |
I'm pretty sure that this bug was introduced by me. It was because the DB was being created with the same file. I'm also pretty sure that it was fixed in #201. I introduced a random file for the creation of the DB within each tests in the code below.
RE: the long time to execute each test, 100% agree that it's network access from Thanks for the insights @suutaku |
Describe the bug
clone master, and run
mage test
first time, got failed result. but try agin maybe will passed. time cost also very long. (router test will take 92.222s)To Reproduce
mage test
Expected behavior
Try more times, maybe 4 or 5 times.
Supporting Material
Environment (please complete the following information):
Additional context
Looks like something timeout? but i did not get any message with timeout. first time run test will have some cache, try agin
The text was updated successfully, but these errors were encountered: