We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker@6ce0334bac9f:/experiment$ ./test.sh p17 basename: missing operand Try 'basename --help' for more information. ./test.sh: line 5: [: =: unary operator expected ./symlink.t .. mod_proxy_core_address.c.158: (trace) resolving 127.0.0.1 on port 1026 mod_proxy_core_address.c.63: (trace) adding 127.0.0.1:1026 to the address-pool mod_proxy_core_address.c.158: (trace) resolving 127.0.0.1 on port 1026 mod_proxy_core_address.c.63: (trace) adding 127.0.0.1:1026 to the address-pool 2018-02-07 00:03:27: (server.c.1445) WARNING: unknown config-key: auth.backend.ldap.url (ignored) ./symlink.t .. 1/10 # status failed: expected '200', got '403' # Failed test 'allow: symlinked file' # at ./symlink.t line 56. # status failed: expected '200', got '403' # Failed test 'allow: directly symlinked dir' # at ./symlink.t line 65. # status failed: expected '200', got '403' # Failed test 'allow: symlinked dir in path' # at ./symlink.t line 74. # Looks like you failed 3 tests of 10. ./symlink.t .. Dubious, test returned 3 (wstat 768, 0x300) Failed 3/10 subtests Test Summary Report ------------------- ./symlink.t (Wstat: 768 Tests: 10 Failed: 3) Failed tests: 3-5 Non-zero exit status: 3 Files=1, Tests=10, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.04 cusr 0.00 csys = 0.06 CPU) Result: FAIL Failed 1/1 test programs. 3/10 subtests failed.
Note that identical behaviour is also observed on the reference ManyBugs virtual machine -- this isn't an issue with our Docker container images.
The text was updated successfully, but these errors were encountered:
Fixed broken symlinks. Test suite now produces the expected results!
Sorry, something went wrong.
No branches or pull requests
Note that identical behaviour is also observed on the reference ManyBugs virtual machine -- this isn't an issue with our Docker container images.
The text was updated successfully, but these errors were encountered: