Hi,
The best way if you want to fix these flaky tests (ie non deterministic
tests) is to try to reproduce them in your favorite IDE.
Regards,
Raphaël Ouazana.
Le 2017-06-08 13:28, cryptearth a écrit :
Hey Benoit,
first: sorry for getting your name the wrong way around - I was
confused by yo
Hey Benoit,
first: sorry for getting your name the wrong way around - I was confused by
your signature.
About maildir not supported on Windows: didn't knew, but IOException got thrown
and the stack for it made it pretty clear whats happening.
Fun fact: try to compile a class called "aux" - it
Hi,
My answers inlined...
Cheers,
Le 08/06/2017 à 16:16, cryptearth a écrit :
> Hey Rapael,
>
> I know about this as Tellier told me this once the first time I reported
> issues when first tried to build beta5. So this is what I as a hobbiest don't
> understand: if the commit that is made pub
Hey Rapael,
I know about this as Tellier told me this once the first time I reported issues
when first tried to build beta5. So this is what I as a hobbiest don't
understand: if the commit that is made public at least passed all tests once -
why it's failing so differently on my different build
Hey Matt,
Thank you for your interest in this project.
You seem to have some issues building James. That's something that can
happen because with have some flaky tests, and not enough time to solve
them all.
But you should now that each time we are making a commit, all the tests
do pass at le