Mailing List Archive

Can we fix timeout exceptions at the bottom of jenkins logs?
Hi Koji,

Sorry for addressing you directly here, I thought you may know off the top
of your head... :)

In many Jenkins builds we have an exception and stack trace at the bottom
of the build. Like this one:

BUILD SUCCESSFUL in 4h 19m 45s
195 actionable tasks: 195 executed
Build step 'Invoke Gradle script' changed build result to SUCCESS
Archiving artifacts
java.lang.InterruptedException: no matches found within 10000
at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
...
No artifacts found that match the file pattern
"**/*.events,heapdumps/**,**/hs_err_pid*". Configuration error?

I looked at the code and see this is configurable via system properties -

https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound

Can we increase this limit per build or somehow on Apache build servers
(and on Uwe's machine)? It's mildly annoying to see those stack traces in
e-mails. I don't think this is configurable in per-job plugin settings [1].

Dawid

[1] Screenshot of the config of the archiving plugin.

[image: image.png]
RE: Can we fix timeout exceptions at the bottom of jenkins logs? [ In reply to ]
Hi,



I am not sure if we may be able to optimize the patterns, but unfortunately it needs to scan thorugh whole directory tree to find hs_err_pid files, which should be archived for later investigation.



Maybe we should open an issue on Jenkins to just omit printing a stack trace for this error. This is the main problem with it.



Uwe



-----

Uwe Schindler

Achterdiek 19, D-28357 Bremen

https://www.thetaphi.de

eMail: uwe@thetaphi.de



From: Dawid Weiss <dawid.weiss@gmail.com>
Sent: Thursday, December 9, 2021 9:50 AM
To: Lucene Dev <dev@lucene.apache.org>
Cc: Koji Sekiguchi <koji.sekiguchi@rondhuit.com>; Uwe Schindler (SD DataSolutions GmbH) <uwe@thetaphi.de>
Subject: Can we fix timeout exceptions at the bottom of jenkins logs?





Hi Koji,



Sorry for addressing you directly here, I thought you may know off the top of your head... :)



In many Jenkins builds we have an exception and stack trace at the bottom of the build. Like this one:



BUILD SUCCESSFUL in 4h 19m 45s
195 actionable tasks: 195 executed
Build step 'Invoke Gradle script' changed build result to SUCCESS
Archiving artifacts
java.lang.InterruptedException: no matches found within 10000
at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
...

No artifacts found that match the file pattern "**/*.events,heapdumps/**,**/hs_err_pid*". Configuration error?



I looked at the code and see this is configurable via system properties -



https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound



