h2spec tracking (80 passed, 14 failed)

[fasterthanlime]

Ran h2spec today, with:

$ just h2spec-server
(cut)
Listening on [::]:8888

h2spec -p 8888 -o 1
(cut)
Finished in 49.2419 seconds
146 tests, 70 passed, 1 skipped, 75 failed

Even with a super naive implementation that fails to check for a lot of preconditions / stubs large parts of the spec, we're already off to a good start!

[fasterthanlime]

I'm gonna update this comment with the latest results:

2023-01-21:

Finished in 43.2143 seconds
146 tests, 103 passed, 1 skipped, 42 failed

(What's neat is that, as tests get fixed, the suite gets faster, since most failures do a 1-second timeout)

edit: The test results are now tracked in CI, I'm editing the issue title now and then.

[fasterthanlime]

Reports are now split, we're at:

• http2: 59 passed, 34 failed, 1 skipped
• hpack: 6 passed, 2 failed
• generic: 44 passed

[fasterthanlime]

Since generic and hpack all pass, I'm going to edit the title of this issue to reflect just the http2 suite.

[fasterthanlime]

Updated today, somehow we went from 67 passed to 72 passed, which is surprising because I don't remember specifically working on making more tests pass (I was about to)! but oh well.

The failing tests can be seen here: https://github.com/hapsoc/fluke/runs/17335784679 (until the artifact expires I guess)

[fasterthanlime]

The number of passing tests has regressed after refactorings, but that should be short-lived.

[fasterthanlime]

The number of passing tests has regressed after refactorings, but that should be short-lived.

Yup, just bumped from 62 to 79, which is 6 better than before the refactor :)

Still some low-hanging fruits, the next big task after that is flow control, but due to the refactor, this should be nice and lock-free.

[fasterthanlime]

Closing in favor of #175.