-
Notifications
You must be signed in to change notification settings - Fork 223
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
Fixed flaky tests #581
Fixed flaky tests #581
Conversation
ofc the "Fixed flaky tests" PR has flaky tests |
I would really like to spot the problem, but testing locally 100 times with jdk 11 I haven't been able to reproduce it. Any idea @eed3si9n? |
Maybe the property based testing doesn't need to consider version numbers with hanzi/kanji characters in them?
|
Wow, how did you picked that line in that huge log? Btw, I think you're right, in a few I'll push a fix for that |
Is not so trivial, after some iterations I get errors like this
even if I set something strict like private val genChar = Gen.alphaNumChar I'll investigate further |
I don't know why but in this commit this line was added: numbers = prefix.toSeq ++: vn.numbers.drop(prefix.length) To the best of my understanding, this should concatenate and empty list to Removing this genVersionNumber.map { vn =>
VersionNumber(
numbers = prefix.toSeq ++: vn.numbers.drop(prefix.length),
tags = vn.tags,
extras = vn.extras
)
} |
In general feel free to remove any flaky tests too if it's not delivering values. It's not like we have a ton of bug reports complaining about version number parsing. |
Okay 👍 This time, I think I fixed it in a meaningful way btw :) |
Closes #455.
See this comment for details.