Midnight Commander's repository https://midnight-commander.org/

Enrico Weigelt, metux IT service 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
opts 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
.gitignore 39bf54faeb Basic MC testfarm infrastructure 14 years ago
README 39bf54faeb Basic MC testfarm infrastructure 14 years ago
_run_test.sh 39bf54faeb Basic MC testfarm infrastructure 14 years ago
config.sh 91d8e2bb00 Test script specific CFLAGS 14 years ago
git.config 39bf54faeb Basic MC testfarm infrastructure 14 years ago
run-test-1775_mvfs_9P 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
run-test-1775_mvfs_9P_2 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
run-test-1823_prev_line_def 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
run-test-1897_libc_return_values 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
run-test-METUX.approved 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
run-test-METUX.hacking e6800e4303 Test for branch: metux/METUX.hacking 14 years ago
run-test-METUX.mvfs 86e3066f81 Test for branch: metux/METUX.mvfs 14 years ago
run-test-master 229802cbaa Removed obsolete testcase: only-mcserver 14 years ago
update-repo 18abc35a2d optimized update-repo a bit 14 years ago

README

Midnight commander testfarm
----------------------------

CAUTION: ALWAYS run the test under an unprivileged user
where no harm can be done!


1. Generic Setup:

* Check out the branch MC-testfarm
* Adapt config.sh to your needs (probably not necessary)
* Run ./update-repo to download the repo master (which the
individual build workdirs are always copied from)
* Also re-run that script regularily to keep up-to-date

2. How the test-scripts work

* There are several scripts which test different branches
in different option variants (defined in the $TEST variable
within the scripts)
* By convention, there is one test script per branch, named
"run-test-". Within these scripts, the tests to run
(aka option variants) and an ID (used for subdir names) is
defined. The actual dirty work is done by _run_test.sh
* The ./configure options for each variant reside under ./opt
* Output files are found under ./out/$ID/
* Different test scripts can be run parallel, but only one
instance is allowed per individual script
* For each successfully variant an appropriate *.OK file
is put into the ./out/$ID/ subdir.
* These *.OK files prevent that test to be rerun on next
call of the test-script.