cimple - My little CI system (hopefully)

	Commit message (Collapse)	Author	Age
*	flame_graph.sh -> flamegraph.sh	Egor Tensin	2023-07-18
\| \| \| \|	Inspired by flamegraph.pl.
*	test: minor refactoring	Egor Tensin	2023-07-18
\|
*	test: exclude silly tests from python_tests_valgrind	Egor Tensin	2023-07-18
\|
*	test: speed up output_long test_repo tests	Egor Tensin	2023-07-18
\|
*	implement flame graph generation	Egor Tensin	2023-07-18
\|
*	process: preserve the exit code more	Egor Tensin	2023-07-18
\| \| \| \| \|	If the process is killed by a signal, preserve the exit code as it would be reported by $?.
*	switch to JSON-RPC as message format	Egor Tensin	2023-07-18
\| \| \| \| \| \|	Instead of the weird `struct msg` I had, I switched to the JSON-RPC format. It's basically the same, but has a well-defined semantics in case of errors.
*	test: move some code to lib/	Egor Tensin	2023-07-12
\|
*	test: use namedtuple where appropriate	Egor Tensin	2023-07-12
\|
*	test: add test for segfaulting CI script	Egor Tensin	2023-07-11
\| \| \| \| \| \| \| \|	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.
*	sqlite: make some identifiers more readable	Egor Tensin	2023-07-11
\|
*	test: more compact CI scripts	Egor Tensin	2023-07-10
\|
*	test: fix Python freezes	Egor Tensin	2023-07-10
\| \| \| \| \|	I would get random freezes when running tests; I completely forgot that logging & multiprocessing don't play well together.
*	test: code style	Egor Tensin	2023-07-10
\|
*	test: test CI run output containing \0	Egor Tensin	2023-07-10
\|
*	test: test long CI run output	Egor Tensin	2023-07-10
\| \| \| \|	It immediately exposed a horrible bug in net.c, which is now fixed.
*	test: prettier test names	Egor Tensin	2023-07-09
\|
*	test: test empty CI run output, refactoring	Egor Tensin	2023-07-09
\| \| \| \| \|	Meh, moving the shell code generation to Python I like better in the end.
*	store process output in SQLite	Egor Tensin	2023-07-09
\|
*	test: attempt to fix random port selection again	Egor Tensin	2023-07-09
\|
*	test: increase timeouts	Egor Tensin	2023-07-09
\| \| \| \|	All the new added tests require more time.
*	test: don't wait for hanging processes	Egor Tensin	2023-07-09
\|
*	test: fix sqlite3.connect usage	Egor Tensin	2023-07-09
\|
*	test: dedupe code by using @parametrize	Egor Tensin	2023-07-08
\|
*	test: refactoring	Egor Tensin	2023-07-08
\|
*	test: verify that added runs are in the database	Egor Tensin	2023-07-08
\| \| \| \| \|	And that they're marked as finished. It immediately exposed some concurrency bugs, so some locking has been fixed.
*	test: add some basic command-line usage tests	Egor Tensin	2023-07-07
\|
*	test: try mitigating port clashes	Egor Tensin	2023-07-06
\| \| \| \|	Also, I don't think calling random.seed is necessary.
*	test: add one more stress test	Egor Tensin	2023-07-06
\|
*	test: add a 2000-iteration basic repository test	Egor Tensin	2023-07-05
\|
*	storage: mark completed runs as such	Egor Tensin	2023-07-04
\|
*	show git hash with --version	Egor Tensin	2023-06-30
\| \| \| \|	Also, use cmake's configure_file to build string constants in.
*	test: split tests into different files	Egor Tensin	2023-06-30
\|
*	test: shuffle files a bit	Egor Tensin	2023-06-29
	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.