You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@lucene.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2025/05/17 05:33:56 UTC
[JENKINS] Lucene » Lucene-Check-main - Build # 12808 - Failure!
Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/12808/
No tests ran.
Build Log:
[...truncated 32 lines...]
ERROR: Could not download gradle-wrapper.jar (IOException: Server returned HTTP response code: 429 for URL: https://raw.githubusercontent.com/gradle/gradle/v8.14.0/gradle/wrapper/gradle-wrapper.jar).
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Re: [JENKINS] Lucene » Lucene-Check-main - Build # 12808 - Failure!
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
the workspace cleanup is done to remove any compile artifact which is
and was needed to make sure we have a "clean" room. The main reason was
that we wanted to make sure that the subversion (now git) checks for
workspace unmodified had a good internal state.
What I wonder about: Policeman Jenkins never had that problem and it
also cleans workspace. Maybe it is caused by too many ASF builds doing
the same like we do. I think it might be better to ask ASF Infra to get
in contact with Github and/or Gradle to figure out what can be done.
Uwe
Am 17.05.2025 um 10:47 schrieb Dawid Weiss:
>
> We have workspace cleaning enabled on this job (and possibly other
> jobs). This removes the gradle wrapper on each run. I wonder if we
> need to do it. Alternatively, we could retry with a timeout on 429 in
> the wrapperdownloader.
>
> D.
>
> On Sat, May 17, 2025 at 7:34 AM Apache Jenkins Server
> <je...@builds.apache.org> wrote:
>
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/12808/
>
> No tests ran.
>
> Build Log:
> [...truncated 32 lines...]
> ERROR: Could not download gradle-wrapper.jar (IOException: Server
> returned HTTP response code: 429 for URL:
> https://raw.githubusercontent.com/gradle/gradle/v8.14.0/gradle/wrapper/gradle-wrapper.jar).
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test
> report files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@lucene.apache.org
> For additional commands, e-mail: builds-help@lucene.apache.org
>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:uwe@thetaphi.de
Re: [JENKINS] Lucene » Lucene-Check-main - Build # 12808 - Failure!
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
the workspace cleanup is done to remove any compile artifact which is
and was needed to make sure we have a "clean" room. The main reason was
that we wanted to make sure that the subversion (now git) checks for
workspace unmodified had a good internal state.
What I wonder about: Policeman Jenkins never had that problem and it
also cleans workspace. Maybe it is caused by too many ASF builds doing
the same like we do. I think it might be better to ask ASF Infra to get
in contact with Github and/or Gradle to figure out what can be done.
Uwe
Am 17.05.2025 um 10:47 schrieb Dawid Weiss:
>
> We have workspace cleaning enabled on this job (and possibly other
> jobs). This removes the gradle wrapper on each run. I wonder if we
> need to do it. Alternatively, we could retry with a timeout on 429 in
> the wrapperdownloader.
>
> D.
>
> On Sat, May 17, 2025 at 7:34 AM Apache Jenkins Server
> <je...@builds.apache.org> wrote:
>
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/12808/
>
> No tests ran.
>
> Build Log:
> [...truncated 32 lines...]
> ERROR: Could not download gradle-wrapper.jar (IOException: Server
> returned HTTP response code: 429 for URL:
> https://raw.githubusercontent.com/gradle/gradle/v8.14.0/gradle/wrapper/gradle-wrapper.jar).
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test
> report files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@lucene.apache.org
> For additional commands, e-mail: builds-help@lucene.apache.org
>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:uwe@thetaphi.de
Re: [JENKINS] Lucene » Lucene-Check-main - Build # 12808 - Failure!
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
the workspace cleanup is done to remove any compile artifact which is
and was needed to make sure we have a "clean" room. The main reason was
that we wanted to make sure that the subversion (now git) checks for
workspace unmodified had a good internal state.
What I wonder about: Policeman Jenkins never had that problem and it
also cleans workspace. Maybe it is caused by too many ASF builds doing
the same like we do. I think it might be better to ask ASF Infra to get
in contact with Github and/or Gradle to figure out what can be done.
Uwe
Am 17.05.2025 um 10:47 schrieb Dawid Weiss:
>
> We have workspace cleaning enabled on this job (and possibly other
> jobs). This removes the gradle wrapper on each run. I wonder if we
> need to do it. Alternatively, we could retry with a timeout on 429 in
> the wrapperdownloader.
>
> D.
>
> On Sat, May 17, 2025 at 7:34 AM Apache Jenkins Server
> <je...@builds.apache.org> wrote:
>
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/12808/
>
> No tests ran.
>
> Build Log:
> [...truncated 32 lines...]
> ERROR: Could not download gradle-wrapper.jar (IOException: Server
> returned HTTP response code: 429 for URL:
> https://raw.githubusercontent.com/gradle/gradle/v8.14.0/gradle/wrapper/gradle-wrapper.jar).
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test
> report files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@lucene.apache.org
> For additional commands, e-mail: builds-help@lucene.apache.org
>
--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:uwe@thetaphi.de
Re: [JENKINS] Lucene » Lucene-Check-main - Build # 12808 - Failure!
Posted by Dawid Weiss <da...@gmail.com>.
We have workspace cleaning enabled on this job (and possibly other jobs).
This removes the gradle wrapper on each run. I wonder if we need to do it.
Alternatively, we could retry with a timeout on 429 in the
wrapperdownloader.
D.
On Sat, May 17, 2025 at 7:34 AM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/12808/
>
> No tests ran.
>
> Build Log:
> [...truncated 32 lines...]
> ERROR: Could not download gradle-wrapper.jar (IOException: Server returned
> HTTP response code: 429 for URL:
> https://raw.githubusercontent.com/gradle/gradle/v8.14.0/gradle/wrapper/gradle-wrapper.jar
> ).
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@lucene.apache.org
> For additional commands, e-mail: builds-help@lucene.apache.org
Re: [JENKINS] Lucene » Lucene-Check-main - Build # 12808 - Failure!
Posted by Dawid Weiss <da...@gmail.com>.
We have workspace cleaning enabled on this job (and possibly other jobs).
This removes the gradle wrapper on each run. I wonder if we need to do it.
Alternatively, we could retry with a timeout on 429 in the
wrapperdownloader.
D.
On Sat, May 17, 2025 at 7:34 AM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/12808/
>
> No tests ran.
>
> Build Log:
> [...truncated 32 lines...]
> ERROR: Could not download gradle-wrapper.jar (IOException: Server returned
> HTTP response code: 429 for URL:
> https://raw.githubusercontent.com/gradle/gradle/v8.14.0/gradle/wrapper/gradle-wrapper.jar
> ).
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> ERROR: Step ‘Publish JUnit test result report’ failed: No test report
> files were found. Configuration error?
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: builds-unsubscribe@lucene.apache.org
> For additional commands, e-mail: builds-help@lucene.apache.org