Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Improved portability of tests | Dan Fandrich | 2010-08-11 | 1 | -1/+3 |
| | | | | | | | | Removed assumptions about umask and locale. Fixed hostname tests to work even when the host has no DNS domain set. Signed-off-by: Dan Fandrich <dan@coneharvesters.com> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com> | ||||
* | randomtest fixes | Denys Vlasenko | 2010-05-12 | 1 | -4/+4 |
| | | | | Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com> | ||||
* | testsuite: fix du testsuite to not use changing directories | Denis Vlasenko | 2008-04-23 | 1 | -1/+1 |
| | |||||
* | egor duda writes: | Eric Andersen | 2004-10-08 | 1 | -2/+3 |
| | | | | | | | | | | | | | | | | | | | | | | | | Hi! I've created a patch to busybox' build system to allow building it in separate tree in a manner similar to kbuild from kernel version 2.6. That is, one runs command like 'make O=/build/some/where/for/specific/target/and/options' and everything is built in this exact directory, provided that it exists. I understand that applyingc such invasive changes during 'release candidates' stage of development is at best unwise. So, i'm currently asking for comments about this patch, starting from whether such thing is needed at all to whether it coded properly. 'make check' should work now, and one make creates Makefile in build directory, so one can run 'make' in build directory after that. One possible caveat is that if we build in some directory other than source one, the source directory should be 'distclean'ed first. egor | ||||
* | Kill off the old 'tests' stuff. Write a ton of new tests for the | Eric Andersen | 2004-04-06 | 1 | -0/+3 |
'testsuite' dir. Fix a bunch of broken tests. Fix the testsuite 'runtest' script so it actually reports all failures and provides meaningful feedback. -Erik |