Again, not having a failure- it just always hangs in that one place- either
on that test or on the next one I'm not sure.
On Mon, May 4, 2020 at 8:57 AM Christofer Dutz
wrote:
> I just had a failure in core which was a timing issue that doesn't always
> happen.
> So right now if I get
I just had a failure in core which was a timing issue that doesn't always
happen.
So right now if I get failures and simply-re running gets rid of them, I add
them to the flaky tests txt file ...
You did notice, that on failure maven tells you how to resume from the failed
module (So you
I misspoke- it was in the Scala bindings, this is the last line to print
off:
https://github.com/apache/mahout/blob/758cfada62556d679c445416dff9d9fb2a3c4e59/core/src/test/scala/org/apache/mahout/math/scalabindings/MatrixOpsSuite.scala#L222
Hope akm or someone else can test to help me figure out
Hi Trevor,
core sort of always passed for me ... it was some of the community modules I
had to run multiple times because of flaky unit tests.
Will re-try on my machines.
Chris
Am 04.05.20, 14:51 schrieb "Trevor Grant" :
On Java 8 when I build with tests it always hangs on
```
On Java 8 when I build with tests it always hangs on
```
Average assignment seqSparse2seqSparse time: 25.776 ms
Average assignment seqSparse2seqSparse via Random Access Sparse time:
224.714 ms
```
It seems like that's in the Mahout Core section. What is our new "official
target" java? I have
No ... I think I was able to go up till 10 ... above that I think I remember I
had errors.
13 is also quite intense when it comes to changes in what you're allowed to do
with reflection.
Chris
Am 03.05.20, 20:39 schrieb "Trevor Grant" :
Is JDK 13 supposed to work now? I was able to get
