Closes #3692

Use of SML is supported by the storage API though the sml_* function
pointers.

Yet, like struct object, struct storage is part of the simple storage
(sml) implementation and does not belong to the storage API. Storage
not using SML (that is, code which does not include storage_simple.h)
should not be concerned with struct storage.

Even thought the first rxresp implies that the backend fetch must have
completed, it is still possible to observe a streaming hit.

Since resp.is_streaming merely looks at the presence of a boc, and not
whether its state is lower than FINISHED, waiting until we see the fetch
end in the logs and forcing a new client session should reduce the race
window in those test cases.

We could also try to settle on the value of resp.is_streaming when we
hit an object in the cache or resume from a backend fetch and change the
semantic to whether resp was streaming when VCL entered the subroutine.

By that I mean, with a proper check of the boc state.

Refs 02ada45c

Spotted by oss-fuzz.

This to silence errors on OSX where apparently int64_t isn't type
equivalent to intmax_t, causing printf-errors when using %jd.

Fixes: #3699

My bad.

fixes #3697

Going back to pretending 32bit bionic builds are fine until #3702 is
sorted out. We have 32bit coverage in our vtest CI anyway.

Reverts f8974400
Reverts c5ed00b6

Fixes: #3688

While at it, try to better formalize all the setup steps.

It operates on a pointer like FREE_OBJ() and clears it.

It turns out, in addition to beeing enclosed inside sh -c '...' the
CFLAGS may also be nested inside "double" quotes.

Otherwise they interfere with the surrounding sh -c '...' command.

It's still a static library, but the build is slightly more uniform.

It's still a static library, but the build is slightly more uniform.

It has been deprecated long enough and could have gone away with the 7.0
release.

Refs 7a85739b

It has been deprecated long enough and could have gone away with the 7.0
release.

Refs 3fb17e94

To avoid trailing blanks in diffs I decided to use underscores.

In curses test cases, pack process writes with the following
expectations.

Refs #3691

Forgot to pass -i for inplace sed run

fixes #3698

Add the necessary bits to the master CCI configuration to make the package
building parts also work in the release branches. This way there is no
need to tailor the release branches' CCI setup on release day.

This should not (famous last words) change how the weekly packages from
the master branch are generated.

Releasing 7.0.0

Refs 33ffbbc5

Refs 33ffbbc5

Or when the -p option is used.

Fixes #3687

and sort options alphabetically while being at it.

Relates to ##3687

Spotted by @Algunenano.