[
https://issues.apache.org/jira/browse/LUCENE-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491871#comment-17491871
]
Uwe Schindler commented on LUCENE-10419:
----------------------------------------
When I have seen this in docs, I was thinking about: "is there a use for this
in Lucene's build?"
Generally this helps when you have a resource that is expensive to create or
has limits on parallelization and is used by many tasks. So there could be a
"rat" resource used by all "rat" and "validateSourcePatterns" tasks to get a
new Rat/Matcher instance. The build service would be configured with
parallelization=1, so only one "rat" resource is available for one task at a
time. Gradle then uses this information to schedule tasks, so waiting times by
global locks is reduced (instead of fixing the rat task with a global lock
around the antbuilder code).
That would be my plan to fix this is I get the rat task to fail.... (trying
hard....).
> Identify occasional validateSourcePatterns error on CI servers
> --------------------------------------------------------------
>
> Key: LUCENE-10419
> URL: https://issues.apache.org/jira/browse/LUCENE-10419
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Fix For: 9.1
>
>
> {code}
> What went wrong: Execution failed for task
> ':lucene:analysis:icu:validateSourcePatterns'. > start 1, end 0, length 0
> {code}
>
> This annoys me. It's a message from stringbuilder.substring somewhere - let's
> get the stack of that first and see where the bug is.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
