I spoke a while ago about working on a multithreaded stress test suite. I have put together some very early details[1]. I would appreciate any feedback.
The goal would be to stress test the C++ dataset API (and soon C++ execution plans and perhaps someday a language independent logical plan / query language). This would happen both through concurrent execution and through injected failure (e.g. filesystem failures). The goal would primarily be the detection of segmentation faults and deadlock. One particular item I could use feedback on is how this gets deployed. In my mind this would be an ongoing test that is continuously running against the previous nightly build. Such a test would quickly consume Apache's GHA minutes so I don't think GHA is an option. Other free CI options probably wouldn't have enough minutes for a continuous daily test (e.g. ~40k minutes). Fortunately, solving this is not a precursor to developing it :). -Weston [1] https://docs.google.com/document/d/1Ozq_TxKvQ7F2XH9Mea_ORefDyKm_EtzRHd948KHCgsg/edit?usp=sharing
