Lines Matching +full:full +full:- +full:custom
5 [0], or the full bcachefs test suite in ktest [1], depending on what's being
7 it for most users; it includes single-command wrappers for all the mainstream
8 in-kernel local filesystems.
12 run by the submitter - but do put some thought into what you're changing and
15 single-command variants for the debug build types you'll most likely need.
32 Instead of running your tests locally, when running the full test suite it's
38 a big tech company, you'll need to help out with server costs to get access -
45 - How will we debug this code? Is there sufficient introspection to diagnose
50 types wired up makes debugging drastically easier - a bit of thoughtful
51 foresight greatly reduces the need to have people build custom kernels with
56 - Does it make the codebase more or less of a mess? Can we also try to do some
59 - Do new tests need to be written? New assertions? How do we know and verify
62 We don't yet have automated code coverage analysis or easy fault injection -
67 in testing is much better than wandering off into undefined behaviour la-la
68 land - use them. Use them judiciously, and not as a replacement for proper
71 - Does it need to be performance tested? Should we add new peformance counters?
78 - If it's a new on disk format feature - have upgrades and downgrades been
94 [0]: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
97 [3]: linux-[email protected]
98 [4]: irc.oftc.net#bcache, #bcachefs-dev