You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They previously weren't supported at all on 0.4.x due to lack of multithreading. Now that multithreading exists, I would assume they should work, but they don't.
I'm not sure how to go about begin debugging this on Scala-Native, but presumably if the same code is passing on Scala-JVM and failing on Scala-Native, it is a Scala-Native bug.
At a first glance, it seems it might be some kind of multithreading bug, where we are trying to convert a java.util.concurrent.ConcurrentLinkedQueue into a Vector via a VectorBuilder, and someone along the chain is having its internal invariants violated
The text was updated successfully, but these errors were encountered:
They previously weren't supported at all on 0.4.x due to lack of multithreading. Now that multithreading exists, I would assume they should work, but they don't.
To repro,
os.proc
on Scala Native com-lihaoyi/os-lib#257./mill -i "os.jvm[2.12.17].test" test.os.SubprocessTests.lines
to see the code passing on Scala-JVM./mill -i "os.native[2.12.17].test" test.os.SubprocessTests.lines
to see the exact same Scala code failing on Scala-Native 0.5.0This gives me the following error:
I'm not sure how to go about begin debugging this on Scala-Native, but presumably if the same code is passing on Scala-JVM and failing on Scala-Native, it is a Scala-Native bug.
At a first glance, it seems it might be some kind of multithreading bug, where we are trying to convert a
java.util.concurrent.ConcurrentLinkedQueue
into aVector
via aVectorBuilder
, and someone along the chain is having its internal invariants violatedThe text was updated successfully, but these errors were encountered: