They are also proxy-timeout related it seems: # testing : QUERY_STRING passed OK # expected: qr/QUERY_STRING = horse=trigger\n/s # received: '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> # <html><head> # <title>504 Proxy Error</title> # </head><body> # <h1>Proxy Error</h1> # <p>The gateway did not receive a timely response # from the upstream server or application.</p> # </body></html>' not ok 27 # Failed test 27 in t/modules/rewrite.t at line 85
> On Mar 14, 2016, at 10:03 AM, Ruediger Pluem <rpl...@apache.org> wrote: > > > > On 03/14/2016 02:55 PM, Jim Jagielski wrote: >> >>> On Mar 14, 2016, at 4:48 AM, Ruediger Pluem <rpl...@apache.org> wrote: >>> >>> >>> This seems to cause frequent (no always) failures with test 8 of >>> t/ssl/proxy.t. >>> The request times out with a 504 status. So it looks like the "backend" in >>> this request does not respond. >>> Used MPM is Event, OS CentOS 6 64 Bit. Without further investigating my >>> closeset guess would be that the changes to >>> checkpipeline cause this. >>> >>> >> >> Getting similar behavior on OSX as well. Note sure if you are also >> seeing occasional errors here as well: >> t/modules/rewrite.t ................. 28/29 # Failed test 28 in >> t/modules/rewrite.t at line 88 >> # Failed test 29 in t/modules/rewrite.t at line 90 >> >> Also: >> t/modules/proxy.t ................... 5/18 # Failed test 5 in >> t/modules/proxy.t at line 28 >> # Failed test 6 in t/modules/proxy.t at line 29 >> >> >> >> > > I have not noticed these here. > > Regards > > Rüdiger >
