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 2024/03/10 17:05:03 UTC
[JENKINS] Lucene » Lucene-Coverage-main - Build # 1065 - Still Failing!
Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/1065/
All tests passed
Build Log:
[...truncated 97716 lines...]
BUILD FAILED in 10m 51s
318 actionable tasks: 318 executed
Publishing build scan...
https://ge.apache.org/s/3a3dhos6frshe
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Archiving artifacts
Recording test results
[Checks API] No suitable checks publisher found.
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Re: [JENKINS] Lucene » Lucene-Coverage-main - Build # 1065 - Still Failing!
Posted by Dawid Weiss <da...@gmail.com>.
I did turn off the security manager for coverage runs, a workaround but
better than none.
On Sun, Mar 10, 2024 at 6:11 PM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/1065/
>
> All tests passed
>
> Build Log:
> [...truncated 97716 lines...]
> BUILD FAILED in 10m 51s
> 318 actionable tasks: 318 executed
>
> Publishing build scan...
> https://ge.apache.org/s/3a3dhos6frshe
>
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> [Checks API] No suitable checks publisher found.
> 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-Coverage-main - Build # 1065 - Still Failing!
Posted by Dawid Weiss <da...@gmail.com>.
I did turn off the security manager for coverage runs, a workaround but
better than none.
On Sun, Mar 10, 2024 at 6:11 PM Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Coverage-main/1065/
>
> All tests passed
>
> Build Log:
> [...truncated 97716 lines...]
> BUILD FAILED in 10m 51s
> 318 actionable tasks: 318 executed
>
> Publishing build scan...
> https://ge.apache.org/s/3a3dhos6frshe
>
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Archiving artifacts
> Recording test results
> [Checks API] No suitable checks publisher found.
> 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