# Hog all the resources possible
---
-
    request: GET /?resource=cpu
    response:
        status: 503
        content: /Script consumed too much time/
-
    request: GET /?resource=mem
    response:
        status: 503
        content: /Script exited with code 137[.] Used too much memory?/
-
    request: GET /?resource=disk
    response:
        status: 503
        content: /Script consumed too much time/
-
    request: GET /?resource=output
    response:
        content: /Script exceeded maximum response size/
        status: 503

# Hog all the resources possible
---
# -
#     request: GET /?resource=cpu
#     response:
#         status: 503
#         content: /Script consumed too much time/
-
    request: GET /?resource=mem
    response:
        status: 503
        content: /Script exited with code 137[.] Used too much memory?/
# -
#     request: GET /?resource=disk
#     response:
#         status: 503
#         content: /Script consumed too much time/
-
    request: GET /?resource=output
    response:
        content: /Script exceeded maximum response size/
        status: 503

Disable time-sensitive tests for now
Disable time-sensitive tests for now

Now that requests may consume up to 45 seconds, these tests are not
reasonable to execute.  I'd have to increase the test runner HTTP
timeout to 45 seconds for all requests.  That would make all other tests
slower (in the case of failures).

For now, I'm disabling the tests.  Once Hookscript issue #116 has been
completed (the API portion), I can re-enable these tests and use the API
to set a shorter execution timeout.
