Okay Job #214 has the arm64 run back close to 11 minutes. On Fri, Jan 10, 2020 at 9:55 AM Mike Rumph <[email protected]> wrote:
> I'm interested in taking a look at this t/apache/expr_string.t testcase > failure. > For example, is it the testcase that is in error or is it the code that > it's testing? > Maybe this can be discussed in a separate thread since it is not exclusive > to arm64. > Has a thread been started on this already? > > Also, it looks like the arm64 job is taking close to 30 minutes. > - https://travis-ci.org/apache/httpd (Job #213) > But we have seen earlier jobs close to 11 minutes. > Has something changed that can explain this? > > On Thu, Jan 9, 2020 at 6:12 AM Joe Orton <[email protected]> wrote: > >> On Thu, Jan 09, 2020 at 03:01:42PM +0100, Luca Toscano wrote: >> > Il giorno gio 9 gen 2020 alle ore 14:19 Joe Orton <[email protected]> >> > ha scritto: >> > > >> > > The caching does work on arm64 so the build & test only takes 11 >> minutes >> > > which is reasonable. >> > > >> > > https://travis-ci.org/apache/httpd/jobs/634661216 >> > > >> > > Looks like this one is the next unreliable test to attack - >> > > >> > > 2425# Failed test 17 in t/apache/expr_string.t at line 87 >> > > 2426# Failed test 20 in t/apache/expr_string.t at line 87 fail #2 >> > > 2427t/apache/expr_string.t .............. >> > > 2428Failed 2/44 subtests >> > > 2429 >> > > >> > > Can anybody reliably reproduce that failure? >> > >> > Does it happen only for ARM or also for other architectures? Never >> > seen this before.. >> >> Definitely all architectures, it's one Rainer reports as failing >> regularly in release testing. Here's another one and I'm pretty sure it >> has shown up in more of the recent failures too - >> >> https://travis-ci.org/apache/httpd/jobs/633442262 >> >>
