== Comment: #0 - NISHANTH ARAVAMUDAN <aravam.com> - 2013-02-08 17:42:07 == While attempting to get autotest server (including web frontend) working on FC18 (originally on FC17, but problem persists after upgrade), I am unable to compile the GWT frontend: From a checkout of autotest, run ./utils/compile_gwt_clients.py -a and they will all fail to compile: Will attach log of compilation of autotest.AfeClient, which indicates a StackOverflow in java. lmr (Lucas Meneghel at RedHat) on IRC indicated this successfully compiles on x86/x86_64 platforms. == Comment: #1 - NISHANTH ARAVAMUDAN <aravam.com> - 2013-02-08 17:43:28 == Output from: java -Xmx512M -cp "/usr/local/autotest/frontend/client/src:/usr/local/autotest/frontend/client/bin:/usr/local/autotest/site-packages/gwt/gwt-user.jar:/usr/local/autotest/site-packages/gwt/gwt-dev.jar" -Djava.awt.headless=true com.google.gwt.dev.Compiler -war "/usr/local/autotest/frontend/client/www.new" autotest.AfeClient == Comment: #2 - NISHANTH ARAVAMUDAN <aravam.com> - 2013-02-08 19:37:13 == Just verified on my FC16 box that compilation there from the current tree is successful. The difference (and I think this has been the case since FC17, but not 100%) is java-1.7.0-openjdk vs. java-1.6.0-openjdk? Manually removing 1.7.0 from FC18 and replacing with 1.6.0 from FC16 leads to successful compilation. Actually, I also noticed that the FC17 1.7.0 was removed, rather than the FC18 version. I will wait for this compilation to finish, update to the latest FC18 java and re-test. Regardless, I think this means the FC17 version is/was broken. Thanks, Nish == Comment: #3 - NISHANTH ARAVAMUDAN <aravam.com> - 2013-02-08 20:02:54 == Confirmed that bug persists in FC18, after updating back to the latest from the repositories. Fails to compile.
Created attachment 696216 [details] Log of compilation failure
Hi Can you try this with -XX:ThreadStackSize=2048 (or -Xss2048k )? Also I would like to provide a later version of the jvm (hsx24 vs hsx22) for testing but will need access to a machine to do builds. Chris
------- Comment From aravam.com 2013-02-21 21:43 EDT------- (In reply to comment #7) > Hi > Can you try this with -XX:ThreadStackSize=2048 (or -Xss2048k )? Thanks for the suggestion, compiling the GWT frontend with -Xss2048k does seem to succeed.
------- Comment From kamaleshb.com 2013-06-07 05:34 EDT------- Hi RedHat, Is this expected to be fixed in Fedora19 ? Thanks.
There doesn't seem to be anything to fix.
------- Comment From kamaleshb.com 2013-06-19 07:14 EDT------- (In reply to comment #10) > There doesn't seem to be anything to fix. As per comment#2 (RedHat bugzilla) later version for jvm was to be provided for testing. It sounded like there will be in change ThreadStackSize in the later version(s), so asked the question.
------- Comment From kamaleshb.com 2013-07-23 08:10 EDT------- Closing the bug, as no issued were seen with Fedora 19.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.