Commits
- Commit:
12866f1911ebefc40cf4f988cd59d620e8b50a96
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add targets to serve the site locally
- Commit:
ae6870fa3bf25561a3f6bd8465ba86307af5d5bb
- From:
- Omar Polo <op@omarpolo.com>
- Date:
import the capsule/website
- Commit:
568419b2c1f71620095acd9bf3be6aaa2bbe43ee
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add .cirrus.yml
Add a cirrus CI config file that runs the regression suite on linux
amd64/aarch64 and on freebsd.
- Commit:
6e0f14d51ef1971893bb094c873ddde86d0cae61
- From:
- Omar Polo <op@omarpolo.com>
- Date:
re-add sha script; it's used in the Makefile
While there, use it in the tests too
- Commit:
2072343d6ba88a37ede0c4ae2791328880cdfacf
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync changelog
- Commit:
260becda9c69d5c76ae8a0bdbc6f98781b615534
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reduced the timeout time for single checks
- Commit:
d046e4d6b500583cda8d2561e47c790eaedd007f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
copy only `len' bytes, not the whole buffer
We ended up copying too much data from the fastcgi process.
- Commit:
4a2a525d7c3013f3c4b5669db9fdbb84d8d77946
- From:
- Omar Polo <op@omarpolo.com>
- Date:
allow running only specific tests
It's now possible to run only a subset of the tests with:
./runtime test1 test2 ...
- Commit:
c1272f63e4b85f663b56a8e67e31f3e85dd78faa
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync
- Commit:
99c91b4a51fea49255b5e6989278f6b9990d0a5c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
remove unused script
- Commit:
176179b2a9e99af595892c396a219c2bc11fb6c9
- From:
- Omar Polo <op@omarpolo.com>
- Date:
rework the regression suite
The tests are still there, the suite is equivalent to the old one, but
this one is better structured.
The biggest annoyance I had with the old one was that it wasn't
straightforward to test only a specific set of tests. It's still
impossible, but it's way easier to do it now.
This extract all the tests to their own functions. It's overall
better in all possible regards.
- Commit:
c28994868efd1da6259f805984cc93135bd74a3a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
update clean target
- Commit:
a49800c86aeceddedd1b876a125276f9e8ff0baa
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync
- Commit:
acafce5b7ddd4342e45a7731ae3f261e6f202a77
- From:
- Omar Polo <op@omarpolo.com>
- Date:
libevent2 fix: unfreeze the client evbuffer
libevent2 has this concept of "freezeness" of a buffer. It's a way to
avoid accidentally write/remove data from the wrong "edge" of the
buffer. The client_tls_{read,write} functions need to add/drain data
from the opposite edge, hence the need for the unfreeze call.
This is the minimum change in order to work on libevent2 too. Another
way would be to define evbuffer_{un,}freeze as NOP on libevent 1, but
it's ugly IMHO.
- Commit:
efb6210d7745c9466ab9a16f23d1549523428ef7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
improve libevent2 handling
* add configure check
* change the way the headers are required (copied from tmux)