[
https://issues.apache.org/jira/browse/SOLR-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514073#comment-17514073
]
Jan Høydahl commented on SOLR-16041:
------------------------------------
I suspected perhaps that the untar'ed folder
{{_tmp/smoke_1648549517/unpack/solr-9.0.0-java11/solr-example.log}} is R/O and
thus the log file creation fails.
I think bin/solr is executable, because the next output is "Sending stop
command to Solr running on port 8983 ... waiting up to 180 seconds" which is
indeed printed by {{bin/solr stop}}.
Can try to add a command "chmod -R 777 <unpack-dir>" to smoke-tester after
unpacking. I see the same error when trying "rm -rf <unpack-dir>" in
releaseWizard, first have to chmod before it can be removed...
> Prepare a Jenkins job that runs smoke tester on 9.0
> ---------------------------------------------------
>
> Key: SOLR-16041
> URL: https://issues.apache.org/jira/browse/SOLR-16041
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: 9.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The old ant build had a [target
> "nightly-smoke"|https://github.com/apache/lucene-solr/blob/branch_8_11/build.xml#L420:L466]
> that would build the release and run smoketester on it. This was run nightly
> before each release in Jenkins to catch issues early -
> [https://ci-builds.apache.org/job/Lucene/job/Lucene-Solr-SmokeRelease-8.11/]
> Could be useful to have a similar mechanism now.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
