travis failing

[Jeff Kaufman]

Every travis build since yesterday has been failing with the same
error after ~30min:

TEST: But do proxy content if the Content-Type header is present.
check_from fgrep -q 200 OK
FAILed Input: HTTP/1.1 403 Forbidden

Date: Tue, 10 Jan 2017 15:34:09 GMT

Server: Apache/2.2.22 (Ubuntu)

Cache-Control: max-age=0, no-cache

Vary: Accept-Encoding

Content-Length: 50

Content-Type: text/html



Missing Content-Type required for proxied resource
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test_helpers.sh:445:
check_from
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/apache/system_tests/proxying.sh:54:
source
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test_helpers.sh:249:
run_test_helper
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/automatic/system_test_helpers.sh:226:
run_test
/home/travis/build/pagespeed/mod_pagespeed/pagespeed/apache/system_test.sh:178:
main
failure at line 54
in 'But do proxy content if the Content-Type header is present.'
FAIL.
make[1]: *** [apache_debug_smoke_test] Error 1

I'm pretty sure this is due to some change in the Travis environment,
since the first change to hit this error [1] can't be causing it.

Jeff

[1] https://github.com/pagespeed/mod_pagespeed/pull/1472

[Jeff Kaufman]

Actually, the problem was that modpagespeed.com wasn't serving the
test files on ports 8091 and 8092. I logged into modpagespeed.com,
killed the existing serve_proxying_tests and nc processes, and ran
~/serve_proxying_tests.sh under screen. Then I verified that it was
working:

$ curl -D- modpagespeed.com:8091
HTTP/1.1 200 OK
Content-Type: text/plain

This file should be proxied.
$ curl -D- modpagespeed.com:8092
HTTP/1.1 200 OK

This file should not be proxyied.

I suspect our tests will pass now.

Jeff

[Jeff Kaufman]

And the build is green again:
https://travis-ci.org/pagespeed/mod_pagespeed/builds/191058458