Abort check-examples target if phantomjs takes too long to run examples.

[twpayne]

Currently a WMS server (http://demo.opengeo.org/geoserver) seems to be down, which results in a neverending integration-test target:

2013-03-12 09:13:12,232 check-examples: phantomjs bin/check-example.js build/gh-pages/unselectable-css-const/examples/wms-single-image.html?mode=raw

We should probably abort phantomjs after a certain amount of time has passed.

[marcjansen]

Fine as a workaround. Actually all external resources might break this target, right?

This is good to be merged, though. Maybe we come up with s.th. more clever in the future. Thanks for tackling this, @twpayne.

[ahocevar]

I think one of the goals of this build target should be to detect external resources that are down, to give developers a chance to change them to other resources that are up. So I'm not so sure if we really want to be more lenient about errors with external resources. Instead of @twpayne's workaround, I'd rather see us change the examples that rely on resources that are down to ones that are up. Pull request to come.

[elemoine]

@ahocevar, that makes sense. Thanks.

[twpayne]

I agree that #360 is a better solution.