Re: flaky HTTP2 test

2020-06-25 Thread Raymond Auge
;>> On Wed, Jun 24, 2020 at 11:35 AM Eduardo Quintanilla < >>> equintani...@bnext.mx> wrote: >>> >>>> The link does not work. >>>> >>>> HTTP Status: 400 >>>> Response: {"count":11,"value":"Uri expir

Re: flaky HTTP2 test

2020-06-25 Thread Rémy Maucherat
gt; >> - Ray >> >> On Wed, Jun 24, 2020 at 11:35 AM Eduardo Quintanilla < >> equintani...@bnext.mx> wrote: >> >>> The link does not work. >>> >>> HTTP Status: 400 >>> Response: {"count":11,"value":"Uri

Re: flaky HTTP2 test

2020-06-24 Thread Raymond Auge
o Quintanilla < > equintani...@bnext.mx> wrote: > >> The link does not work. >> >> HTTP Status: 400 >> Response: {"count":11,"value":"Uri expired"} >> >> Eduardo Quintanilla >> Software Developer >> >> From: R

Re: flaky HTTP2 test

2020-06-24 Thread Raymond Auge
{"count":11,"value":"Uri expired"} > > Eduardo Quintanilla > Software Developer > > From: Raymond Auge > Sent: miércoles, 24 de junio de 2020 10:29 a. m. > To: Tomcat Developers List > Subject: Re: flaky HTTP2 test > > You'll not

RE: flaky HTTP2 test

2020-06-24 Thread Eduardo Quintanilla
The link does not work. HTTP Status: 400 Response: {"count":11,"value":"Uri expired"} Eduardo Quintanilla Software Developer From: Raymond Auge Sent: miércoles, 24 de junio de 2020 10:29 a. m. To: Tomcat Developers List Subject: Re: flaky HTTP2 test You'

Re: flaky HTTP2 test

2020-06-24 Thread Raymond Auge
You'll notice that in the same run that test passed on JDK 14 and 15-ea. - Ray On Wed, Jun 24, 2020 at 11:26 AM Raymond Auge wrote: > See >

Re: flaky HTTP2 test

2020-06-24 Thread Raymond Auge
See https://pipelines.actions.githubusercontent.com/hQhYuytC86T1GsTs7qTvThq2ESqStTSskvOzwdA12PGOh7ZWVy/_apis/pipelines/1/runs/14/signedlogcontent/7?urlExpires=2020-06-24T15%3A25%3A51.1449322Z=HMACV1=O2PyO3WhK3FTDVz3t1sTeAGHP7IOlnynp8PZIfw%2BsOQ%3D and search for "Running

Re: flaky HTTP2 test

2020-06-24 Thread Mark Thomas
On 24/06/2020 15:56, Raymond Auge wrote: > Hey all, > > The test > org.apache.coyote.http2.TestHttp2Limits > seems to be flaky. Haven't seen any issues with it recently either locally or with on of the other CI systems. Do you have a log from a failure case? Mark > > I'm playing with github