Created attachment 207354 [details] Update to 4.13 Upgrade from 4.12 to 4.13. No relnotes link available yet, as of this submission.
Will there be a link to some release notes sometime in the near future or is it too new to have one ?
The official release date is 18-Sep-2019. It should be ready by then, very likely on https://www.eclipse.org/eclipseide/2019-09/noteworthy/
The release page is up at https://www.eclipse.org/eclipseide/2019-09/ Release notes at https://www.eclipse.org/eclipseide/2019-09/noteworthy/
Testbuilds done. For whatever reason, the testbuilds seem to end in: =>> Killing runaway build after 7200 seconds with no output For example: https://people.freebsd.org/~pi/logs/eclipse-runaway-build.txt or https://people.freebsd.org/~pi/logs/java__eclipse-120-1568146810.txt (same if you replace 120 with cur, 113, 112).
Created attachment 207667 [details] Update to 4.13 Update patches to use p2-repo references in offline-maven repo. Distfile daemonblade-eclipse-maven-repo-4.13_GH0.tar.gz has been re-rolled.
testbuilds@work
(In reply to Kurt Jaeger from comment #6) The build looks similar. It stays at the [INFO] --- tycho-packaging-plugin:1.5.0-SNAPSHOT:package-plugin (default-package-plugin) @ org.eclipse.osgi --- line. No detectable progress.
Same behaviour: =>> Killing runaway build after 7200 seconds with no output
My local builds are running to completion. I must admit I don't know why it's not working on the testbuild hosts. Could you please tweak the Makefile and change "do-build" directive from: ... mvn --offline ... to: ... mvn -X --offline ... This provides verbose logs that I will have to look at. Thanks!
The verbose log, currently hanging at the usual place, can be found at https://people.freebsd.org/~pi/logs/eclipse-verbose.txt
There doesn't seem to be an obvious fix from looking at the logs. I will have to compare the logs from my local good builds vs the bad builds on the testbuild host. Unfortunately, I will be away from tomorrow, and will not be available to do this until 11-Oct-2019.
I'll do a testbuild on a Intel CPU (the other test was on a AMD Ryzen Threadripper 2950X 16-Core).
Same problem on Intel: =>> Killing runaway build after 3600 seconds with no output
FWIW, I downloaded the patch and was able to do a build while my network connection was down.
(In reply to Greg Lewis from comment #14) Greg, with the latest update to openjdk8-8.232.09.1_1, I can now reproduce the hanging issue. Could you retry? I'll see if I can build DEBUG version to see where the java-vm is hanging.
Sorry for not responding earlier. I didn't disconnect my network this time, but I can still build the port with the newer version of openjdk8.
I attached truss(1) onto a hanging build, and it appears to be looping on: openat(AT_FDCWD,"/construction/xports/java/eclipse/work/eclipse.platform.releng.aggregator-R4_13/.git/.probe-7955aaca-b297-4605-a27c-0dd8d7905281",O_WRONLY|O_CREAT|O_TRUNC,0666) = 241 (0xf1) close(241) = 0 (0x0) fstatat(AT_FDCWD,"/construction/xports/java/eclipse/work/eclipse.platform.releng.aggregator-R4_13/.git/.probe-7955aaca-b297-4605-a27c-0dd8d7905281",{ mode=-rw-r--r-- ,inode=105710,size=0,blksize=4096 },0x0) = 0 (0x0) _umtx_op(0x8007fb1e8,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdebe8d08) ERR#60 'Operation timed out' _umtx_op(0x8007fb1e8,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdebe8d08) ERR#60 'Operation timed out' _umtx_op(0x8007fb1e8,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdebe8d08) ERR#60 'Operation timed out' _umtx_op(0x8007fb008,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdfffadb8) ERR#60 'Operation timed out' openat(AT_FDCWD,"/construction/xports/java/eclipse/work/eclipse.platform.releng.aggregator-R4_13/.git/.probe-7955aaca-b297-4605-a27c-0dd8d7905281",O_WRONLY|O_CREAT|O_TRUNC,0666) = 241 (0xf1) close(241) = 0 (0x0) fstatat(AT_FDCWD,"/construction/xports/java/eclipse/work/eclipse.platform.releng.aggregator-R4_13/.git/.probe-7955aaca-b297-4605-a27c-0dd8d7905281",{ mode=-rw-r--r-- ,inode=105710,size=0,blksize=4096 },0x0) = 0 (0x0) _umtx_op(0x8007fb1e8,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdebe8d08) ERR#60 'Operation timed out' _umtx_op(0x8007fb1e8,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdebe8d08) ERR#60 'Operation timed out' _umtx_op(0x8007fb008,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x7fffdfffadb8) ERR#60 'Operation timed out' [...] I did a quick check on the chroot, and the file was successfully being created, however, the _umtx_op() is failing. I do not know what _umtx_op() is. The file name changes on subsequent hanging builds, but the _umtx_op() timeout is consistent.
It doesn't appear to be a network issue. I'm using 'synth' to build the port, and I think it has network connectivity in all its build-phases. The problem appears to be a chroot/jail related, as I'm able to build outside of the chroot'd system, but not within it.
Obsoleted by update to 4.14: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243017