Does anyone here invoke the smokeTester outside of an RC vote?
TLDR: Looking for help to see that someone else has run it on "main"
successfully, can do so now to confirm, and maybe knows some Python.

In the course of expanding its scope, naturally I need to invoke this
thing to ensure it actually works as expected.  I've encountered one
problem after another after another when trying to do so.  Since I'm
not interested is expanding my repertoire to Python, LLMs helped me
expand the scope and then play wack-a-mole with the bugs/difficulties
I was encountering in running it.  At this point, I question whether
the basic assumptions for running it outside of an RC ever hold or
require tribal knowledge that I lack.  After examining its docs/help,
I was a bit lost so then I went to the Jenkins job to see how it's
configured.

The Smoketester has been failing for awhile and actually has failed
for one of the reasons I saw.  It's concerning the Changes.html not
having the expected version:
https://ci-builds.apache.org/job/Solr/job/Solr-Smoketest-10.0/174/console

By examining the Job build steps, I see it's necessary to do:

./gradlew clean
./gradlew assembleRelease

#!/bin/bash
echo "Installing Python script requirements"
pip3 install -r dev-tools/scripts/requirements.txt
export TMP_ROOT=$(pwd)/_tmp
mkdir -p $TMP_ROOT
export SMOKE_TMP=$TMP_ROOT/smoke_$GIT_COMMIT_$(date +%s)
export SOLR_VERSION=$(ls solr/distribution/build/release | sed -r -n
's/.*solr-([a-zA-Z0-9.-]+).tgz$/\1/p' | grep -v 'src$' | grep -v
'slim')
export GIT_REV=$(git rev-parse HEAD)
echo "Starting Smoke tester in folder $(pwd)"
python3 -u dev-tools/scripts/smokeTestRelease.py --tmp-dir $SMOKE_TMP
--not-signed --revision $GIT_REV --version $SOLR_VERSION
file://$(pwd)/solr/distribution/build/release

Any help is appreciated.

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to