Can we increase this limit per build or somehow on Apache build servers (and on Uwe's machine)? It's mildly annoying to see those stack traces in e-mails. I don't think this is configurable in per-job plugin settings [1].



Dawid



[1] Screenshot of the config of the archiving plugin.
Re: Can we fix timeout exceptions at the bottom of jenkins logs? [ In reply to ]
> Maybe we should open an issue on Jenkins to just omit printing a stack
> trace for this error. This is the main problem with it.
>

If it prints a stack trace it means it hasn't finished though? So it's not
doing the job it was set up to do. I think we should increase the limit or
maybe make the patterns more specific so that not so many entries are
scanned? It looks fishy to me the way it is right now.

D.


>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> https://www.thetaphi.de
>
> eMail: uwe@thetaphi.de
>
>
>
> *From:* Dawid Weiss <dawid.weiss@gmail.com>
> *Sent:* Thursday, December 9, 2021 9:50 AM
> *To:* Lucene Dev <dev@lucene.apache.org>
> *Cc:* Koji Sekiguchi <koji.sekiguchi@rondhuit.com>; Uwe Schindler (SD
> DataSolutions GmbH) <uwe@thetaphi.de>
> *Subject:* Can we fix timeout exceptions at the bottom of jenkins logs?
>
>
>
>
>
> Hi Koji,
>
>
>
> Sorry for addressing you directly here, I thought you may know off the top
> of your head... :)
>
>
>
> In many Jenkins builds we have an exception and stack trace at the bottom
> of the build. Like this one:
>
>
>
> BUILD SUCCESSFUL in 4h 19m 45s
> 195 actionable tasks: 195 executed
> Build step 'Invoke Gradle script' changed build result to SUCCESS
> Archiving artifacts
> java.lang.InterruptedException: no matches found within 10000
> at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
> ...
>
> No artifacts found that match the file pattern
> "**/*.events,heapdumps/**,**/hs_err_pid*". Configuration error?
>
>
>
> I looked at the code and see this is configurable via system properties -
>
>
>
>
> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
>
>
>
> Can we increase this limit per build or somehow on Apache build servers
> (and on Uwe's machine)? It's mildly annoying to see those stack traces in
> e-mails. I don't think this is configurable in per-job plugin settings [1].
>
>
>
> Dawid
>
>
>
> [1] Screenshot of the config of the archiving plugin.
>
>
>
>
Re: Can we fix timeout exceptions at the bottom of jenkins logs? [ In reply to ]
Hi Dawid,

I think I'm not the right person to be asked. I'm sorry for being not useful on this...

Koji

On 2021/12/09 17:50, Dawid Weiss wrote:
>
> Hi Koji,
>
> Sorry for addressing you directly here, I thought you may know off the top of your head... :)
>
> In many Jenkins builds we have an exception and stack trace at the bottom of the build. Like this one:
>
> BUILD SUCCESSFUL in 4h 19m 45s
> 195 actionable tasks: 195 executed
> Build step 'Invoke Gradle script' changed build result to SUCCESS
> Archiving artifacts
> java.lang.InterruptedException: no matches found within 10000
>         at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
> ...
> No artifacts found that match the file pattern "**/*.events,heapdumps/**,**/hs_err_pid*".
> Configuration error?
>
> I looked at the code and see this is configurable via system properties -
>
> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
> <https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound>
>
> Can we increase this limit per build or somehow on Apache build servers (and on Uwe's machine)? It's
> mildly annoying to see those stack traces in e-mails. I don't think this is configurable in per-job
> plugin settings [1].
>
> Dawid
>
> [1] Screenshot of the config of the archiving plugin.
>
> image.png

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Can we fix timeout exceptions at the bottom of jenkins logs? [ In reply to ]
No worries, thanks!

On Fri, Dec 10, 2021 at 1:45 AM Koji Sekiguchi <koji.sekiguchi@rondhuit.com>
wrote:

> Hi Dawid,
>
> I think I'm not the right person to be asked. I'm sorry for being not
> useful on this...
>
> Koji
>
> On 2021/12/09 17:50, Dawid Weiss wrote:
> >
> > Hi Koji,
> >
> > Sorry for addressing you directly here, I thought you may know off the
> top of your head... :)
> >
> > In many Jenkins builds we have an exception and stack trace at the
> bottom of the build. Like this one:
> >
> > BUILD SUCCESSFUL in 4h 19m 45s
> > 195 actionable tasks: 195 executed
> > Build step 'Invoke Gradle script' changed build result to SUCCESS
> > Archiving artifacts
> > java.lang.InterruptedException: no matches found within 10000
> > at
> hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
> > ...
> > No artifacts found that match the file pattern
> "**/*.events,heapdumps/**,**/hs_err_pid*".
> > Configuration error?
> >
> > I looked at the code and see this is configurable via system properties -
> >
> >
> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
> > <
> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
> >
> >
> > Can we increase this limit per build or somehow on Apache build servers
> (and on Uwe's machine)? It's
> > mildly annoying to see those stack traces in e-mails. I don't think this
> is configurable in per-job
> > plugin settings [1].
> >
> > Dawid
> >
> > [1] Screenshot of the config of the archiving plugin.
> >
> > image.png
>
Re: Can we fix timeout exceptions at the bottom of jenkins logs? [ In reply to ]
Dawid,

Maybe you meant https://en.wikipedia.org/wiki/Kohsuke_Kawaguchi ?

Mark

On Fri, 10 Dec 2021 at 09:42, Dawid Weiss <dawid.weiss@gmail.com> wrote:

>
> No worries, thanks!
>
> On Fri, Dec 10, 2021 at 1:45 AM Koji Sekiguchi <
> koji.sekiguchi@rondhuit.com> wrote:
>
>> Hi Dawid,
>>
>> I think I'm not the right person to be asked. I'm sorry for being not
>> useful on this...
>>
>> Koji
>>
>> On 2021/12/09 17:50, Dawid Weiss wrote:
>> >
>> > Hi Koji,
>> >
>> > Sorry for addressing you directly here, I thought you may know off the
>> top of your head... :)
>> >
>> > In many Jenkins builds we have an exception and stack trace at the
>> bottom of the build. Like this one:
>> >
>> > BUILD SUCCESSFUL in 4h 19m 45s
>> > 195 actionable tasks: 195 executed
>> > Build step 'Invoke Gradle script' changed build result to SUCCESS
>> > Archiving artifacts
>> > java.lang.InterruptedException: no matches found within 10000
>> > at
>> hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
>> > ...
>> > No artifacts found that match the file pattern
>> "**/*.events,heapdumps/**,**/hs_err_pid*".
>> > Configuration error?
>> >
>> > I looked at the code and see this is configurable via system properties
>> -
>> >
>> >
>> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
>> > <
>> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
>> >
>> >
>> > Can we increase this limit per build or somehow on Apache build servers
>> (and on Uwe's machine)? It's
>> > mildly annoying to see those stack traces in e-mails. I don't think
>> this is configurable in per-job
>> > plugin settings [1].
>> >
>> > Dawid
>> >
>> > [1] Screenshot of the config of the archiving plugin.
>> >
>> > image.png
>>
>
Re: Can we fix timeout exceptions at the bottom of jenkins logs? [ In reply to ]
Oh... [Red-faced]. Of course, right. I am struggling through covid right
now so I guess there are mental side-effects of that as well - hazy head...
Sorry for confusion (and I apologize
for calling out your name in the wrong context, Koji).

Dawid





On Fri, Dec 10, 2021 at 9:16 AM Mark Jens <mark.r.jens@gmail.com> wrote:

> Dawid,
>
> Maybe you meant https://en.wikipedia.org/wiki/Kohsuke_Kawaguchi ?
>
> Mark
>
> On Fri, 10 Dec 2021 at 09:42, Dawid Weiss <dawid.weiss@gmail.com> wrote:
>
>>
>> No worries, thanks!
>>
>> On Fri, Dec 10, 2021 at 1:45 AM Koji Sekiguchi <
>> koji.sekiguchi@rondhuit.com> wrote:
>>
>>> Hi Dawid,
>>>
>>> I think I'm not the right person to be asked. I'm sorry for being not
>>> useful on this...
>>>
>>> Koji
>>>
>>> On 2021/12/09 17:50, Dawid Weiss wrote:
>>> >
>>> > Hi Koji,
>>> >
>>> > Sorry for addressing you directly here, I thought you may know off the
>>> top of your head... :)
>>> >
>>> > In many Jenkins builds we have an exception and stack trace at the
>>> bottom of the build. Like this one:
>>> >
>>> > BUILD SUCCESSFUL in 4h 19m 45s
>>> > 195 actionable tasks: 195 executed
>>> > Build step 'Invoke Gradle script' changed build result to SUCCESS
>>> > Archiving artifacts
>>> > java.lang.InterruptedException: no matches found within 10000
>>> > at
>>> hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:3069)
>>> > ...
>>> > No artifacts found that match the file pattern
>>> "**/*.events,heapdumps/**,**/hs_err_pid*".
>>> > Configuration error?
>>> >
>>> > I looked at the code and see this is configurable via system
>>> properties -
>>> >
>>> >
>>> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
>>> > <
>>> https://www.jenkins.io/doc/book/managing/system-properties/#hudson-filepath-validate_ant_file_mask_bound
>>> >
>>> >
>>> > Can we increase this limit per build or somehow on Apache build
>>> servers (and on Uwe's machine)? It's
>>> > mildly annoying to see those stack traces in e-mails. I don't think
>>> this is configurable in per-job
>>> > plugin settings [1].
>>> >
>>> > Dawid
>>> >
>>> > [1] Screenshot of the config of the archiving plugin.
>>> >
>>> > image.png
>>>
>>