Closed xlanor closed 2 years ago
Thanks for reporting, I'll check those errors
@xlanor can you give more details about the environment where you are seeing these errors? What is the OS, architecture and go version that you are using?
Not a problem. It's currently late here but off the top of the head I am only able to reproduce this in a docker Ubuntu environment (doing it using code-server with go 1.17.3)
I'll be able to pull more information tomorrow and hopefully reproduce it. Currently it's sparodic, but the only consistent thing is that when it fails, all three of them fail.
I released a fix that potentially would fix this issue, could you try to update to v1.10.2
and try again?
I'll try it out and let you know!
@xlanor since you haven't come back, I'm assuming this issue is fixed, I'm closing but let me know if the issue persists.
Some of the tests are flaky and failing randomly - mainly related to TestUNIXTime and the like. I've noticed 3 of them randomly failing so far and am opening this issue to investigate at a later stage. This should not be related to any changes in the crypto feature that I was writing as these are in completely different files and non-overlapping.
Edit: Managed to get the verbose output.