Bug 216558 - comms/rxtx: Set MAKE_JOBS_UNSAFE
Summary: comms/rxtx: Set MAKE_JOBS_UNSAFE
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Craig Leres
URL:
Keywords: patch
: 216557 (view as bug list)
Depends on: 216248
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-28 21:21 UTC by Craig Leres
Modified: 2019-01-01 03:18 UTC (History)
2 users (show)

See Also:
james: maintainer-feedback+
koobs: merge-quarterly?


Attachments
patch (467 bytes, patch)
2017-01-28 21:21 UTC, Craig Leres
koobs: maintainer-approval+
Details | Diff
podriere build log showing build failure (118.11 KB, text/plain)
2017-01-28 21:23 UTC, Craig Leres
no flags Details
make.conf (888 bytes, text/plain)
2017-01-28 22:37 UTC, Craig Leres
no flags Details
JCE - comms/rxtx (epoch 3) build log from a clean ports build (42.28 KB, text/plain)
2017-02-08 22:36 UTC, James Elstone
no flags Details
JCE - comms/rxtx (epoch 4) build log from a clean ports build (4 (42.33 KB, text/plain)
2017-02-08 22:39 UTC, James Elstone
no flags Details
JCE - poudriere.conf (working) (523 bytes, text/plain)
2017-02-08 22:48 UTC, James Elstone
no flags Details
poudriere.conf diff against .sample that causes build failure (4.14 KB, text/plain)
2017-02-13 06:50 UTC, Craig Leres
no flags Details
podriere build log showing build failure (7.51 KB, text/plain)
2018-02-10 23:52 UTC, Craig Leres
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Leres freebsd_committer 2017-01-28 21:21:44 UTC
Created attachment 179384 [details]
patch

rxtx-openjdk8 (comms/rxtx) fails to make package unless MAKE_JOBS_UNSAFE is turned on (see attached poudriere build log). While we're here define LICENSE.
Comment 1 Craig Leres freebsd_committer 2017-01-28 21:23:58 UTC
Created attachment 179385 [details]
podriere build log showing build failure
Comment 2 Tilman Keskinoz freebsd_committer 2017-01-28 21:45:07 UTC
*** Bug 216557 has been marked as a duplicate of this bug. ***
Comment 3 James Elstone 2017-01-28 22:03:24 UTC
Would it be possible to share your contents of /etc/make.conf on the compile host in question please?

Kr,

James
Comment 4 James Elstone 2017-01-28 22:10:26 UTC
LICENSE defined in bug #216248.
Comment 5 James Elstone 2017-01-28 22:20:34 UTC
Comment on attachment 179384 [details]
patch

LICENSE defined in dependency added.
Comment 6 Craig Leres freebsd_committer 2017-01-28 22:37:29 UTC
Created attachment 179387 [details]
make.conf

Here's a make.conf I copied out of the jail I got with "poudriere bulk -i ..."
Comment 7 James Elstone 2017-01-28 22:51:43 UTC
Many Thanks; looking into issue now.

Kr,
James
Comment 8 James Elstone 2017-01-31 23:10:06 UTC
(In reply to leres from comment #0)
Have looked at the log you have supplied.

With the EPOCH 4 patch submitted in bug #216248 applied, the reported issue is not seen (confirmed today with a "bulk -c" being issued on poudriere).

On doing a diff between the working (bug #216248) and failed (this report) log I noticed:
- Non-default port options set on zinc.ee.lbl.gov (e.g. "png" being built on zinc)
- OS 10.3-p16 on zinc, OS 11.0-p7 on radon
- custom make options set on zinc

Will run a new build on a 10.3 jail to see if I can replicate the issue shown.  I wonder if this is an issue only seen on <11.0?!

Should have answer to above question in about 10 hours...
Comment 9 James Elstone 2017-02-01 08:06:20 UTC
Just built on fresh FreeBSD 10.3-p16 without any build options set, without issue.

Going to add your make.conf settings in to see if that leads to an error, but right now I cannot replicate the issue you are experiencing.
Comment 10 James Elstone 2017-02-07 22:46:21 UTC
Wow! Your options file rocks; llvm39 with -g set results in llvm39 package which is over 100GB in size!!

(Delay in responding due to my build machine having had a full workout!)

However, I cannot recreate the issue you have posted; Can I have some more information please?

Can you provide a copy of the following from the build machine (not inside the jail) please:

grep -v # /etc/make.conf
grep -v # /usr/local/etc/poudriere.conf 

Also can you confirm the command line you are using to launch poudriere when experiencing this error please?

Kr,

James.
Comment 11 James Elstone 2017-02-08 22:36:16 UTC
Created attachment 179777 [details]
JCE - comms/rxtx (epoch 3) build log from a clean ports build

FreeBSD 10.3 amd64
using LBL poudriere make file
fresh clean ports tree
latest ports version of openJDK v8
rxtx-openjdk8-2.2p2_3.log

Working, no build issue seen.
Comment 12 James Elstone 2017-02-08 22:39:22 UTC
Created attachment 179778 [details]
JCE - comms/rxtx (epoch 4) build log from a clean ports build (4

FreeBSD 10.3 amd64
using LBL poudriere make file
fresh patched ports tree with Epoc 4 (see bug #216248)
latest ports version of openJDK v8
rxtx-openjdk8-2.2p2_3.log

Working, no build issue seen.

Do need information requested in comment #10
Comment 13 James Elstone 2017-02-08 22:48:33 UTC
Created attachment 179779 [details]
JCE - poudriere.conf (working)

Attached working /usr/local/etc/poudriere.conf file.

(Also noted is that FreeBSD Jenkins build cluster has been compiling EPOCH 3 for sometime without issue.)

Maybe the issue is local to the "zinc" build machine?

Further information from reporter of issue required to recreate; not doubting issue exists, but need to understand how to replicate the issue to confirm resolution is appropriate.
Comment 14 Craig Leres freebsd_committer 2017-02-13 06:45:17 UTC
I removed /etc/make.conf and the make.conf used with my poudriere build jail and then started commenting out non-default lines in my poudriere.conf. Looks like PRIORITY_BOOST causes the problem. I'll attach a diff.
Comment 15 Craig Leres freebsd_committer 2017-02-13 06:50:34 UTC
Created attachment 179927 [details]
poudriere.conf diff against .sample that causes build failure
Comment 16 w.schwarzenfeld freebsd_triage 2018-02-10 14:53:10 UTC
Status?
Comment 17 Craig Leres freebsd_committer 2018-02-10 23:52:06 UTC
Created attachment 190498 [details]
podriere build log showing build failure

I still see frequent poudriere build errors without MAKE_JOBS_UNSAFE=yes:

    Error: cannot access gnu.io.RS485.MonitorThread

see attached build log.
Comment 18 w.schwarzenfeld freebsd_triage 2018-02-11 00:22:32 UTC
Cannot read attachment. How is it encoded?
Comment 19 Craig Leres freebsd_committer 2018-02-11 00:24:36 UTC
It's gzip'ed.
Comment 20 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-20 10:20:25 UTC
Reporter is committer, assign accordingly
Comment 21 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-20 10:23:25 UTC
Comment on attachment 179384 [details]
patch

Approved by: koobs (ports)

@Craig Please include the error message in the commit log message that has been observed without this patch added. (ie with parallel builds) and merge to quarterly too
Comment 22 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-20 10:27:16 UTC
This issue, while technically a maintainer timeout (1+ years since last maintainer response, 10 months since last comment), we as developers/triagers should remember to set maintainer-feedback to ? <maintainer-email> in cases that we want/need feedback, or the maintainer-approval flag on attachments where we want approval, so that we have 'explicitly requested it', rather than left it implicit.

Once ? <maintainer-email> is set on a flag, you can then:

Approved by: portmgr (maintainer timeout: > 2 weeks)

at your leisure.