-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
[WIP] Enable remaining Scala Native tests #274
base: main
Are you sure you want to change the base?
Conversation
@WojciechMazur any chance I could trouble you to look into these? The failures should be on the Scala-Native side of things |
lihaoyi, Thank you for the time you and others have spent adding support for Scala Native. @WojciechMazur asked me to look at the macOS & Linux process related errors. I guess Through code inspection I have already discovered & PR'd one bug. My next step is to run the reproducer which Wojciech has created against the most recently Then I might see if I can run it against a private build of Scala Native containing my fix from Realistically, I think I will have to do some minimal private design studies where a pipe gets I'll keep you posted, but it is probably doing to be multiple days between updates. Does this fit in with your plan? |
Yes please take your time investigating, take as long as you need |
I've found an additional bug in Scala Native 0.5.4-SNAPSHOT. With a trial fix for that bug and the I hope to create a PR for Scala Native in the next day or so. |
lolgab, Thank you for updating to Scala Native 0.5.4. It looks like some of the tests are failing, linux & macOS. Is it evident to you that something is going You have more experience and knowledge looking at these CI log files than I do. Thank you for your time. |
@LeeTibbert looks like its getting stuck and timing out |
These tests currently fail on Scala-Native, but pass on Scala-JVM, and do not have a reason they should not pass on Scala-Native as well