[
https://issues.apache.org/jira/browse/LUCENE-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367696#comment-16367696
]
Steve Rowe commented on LUCENE-8106:
------------------------------------
bq. [~thetaphi], I'll try to set up a job for your master slave.
I did this, after copying the configuration for the
{{Lucene-Solr-master-Linux}} project:
https://jenkins.thetaphi.de/job/Lucene-Solr-repro-Linux/
But I ran into three problems:
# The Parameterized Trigger plugin is not installed, but AFAIK is required to
pass information from the upstream job (to know where the upstream job's build
log is)
# When I tried to configure the {{Lucene-Solr-master-Linux}} project to trigger
building the new project, the "Build other projects" item in the "Add
post-build action" menu is greyed out.
# I'm not sure how to pass the randomized JDK+cmdline options to the repro
script - I suppose via the Parameterized Trigger plugin?
> Add script to attempt to reproduce failing tests from a Jenkins log
> -------------------------------------------------------------------
>
> Key: LUCENE-8106
> URL: https://issues.apache.org/jira/browse/LUCENE-8106
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Major
> Fix For: master (8.0), 7.3
>
> Attachments: LUCENE-8106-part2.patch, LUCENE-8106.patch,
> LUCENE-8106.patch
>
>
> This script will be runnable from a downstream job triggered by an upstream
> failing Jenkins job, passing log location info between the two.
> The script will also be runnable manually from a developer's cmdline.
> From the script help:
> {noformat}
> Usage:
> python3 -u reproduceJenkinsFailures.py URL
> Must be run from a Lucene/Solr git workspace. Downloads the Jenkins
> log pointed to by the given URL, parses it for Git revision and failed
> Lucene/Solr tests, checks out the Git revision in the local workspace,
> groups the failed tests by module, then runs
> 'ant test -Dtest.dups=5 -Dtests.class="*.test1[|*.test2[...]]" ...'
> in each module of interest, failing at the end if any of the runs fails.
> To control the maximum number of concurrent JVMs used for each module's
> test run, set 'tests.jvms', e.g. in ~/lucene.build.properties
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
