Bug 2105384

Summary: truth FTBFS after injection of ExclusiveArch: %{java_arches} noarch, but this macro is not guilty
Product: [Fedora] Fedora Reporter: jiri vanek <jvanek>
Component: truthAssignee: Orion Poplawski <orion>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: java-maint-sig, java-sig-commits, jhuttana, jvanek, orion, pmikova, sgehwolf, zzambers
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: truth-1.0.1-4.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-10 03:56:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2105362    

Description jiri vanek 2022-07-08 16:29:23 UTC
Hello! Your package got injected

      ExclusiveArch:  %{java_arches} noarch
      
      See https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs

And failed, to build from sources (FTBFS), however the macro itself is not a cause. I had checked tha fialure, and the build is failing for longer time (mostly since jdk17 was introduced).
Please elaborate, or your package will be retired, and orphaned later.
It is also reason, why this bug is not blocking the https://bugzilla.redhat.com/show_bug.cgi?id=2083750.

Comment 1 Orion Poplawski 2022-07-09 03:52:45 UTC
I'm not able to figure out why the build is failing.  Any help would be appreciated.

Comment 2 jiri vanek 2022-07-11 12:02:56 UTC
interesting, it passed for you at the end!

Comment 3 jiri vanek 2022-07-12 09:13:40 UTC
I see, you lowered to jdk11. If jdk17 is the cause, then My bet would be that jdk17 had hidden some packages/classes form being visible. Adding  exports/opens usually helps but the stack trace is usually a bit different.
Recentloy I hit and issue, where ourd wonstream depndece had changed build system from gradle, to pom, and they had not used the moduleinfo/manifest logic from  upstream fgradle, so downstream was broken, and the trace was pretty similatr .. bt not same.

The usptream build passes fine with jdk17. So I would really bet on broken downstream depndence. Maybe ping them?