сб, 21 мар. 2020 г. в 14:59, Willy Tarreau <w...@1wt.eu>:

> On Sat, Mar 21, 2020 at 02:51:16PM +0500, ???? ??????? wrote:
> > ??, 21 ???. 2020 ?. ? 14:29, Willy Tarreau <w...@1wt.eu>:
> >
> > > On Sat, Mar 21, 2020 at 02:04:04PM +0500, ???? ??????? wrote:
> > > > how do you call h2spec ?
> > >
> > > Like this (for example):
> > >
> > >   $ h2spec -Svtk -h 127.0.0.1 -p 4443
> > >
> >
> > indeed.   146/146
> >
> > https://github.com/chipitsine/haproxy/runs/523821049
> >
> > ok, I'll try to run it multiple times to figure out how stable it is
>
> Really you *need* to have some response data, not just an empty 200.
> Probably that you can do it with something like this to build 10kB of
> garbage:
>

am I correct, dealing with large blocks is something HPACK related ?
so, for example, if we decide, we can split into several steps, like http2,
HPACK, ...

h2spec can report in junit format. but no CI can import it (well, gitlab-ci
can, but I did not try).
I'd actually prefer to see history test by test (and for reg-tests as well)

the most we can do (and it is relatively cheap) is to define several steps
in github actions.
like, I already done for "build" and "download h2spec", we can define
several steps for h2spec itself.

ok, I'll try it.



>
>    # 40B
>    http-request set-var(req.v)
> str(0123456789.123456789.123456789.123456789)
>    # 160B
>    http-request set-var(req.v)
> var(req.v),concat(,req.v),concat(,req.v),concat(,req.v)
>    # 640B
>    http-request set-var(req.v)
> var(req.v),concat(,req.v),concat(,req.v),concat(,req.v)
>    # 2560B
>    http-request set-var(req.v)
> var(req.v),concat(,req.v),concat(,req.v),concat(,req.v)
>    # 10240B
>    http-request set-var(req.v)
> var(req.v),concat(,req.v),concat(,req.v),concat(,req.v)
>    http-request return status 200 content-type text/plain lf-string
> %[var(req.v)]
>
> Note that I didn't test it, and might have written a bit of crap, but you
> get the idea.
>
> Willy
>

Reply via email to