Closed juancnuno closed 7 months ago
CC @igordmn -- I can repro this myself, too. Is there a way we can tell Skiko where to dump the files with a flag? That way we can solve the problem without having to have a before/after on every test suite.
where to dump the files with a flag
There is currently no way to tell where to extract binaries (dll/so/dylib), but there is a way to use already extracted binaries.
You can extract binaries from these files:
Place them in ./lib/skiko
, and load them from there this way:
System.setProperty("skiko.library.path", "./lib/skiko")
Would it be hard to add a property to pick the auto-extract folder? So we don't have to reimplement the download and extract logic ourselves
Not hard, we will do it soon
Thanks 🙏
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.
One of our Compose tests failed with the following stack trace on Linux
Adding the following to the test
works around the issue
Skiko wants to write a file at Library.kt:37. When the test is run by Bazel, the destination path resolves to a directory that does not exist (because of Bazel's sandboxing or whatever). IdeaTestSuiteBase overrides user.home to java.io.tmpdir. The workaround reproduces that bit of IdeaTestSuiteBase.