Bug 240480 - java/eclipse: update to 4.13
Summary: java/eclipse: update to 4.13
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Kurt Jaeger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-10 19:45 UTC by Jonathan Chen
Modified: 2019-11-24 04:39 UTC (History)
3 users (show)

See Also:


Attachments
Update to 4.13 (51.06 KB, patch)
2019-09-10 19:45 UTC, Jonathan Chen
jonc: maintainer-approval+
Details | Diff
Update to 4.13 (51.88 KB, patch)
2019-09-21 00:37 UTC, Jonathan Chen
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Chen 2019-09-10 19:45:05 UTC
Created attachment 207354 [details]
Update to 4.13

Upgrade from 4.12 to 4.13.

No relnotes link available yet, as of this submission.
Comment 1 Kurt Jaeger freebsd_committer 2019-09-10 20:18:38 UTC
Will there be a link to some release notes sometime in the near future or is it too new to have one ?
Comment 2 Jonathan Chen 2019-09-10 20:29:46 UTC
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/
Comment 3 Jonathan Chen 2019-09-15 19:35:21 UTC
The release page is up at https://www.eclipse.org/eclipseide/2019-09/

Release notes at https://www.eclipse.org/eclipseide/2019-09/noteworthy/
Comment 4 Kurt Jaeger freebsd_committer 2019-09-19 17:19:48 UTC
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).
Comment 5 Jonathan Chen 2019-09-21 00:37:56 UTC
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.
Comment 6 Kurt Jaeger freebsd_committer 2019-09-21 06:04:11 UTC
testbuilds@work
Comment 7 Kurt Jaeger freebsd_committer 2019-09-21 06:59:37 UTC
(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.
Comment 8 Kurt Jaeger freebsd_committer 2019-09-21 11:50:47 UTC
Same behaviour:

=>> Killing runaway build after 7200 seconds with no output
Comment 9 Jonathan Chen 2019-09-21 20:22:31 UTC
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!
Comment 10 Kurt Jaeger freebsd_committer 2019-09-22 07:58:14 UTC
The verbose log, currently hanging at the usual place, can be found at

https://people.freebsd.org/~pi/logs/eclipse-verbose.txt
Comment 11 Jonathan Chen 2019-09-23 08:49:37 UTC
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.
Comment 12 Kurt Jaeger freebsd_committer 2019-09-23 08:59:50 UTC
I'll do a testbuild on a Intel CPU (the other test was on a AMD Ryzen Threadripper 2950X 16-Core).
Comment 13 Kurt Jaeger freebsd_committer 2019-09-24 04:07:48 UTC
Same problem on Intel:

=>> Killing runaway build after 3600 seconds with no output
Comment 14 Greg Lewis freebsd_committer 2019-10-09 17:42:37 UTC
FWIW, I downloaded the patch and was able to do a build while my network connection was down.
Comment 15 Jonathan Chen 2019-10-20 04:25:21 UTC
(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.
Comment 16 Greg Lewis freebsd_committer 2019-10-30 18:45:41 UTC
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.
Comment 17 Jonathan Chen 2019-11-23 23:47:38 UTC
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.
Comment 18 Jonathan Chen 2019-11-24 04:39:13 UTC
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.