aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/test (unfollow)
Commit message (Collapse)Author
2023-07-11test: add test for segfaulting CI scriptEgor Tensin
The C code leaked out of src/, so I moved .clang-format and some compile options to the root directory. Also, I'm starting to hit test execution limits; I'm going to limit the repositories used for stress testing.
2023-07-11sqlite: make some identifiers more readableEgor Tensin
2023-07-10test: more compact CI scriptsEgor Tensin
2023-07-10test: fix Python freezesEgor Tensin
I would get random freezes when running tests; I completely forgot that logging & multiprocessing don't play well together.
2023-07-10test: code styleEgor Tensin
2023-07-10test: test CI run output containing \0Egor Tensin
2023-07-10test: test long CI run outputEgor Tensin
It immediately exposed a horrible bug in net.c, which is now fixed.
2023-07-09test: prettier test namesEgor Tensin
2023-07-09test: test empty CI run output, refactoringEgor Tensin
Meh, moving the shell code generation to Python I like better in the end.
2023-07-09store process output in SQLiteEgor Tensin
2023-07-09test: attempt to fix random port selection againEgor Tensin
2023-07-09test: print test timingsEgor Tensin
2023-07-09test: increase timeoutsEgor Tensin
All the new added tests require more time.
2023-07-09test: don't wait for hanging processesEgor Tensin
2023-07-09test: fix sqlite3.connect usageEgor Tensin
2023-07-08test: dedupe code by using @parametrizeEgor Tensin
2023-07-08test: refactoringEgor Tensin
2023-07-08test: verify that added runs are in the databaseEgor Tensin
And that they're marked as finished. It immediately exposed some concurrency bugs, so some locking has been fixed.
2023-07-07test: add some basic command-line usage testsEgor Tensin
2023-07-06test: try mitigating port clashesEgor Tensin
Also, I don't think calling random.seed is necessary.
2023-07-06test: add one more stress testEgor Tensin
2023-07-05test: add a 2000-iteration basic repository testEgor Tensin
2023-07-05tcp_server: keep track of client threadsEgor Tensin
This is a major change, obviously; brought to me by Valgrind, which noticed that we don't actually clean up after cimple-client threads. For a more thorough explanation, please see the added comment in tcp_server.c.
2023-07-04storage: mark completed runs as suchEgor Tensin
2023-06-30show git hash with --versionEgor Tensin
Also, use cmake's configure_file to build string constants in.
2023-06-30test: split tests into different filesEgor Tensin
2023-06-29test: shuffle files a bitEgor Tensin
This should hopefully reduce clutter in the test/ directory. Side note: if I leave the __init__.py file in the new py/ directory, pytest fails with import errors. To make it work, I need to either delete it or keep the __init__.py file in both test/ and py/. No idea why.
2023-06-28add .pytest_cache to .gitignoreEgor Tensin
It's added by Pytest automatically, but I like doing it explicitly better.
2023-06-28test: better loggingEgor Tensin
2023-06-28test: skip ci.sh w/ ValgrindEgor Tensin
2023-06-28test/lib: remove non-sensical *Runner classesEgor Tensin
2023-06-28test/lib: refactoringEgor Tensin
2023-06-28test: add test timeouts, prettier outputEgor Tensin
2023-06-28test: add test for actual CI runsEgor Tensin
2023-06-28test/lib: refactoringEgor Tensin
2023-05-15test/lib: refactoringEgor Tensin
2023-05-07test/lib: log process readiness only onceEgor Tensin
2023-05-07test: refactoringEgor Tensin
2023-05-07test: rename CMake testsEgor Tensin
2023-05-07add tests to run binaries under ValgrindEgor Tensin
This was quite a bit of refactoring in test/; everything should be more maintainable and robust in theory. Also, valgrind.sh was fixed to use exec (so that signals are passed to the underlying process); Valgrind command line options have also been tweaked. ./ci.sh fails now, but that should be fixable.
2023-05-06test: mark global fixtures as suchEgor Tensin
2023-05-06add a couple of the most basic tests using PytestEgor Tensin
I'm super-unsure about this; I don't really like all the magic, but we'll see, I guess?