[
https://issues.apache.org/jira/browse/SOLR-16634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680306#comment-17680306
]
Ishan Chattopadhyaya commented on SOLR-16634:
---------------------------------------------
[~krisden], you started the you said/i said discussions here based on things
said on SOLR-15616, which were based on my attempts to navigate the problems
and solve them. But, *this ticket* is different. It is not about what you said,
or I said. It is not mainly about "gradlew localSettings" spitting out 1G
either, though it was noted in the description for additional context. This
issue is about a *fresh clone* and "gradlew check" failing on it. It should
not, and accusing me of being "in capable of reading the logs" misses the point
I'm trying to make here: a new user using a fresh checkout shouldn't need to
deduce what he/she needs to do based on a failed run. Either it should just
work, or a pre-requisite (necessary) step should be advised in the
CONTRIBUTING.md document.
I can issue point by point rebuttal to everything you mentioned above and prove
you wrong. But, it is irrelevant to this issue. So, I concede defeat for now
(because I have better things to do), and I'm prepared to hand you a prize for
winning the argument, if you so want.
bq. Yeah, you really have to run localSettings first.
[~magibney], yes, that's the current situation and I know that. With this
issue, I was hoping of exploring whether it necessarily has to be that way? And
if so, shouldn't it be necessary for a user to run it (say, first build doesn't
even attempt a build, until localSettings have been run once)? In Solr 8x, "ant
ivy-bootstrap" was a necessary pre-step.
> "gradlew check" fails with OOM on fresh clone
> ---------------------------------------------
>
> Key: SOLR-16634
> URL: https://issues.apache.org/jira/browse/SOLR-16634
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Priority: Major
>
> I have a 64GB machine, where a fresh Solr clone was done. "gradlew check"
> failed with this following:
> https://issues.apache.org/jira/browse/SOLR-15616?focusedCommentId=17679832&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17679832
> {code}
> [ishan@7980xe solr] $ ./gradlew check -x test -Pvalidation.errorprone=true
> Downloading gradle-wrapper.jar from
> https://raw.githubusercontent.com/gradle/gradle/v7.6.0/gradle/wrapper/gradle-wrapper.jar
> To honour the JVM settings for this build a single-use Daemon process will be
> forked. See
> https://docs.gradle.org/7.6/userguide/gradle_daemon.html#sec:disabling_the_daemon.
> Daemon will be stopped at the end of the build
> > Task :localSettings
> IMPORTANT. This is the first time you ran the build. I wrote some sane
> defaults (for this machine) to 'gradle.properties', they will be picked up on
> consecutive gradle invocations (not this one).
> Run gradlew :helpLocalSettings for more information.
> > Task :rat
> Trying to override old definition of task javadoc
> > Task :solr:solrj:compileJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> > Task :solr:solrj-streaming:compileJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> > Task :solr:solrj-zookeeper:compileJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> FAILURE: Build failed with an exception.
> * What went wrong:
> Gradle build daemon has been stopped: JVM garbage collector thrashing and
> after running out of JVM memory
> * Try:
> > Run with --stacktrace option to get the stack trace.
> > Run with --info or --debug option to get more log output.
> > Run with --scan to get full insights.
> * Get more help at https://help.gradle.org
> {code}
> For context, [~krisden] has attributed this to user error:
> https://issues.apache.org/jira/browse/SOLR-15616?focusedCommentId=17679837&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17679837
> Please also note that "gradlew localSettings" also resulted in a subsequent
> OOM failure (details here:
> https://issues.apache.org/jira/browse/SOLR-15616?focusedCommentId=17679841&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17679841)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
