[ https://issues.apache.org/jira/browse/LUCENE-8106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367516#comment-16367516 ]
Steve Rowe commented on LUCENE-8106: ------------------------------------ [~thetaphi], I'll try to set up a job for your master slave. I'm not sure which entries you're referring to in {{lucene.build.properties}}? Here's how ASF Jenkins is populated (from [https://builds.apache.org/view/L/view/Lucene/job/Lucene-Ivy-Bootstrap/configure]): {noformat} tests.multiplier=2 smokeTestRelease.testArgs=-Dtests.slow=false tests.jvms=3 {noformat} AFAICT none of those refer to Python. The repro job on ASF Jenkins invokes the script like this: {noformat} /usr/bin/python3 -u dev-tools/scripts/reproduceJenkinsFailures.py --no-fetch https://builds.apache.org/job/$UPSTREAM_JOB_NAME/$UPSTREAM_BUILD_NUMBER/consoleText {noformat} (On my Jenkins the URL points to the local log file instead of using HTTPS.) > 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