You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@solr.apache.org by Chris Hostetter <ho...@fucit.org> on 2026/02/13 18:35:38 UTC

Every Jenkins + Windows build has failed for the past 4 months

Tying to draw some attention to this again...

https://jenkins.thetaphi.de/job/Solr-main-Windows/

  - Last successful build (#7184), 4 mo 12 days ago



https://lists.apache.org/thread/9l5ng8dfsjxvvszft1rgrnx0dk1c077g

> Any build that [has all] pasing tests eventually triggers two
> failures...
>
>   :solr:documentation:checkBrokenLinks
>   :solr:solr-ref-guide:checkSiteLinks
> 
> ...both problems seem to relate to Changes.html, so this smells like
> it might be related to the CHANGES.txt vs logchange generation -- except i
> think these problems predate any logchange related commits? (and they
> don't seem to fail on linux, so probably a subtle path/escaping issue?)

(NOTE: Adjusted incorrect "negative" in original email wording)

-Hoss
http://www.lucidworks.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
For additional commands, e-mail: dev-help@solr.apache.org


Re: Every Jenkins + Windows build has failed for the past 4 months

Posted by Jan Høydahl <ja...@cominvent.com>.
Python is about 10x better than Perl which was the requirement earlier :) Install Py on Jenkins. Solved.

Jan

> 13. feb. 2026 kl. 23:42 skrev David Smiley <ds...@apache.org>:
> 
> We barely use Python; I'd like to see us stop using it where it's not
> needed.  Maybe for this specific thing, we no longer need it any longer.
> Our changelog is now in Markdown, which looks nice.  Or maybe the changelog
> tool we have can generate something.  Either is better than maintaining
> this script and adding a python requirement as well.
> 
> On Fri, Feb 13, 2026 at 2:34 PM Rahul Goswami <ra...@gmail.com> wrote:
> 
>> Ah the classic “works on my machine” strikes again! After the last month’s
>> Solr meetup when you flagged this, I tried running the build and it
>> reproduced immediately. I fixed it, tested it and moved on.
>> 
>> Didn’t closely look at the error specifically on Jenkins. Thanks for
>> spotting this. So I believe installing python3 on Jenkins node should take
>> care of this.
>> 
>> I am assuming the Linux build node already has python3 and so we are not
>> hitting any issues there?
>> 
>> Of course, additionally the gradle build needs to throw an error instead of
>> a warning independent of the platform.
>> 
>> -Rahul
>> 
>> On Fri, Feb 13, 2026 at 2:18 PM Chris Hostetter <ho...@fucit.org>
>> wrote:
>> 
>>> 
>>> 
>>> Ah... the smoking gun...
>>> 
>>> https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
>>> 
>>>> Task :solr:documentation:changesToHtml
>>> WARNING: Python is not installed, skipping creating Changes.html
>>> 
>>> ...this aparently warns w/o failing, and other downstream tasks
>>> dependening on it have no way of knowing that it (effectively) "skipped"
>>> itself.
>>> 
>>> https://issues.apache.org/jira/browse/SOLR-18119
>>> 
>>> 
>>> 
>>> 
>>> : Date: Fri, 13 Feb 2026 12:07:40 -0700 (MST)
>>> : From: Chris Hostetter <ho...@fucit.org>
>>> : To: dev@solr.apache.org
>>> : Subject: Re: Every Jenkins + Windows build has failed for the past 4
>>> months
>>> :
>>> :
>>> : (responding out of order)
>>> :
>>> : : Maybe the Jenkins build is running more tasks.
>>> :
>>> : https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
>>> : cmd.exe /C "C:\Users\jenkins\workspace\Solr-main-Windows\gradlew.bat
>>> : -Dtests.haltonfailure=false -Dtests.badapples=false --continue
>>> --stacktrace
>>> : check && exit %%ERRORLEVEL%%"
>>> :
>>> :
>>> : : I thought I fixed that with
>>> : : https://github.com/apache/solr/pull/4072
>>> :
>>> : IIUC your PR changed the the output encoding of the python script
>>> writing the
>>> : HTML to sysout, which gradle then reads->writes to Changes.html
>>> :
>>> :
>>> : But the jenkins failures don't suggest there was a problem *reading*
>>> : Changes.html The failures suggest the problem was *finding*
>> Changes.html
>>> at
>>> : the expected relative path
>>> :
>>> : > Task :solr:solr-ref-guide:checkSiteLinks FAILED
>>> : {
>>> :  "stats": {
>>> :    "errors": [
>>> :      {
>>> :        "type": "page",
>>> :        "target":
>>> : "..\\..\\..\\documentation\\build\\site\\changes\\Changes.html",
>>> :        "source":
>> "solr\\latest\\upgrade-notes\\solr-upgrade-notes.html",
>>> :        "reason": "page not found"
>>> :      }
>>> :    ],
>>> :
>>> :
>>> : -Hoss
>>> : http://www.lucidworks.com/
>>> :
>>> 
>>> -Hoss
>>> http://www.lucidworks.com/
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
>>> For additional commands, e-mail: dev-help@solr.apache.org
>>> 
>>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
For additional commands, e-mail: dev-help@solr.apache.org


Re: Every Jenkins + Windows build has failed for the past 4 months

Posted by David Smiley <ds...@apache.org>.
We barely use Python; I'd like to see us stop using it where it's not
needed.  Maybe for this specific thing, we no longer need it any longer.
Our changelog is now in Markdown, which looks nice.  Or maybe the changelog
tool we have can generate something.  Either is better than maintaining
this script and adding a python requirement as well.

On Fri, Feb 13, 2026 at 2:34 PM Rahul Goswami <ra...@gmail.com> wrote:

> Ah the classic “works on my machine” strikes again! After the last month’s
> Solr meetup when you flagged this, I tried running the build and it
> reproduced immediately. I fixed it, tested it and moved on.
>
> Didn’t closely look at the error specifically on Jenkins. Thanks for
> spotting this. So I believe installing python3 on Jenkins node should take
> care of this.
>
> I am assuming the Linux build node already has python3 and so we are not
> hitting any issues there?
>
> Of course, additionally the gradle build needs to throw an error instead of
> a warning independent of the platform.
>
> -Rahul
>
> On Fri, Feb 13, 2026 at 2:18 PM Chris Hostetter <ho...@fucit.org>
> wrote:
>
> >
> >
> > Ah... the smoking gun...
> >
> > https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
> >
> > > Task :solr:documentation:changesToHtml
> > WARNING: Python is not installed, skipping creating Changes.html
> >
> > ...this aparently warns w/o failing, and other downstream tasks
> > dependening on it have no way of knowing that it (effectively) "skipped"
> > itself.
> >
> > https://issues.apache.org/jira/browse/SOLR-18119
> >
> >
> >
> >
> > : Date: Fri, 13 Feb 2026 12:07:40 -0700 (MST)
> > : From: Chris Hostetter <ho...@fucit.org>
> > : To: dev@solr.apache.org
> > : Subject: Re: Every Jenkins + Windows build has failed for the past 4
> > months
> > :
> > :
> > : (responding out of order)
> > :
> > : : Maybe the Jenkins build is running more tasks.
> > :
> > : https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
> > : cmd.exe /C "C:\Users\jenkins\workspace\Solr-main-Windows\gradlew.bat
> > : -Dtests.haltonfailure=false -Dtests.badapples=false --continue
> > --stacktrace
> > : check && exit %%ERRORLEVEL%%"
> > :
> > :
> > : : I thought I fixed that with
> > : : https://github.com/apache/solr/pull/4072
> > :
> > : IIUC your PR changed the the output encoding of the python script
> > writing the
> > : HTML to sysout, which gradle then reads->writes to Changes.html
> > :
> > :
> > : But the jenkins failures don't suggest there was a problem *reading*
> > : Changes.html The failures suggest the problem was *finding*
> Changes.html
> > at
> > : the expected relative path
> > :
> > : > Task :solr:solr-ref-guide:checkSiteLinks FAILED
> > : {
> > :  "stats": {
> > :    "errors": [
> > :      {
> > :        "type": "page",
> > :        "target":
> > : "..\\..\\..\\documentation\\build\\site\\changes\\Changes.html",
> > :        "source":
> "solr\\latest\\upgrade-notes\\solr-upgrade-notes.html",
> > :        "reason": "page not found"
> > :      }
> > :    ],
> > :
> > :
> > : -Hoss
> > : http://www.lucidworks.com/
> > :
> >
> > -Hoss
> > http://www.lucidworks.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
> > For additional commands, e-mail: dev-help@solr.apache.org
> >
> >
>

Re: Every Jenkins + Windows build has failed for the past 4 months

Posted by Rahul Goswami <ra...@gmail.com>.
Ah the classic “works on my machine” strikes again! After the last month’s
Solr meetup when you flagged this, I tried running the build and it
reproduced immediately. I fixed it, tested it and moved on.

Didn’t closely look at the error specifically on Jenkins. Thanks for
spotting this. So I believe installing python3 on Jenkins node should take
care of this.

I am assuming the Linux build node already has python3 and so we are not
hitting any issues there?

Of course, additionally the gradle build needs to throw an error instead of
a warning independent of the platform.

-Rahul

On Fri, Feb 13, 2026 at 2:18 PM Chris Hostetter <ho...@fucit.org>
wrote:

>
>
> Ah... the smoking gun...
>
> https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
>
> > Task :solr:documentation:changesToHtml
> WARNING: Python is not installed, skipping creating Changes.html
>
> ...this aparently warns w/o failing, and other downstream tasks
> dependening on it have no way of knowing that it (effectively) "skipped"
> itself.
>
> https://issues.apache.org/jira/browse/SOLR-18119
>
>
>
>
> : Date: Fri, 13 Feb 2026 12:07:40 -0700 (MST)
> : From: Chris Hostetter <ho...@fucit.org>
> : To: dev@solr.apache.org
> : Subject: Re: Every Jenkins + Windows build has failed for the past 4
> months
> :
> :
> : (responding out of order)
> :
> : : Maybe the Jenkins build is running more tasks.
> :
> : https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
> : cmd.exe /C "C:\Users\jenkins\workspace\Solr-main-Windows\gradlew.bat
> : -Dtests.haltonfailure=false -Dtests.badapples=false --continue
> --stacktrace
> : check && exit %%ERRORLEVEL%%"
> :
> :
> : : I thought I fixed that with
> : : https://github.com/apache/solr/pull/4072
> :
> : IIUC your PR changed the the output encoding of the python script
> writing the
> : HTML to sysout, which gradle then reads->writes to Changes.html
> :
> :
> : But the jenkins failures don't suggest there was a problem *reading*
> : Changes.html The failures suggest the problem was *finding* Changes.html
> at
> : the expected relative path
> :
> : > Task :solr:solr-ref-guide:checkSiteLinks FAILED
> : {
> :  "stats": {
> :    "errors": [
> :      {
> :        "type": "page",
> :        "target":
> : "..\\..\\..\\documentation\\build\\site\\changes\\Changes.html",
> :        "source": "solr\\latest\\upgrade-notes\\solr-upgrade-notes.html",
> :        "reason": "page not found"
> :      }
> :    ],
> :
> :
> : -Hoss
> : http://www.lucidworks.com/
> :
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
> For additional commands, e-mail: dev-help@solr.apache.org
>
>

Re: Every Jenkins + Windows build has failed for the past 4 months

Posted by Chris Hostetter <ho...@fucit.org>.

Ah... the smoking gun...

https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText

> Task :solr:documentation:changesToHtml
WARNING: Python is not installed, skipping creating Changes.html

...this aparently warns w/o failing, and other downstream tasks 
dependening on it have no way of knowing that it (effectively) "skipped" 
itself.

https://issues.apache.org/jira/browse/SOLR-18119




: Date: Fri, 13 Feb 2026 12:07:40 -0700 (MST)
: From: Chris Hostetter <ho...@fucit.org>
: To: dev@solr.apache.org
: Subject: Re: Every Jenkins + Windows build has failed for the past 4 months
: 
: 
: (responding out of order)
: 
: : Maybe the Jenkins build is running more tasks.
: 
: https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
: cmd.exe /C "C:\Users\jenkins\workspace\Solr-main-Windows\gradlew.bat
: -Dtests.haltonfailure=false -Dtests.badapples=false --continue --stacktrace
: check && exit %%ERRORLEVEL%%"
: 
: 
: : I thought I fixed that with
: : https://github.com/apache/solr/pull/4072
: 
: IIUC your PR changed the the output encoding of the python script writing the
: HTML to sysout, which gradle then reads->writes to Changes.html
: 
: 
: But the jenkins failures don't suggest there was a problem *reading*
: Changes.html The failures suggest the problem was *finding* Changes.html at
: the expected relative path
: 
: > Task :solr:solr-ref-guide:checkSiteLinks FAILED
: {
:  "stats": {
:    "errors": [
:      {
:        "type": "page",
:        "target":
: "..\\..\\..\\documentation\\build\\site\\changes\\Changes.html",
:        "source": "solr\\latest\\upgrade-notes\\solr-upgrade-notes.html",
:        "reason": "page not found"
:      }
:    ],
: 
: 
: -Hoss
: http://www.lucidworks.com/
: 

-Hoss
http://www.lucidworks.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
For additional commands, e-mail: dev-help@solr.apache.org


Re: Every Jenkins + Windows build has failed for the past 4 months

Posted by Chris Hostetter <ho...@fucit.org>.
(responding out of order)

: Maybe the Jenkins build is running more tasks.

https://jenkins.thetaphi.de/job/Solr-main-Windows/8230/consoleText
cmd.exe /C "C:\Users\jenkins\workspace\Solr-main-Windows\gradlew.bat -Dtests.haltonfailure=false -Dtests.badapples=false --continue --stacktrace check && exit %%ERRORLEVEL%%"


: I thought I fixed that with
: https://github.com/apache/solr/pull/4072

IIUC your PR changed the the output encoding of the python script writing 
the HTML to sysout, which gradle then reads->writes to Changes.html


But the jenkins failures don't suggest there was a problem *reading* 
Changes.html The failures suggest the problem was *finding* Changes.html 
at the expected relative path

> Task :solr:solr-ref-guide:checkSiteLinks FAILED
{
  "stats": {
    "errors": [
      {
        "type": "page",
        "target": "..\\..\\..\\documentation\\build\\site\\changes\\Changes.html",
        "source": "solr\\latest\\upgrade-notes\\solr-upgrade-notes.html",
        "reason": "page not found"
      }
    ],


-Hoss
http://www.lucidworks.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
For additional commands, e-mail: dev-help@solr.apache.org


Re: Every Jenkins + Windows build has failed for the past 4 months

Posted by Rahul Goswami <ra...@gmail.com>.
I thought I fixed that with
https://github.com/apache/solr/pull/4072

gw dev | build | check were all failing prior to that. And I verified they
pass post the fix.
Maybe the Jenkins build is running more tasks.
I’ll try to check this over the weekend.

-Rahul

On Fri, Feb 13, 2026 at 1:37 PM Chris Hostetter <ho...@fucit.org>
wrote:

>
> Tying to draw some attention to this again...
>
> https://jenkins.thetaphi.de/job/Solr-main-Windows/
>
>   - Last successful build (#7184), 4 mo 12 days ago
>
>
>
> https://lists.apache.org/thread/9l5ng8dfsjxvvszft1rgrnx0dk1c077g
>
> > Any build that [has all] pasing tests eventually triggers two
> > failures...
> >
> >   :solr:documentation:checkBrokenLinks
> >   :solr:solr-ref-guide:checkSiteLinks
> >
> > ...both problems seem to relate to Changes.html, so this smells like
> > it might be related to the CHANGES.txt vs logchange generation -- except
> i
> > think these problems predate any logchange related commits? (and they
> > don't seem to fail on linux, so probably a subtle path/escaping issue?)
>
> (NOTE: Adjusted incorrect "negative" in original email wording)
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@solr.apache.org
> For additional commands, e-mail: dev-help@solr.apache.org
>
>