Closed yushkovskiy closed 7 years ago
Ack. What platform are you on? Does it fail each time?
This got reported once for Ubuntu, probably same JDK issue, apparently fixed https://github.com/os72/protoc-jar/issues/8
Yes we can try the retry approach
My get this error on my laptop about once a day:
$ uname -a
Linux yushkovskiy-nix 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.10
Release: 16.10
Codename: yakkety
$ java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
On CI hosts I see that about 5 times a day:
$ uname -a
Linux fol1-0805.search.yandex.net 3.18.35-35 #1 SMP Mon Jun 20 11:39:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.5 LTS
Release: 12.04
Codename: precise
$ java -version
java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)
I not sure that reordering will help if that this is JDK bug. I guess setting executable flag in forked process could help
OK. I'll need a day or two till I can look into it. I assume you're able to run snapshot versions?
Could you try 3.1.0.6-SNAPSHOT? https://oss.sonatype.org/content/repositories/snapshots/com/github/os72/protoc-jar-maven-plugin/3.1.0.6-SNAPSHOT/
I failed to find com.github.os72:protoc-jar:jar:3.1.0.4-SNAPSHOT. Could you please upload it too?
Done https://oss.sonatype.org/content/repositories/snapshots/com/github/os72/protoc-jar/3.1.0.4-SNAPSHOT/
You could also clone or fork the repos and build yourself, if changes are needed
Seems fixed, but I wish some more time to check it.
Looks like it fixed. Didn't reproduced on snapshot version
Okay great, I'll make a release soon. Did you observe any retries?
Released 3.2.0
Thanks! It is too many logs in our build and it is pretty hard to find something in it on CI.
During run on CI I get the following error
For mvn I use -T2C but I believe that it could be raise between different builds on the same agent. Also it could be result of JDK-8068370 (process) Executing recently modified file results in ETXTBSY
Is it possible to add some retry policy?