search

borisbrodski / sevenzipjbinding

7-Zip-JBinding
http://sevenzipjbind.sourceforge.net/
Other
176 stars 50 forks source link

Corrupted STDOUT when used with maven-failsafe-plugin #20

Open lasselindqvist opened 5 years ago

lasselindqvist commented 5 years ago

When this library is used with maven-failsafe-plugin we often get a warning [2019-04-25T12:03:20.202Z] [WARNING] Corrupted STDOUT by directly writing to native stream in forked JVM 1. See FAQ web page and the dump file

Not sure if this is something that can be solved here though.

Related links: https://maven.apache.org/surefire/maven-failsafe-plugin/faq.html#corruptedstream

borisbrodski commented 5 years ago

Hi,

I'm not aware of writing to stdout from the productive 7-Zip-JBinding code, besides major failures, where JVM should be terminated.

Are you experiencing any problems with getting test results to the Maven plugin?

lasselindqvist commented 5 years ago

I am not really an expert on this particular issue, but I suspect that the problem is with 7-zip itself, not the bindings, since 7-zip does not support a silent mode.

borisbrodski commented 4 years ago

Do you know, which archive format codec may contain std output statements?

lasselindqvist commented 4 years ago

We used this for reading ZIP archives and also for DMGs (https://en.wikipedia.org/wiki/Apple_Disk_Image). We removed the ZIP reading because that was doable with the standard library quite easily, but still rely on reading DMGs, and I haven't seen these issues anymore, which is why I suspect the ZIPs caused the problem.