examine the list of things we can handle, and if not, and we are
looking for strings anyway, convert to string right away.

Really fixes #2205

Fixes #2205.

(url, proto, reason, status etc.) to an empty string.

Fixes #1856

message which either goes into CLI (vcl_init{}) or VSL (all others).

Add a new global counter 'vcl_fail' which counts all VCL_RET_FAIL.

Make use of the ${v*_name} macro and retire redundant redirections.

It turns out some of the tests weren't completely checked.

This reverts commit cca77006.

Sometimes it's not a good idea to fix things before having coffee.

Sometimes it's not a good idea to fix things after midnight.

Suggested by Federico.

While working on libvarnishapi I couldn't get the VUTs to fail on
an INCOMPL() statement, this was caused by the recent changes to
the `shell` command.

The original test was:

    shell -err {
            varnishlog -n ${v1_name} -d -g raw |
            grep "Should not happen"
    }

But it wouldn't catch errors, like for example varnishlog failing to
connect to the shmlog.

Instead of crashing the varnishtest sub-process with an assert,
check that both `vcl.load` and `vcl.use` pass or fail when running
the varnish command for `-vcl` and `-errvcl`. `vcl.use` may fail
the warmup step.

See 9849fd06 for how it was solved.

We also don't want the test to pass if varnishlog failed.

This is an (intentional) regression from 6f9595e6,
but I don't see why we should prevent stringifications of DURATION.

Related to #2101 #2102

we can ditch the bogus return values and some decorations.

Right now this only affects failures in vcl_init{}

it more than once.

which means not in vcl_backend_error{}

Fixes: #1865

with their length.

Explains some of #2117 and friends

I'd really like to come back to https://lists.gt.net/varnish/dev/39240 somewhen.

We should not leave the workspace sizing calculations to the admin based on
incomplete information. The admin should only need to set the "space available
to VCL".