summaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)Author
2015-01-21sysv-generator: Replace Provides: symlinks with real unitsMartin Pitt
Since commit b7e7184 the SysV generator creates symlinks for all "Provides:" in the LSB header. However, this is too greedy; there are cases where the creation of a unit .service file fails because of an already existing symlink with the same name: - Backup files such as /etc/init.d/foo.bak still have "Provides: foo", and thus get a foo.service -> foo.bak.service link. foo.bak would not be enabled in rcN.d/, but we (deliberately) create units for all executables in init.d/ so that a manual "systemctl start" works. If foo.bak is processed before, the symlink already exists. - init.d/bar has "Provides: foo", while there also is a real init.d/foo. The former would create a link foo.service -> bar.service, while the latter would fail to create the real foo.service. If we encounter an existing symlink, just remove it before writing a real unit. Note that two init.d scripts "foo" and "bar" which both provide the same name "common" already work. The first processed init script wins and creates the "common.service" symlink, and the second just fails to create the symlink again. Thus create an additional test case for this to ensure that it keeps working sensibly. https://bugs.debian.org/775404
2015-01-21systemd-sysv-generator test: test scripts with hidden suffixesMartin Pitt
We don't expect any unit generated from temporary package manager, swap, and similar files.
2015-01-21sysv-generator: Handle .sh suffixes when translating Provides:Martin Pitt
When deciding whether the provided name equals the file name in sysv_translate_facility(), also consider them equal if the file name has a ".sh" suffix. This was uncovered by commit b7e7184 which then created a symlink "<name>.service" to itself for ".sh" suffixed init.d scripts. For additional robustness, refuse to create symlinks to itself in add_alias(). Add test case which reproduces the bug. https://bugs.debian.org/775889
2015-01-21systemd-sysv-generator test: fix enabled checkMartin Pitt
Fix hardcoded "foo.service", test for the actual unit parameter.
2015-01-21systemd-sysv-generator test: don't parse symlinksMartin Pitt
Generated services which are symlinks should be tested/handled differently from files, so ignore them in run_generator()'s result parsing.
2015-01-21test: add integration test for systemd-sysv-generatorMartin Pitt
This covers the general functionality as well as regression tests for recent fixes like commits b7e718 and 1ed0c19.
2015-01-20test: eliminate shell wrapper for Python testMartin Pitt
Use the parallel test runner's TEST_EXTENSIONS/*_LOG_COMPILER feature (https://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html) to run *.py tests through $(PYTHON), and only if we have python available/enabled. This eliminates the need of having shell wrappers, thus drop test/rules-test.sh.
2015-01-20test: simplify rules-test.sh wrapperMartin Pitt
Drop globbing of rules/*.rules in the rules-test.sh wrapper and move that logic into the actual test rule-syntax-check.py. This can still be called with individual rules files, but when being called without arguments it will now process all top_builddir/rules/*.rules. Preparation for dropping the shell wrappers altogether.
2015-01-20test: Use configured PythonMartin Pitt
Don't hardcode "python" or /usr/bin/python, but use the configured $(PYTHON).
2015-01-20test/rule-syntax-check.py: Fix for Python 3Martin Pitt
Make this work with both Python 2 and 3.
2014-12-11test-execute: add tests for UMask directiveRonny Chevalier
2014-12-11tests: udev - assume /etc/machine-id rather than /etc/hostsTom Gundersen
On todays machines /etc/hosts is not mandatory. /etc/machine-id is though, so let's rely on that instead. This makes the udev tests pass again for me.
2014-12-10test: fix some tests when running inside a containerJan Synacek
2014-11-26bus-policy: also add in other bus policy tests from dbus1Lennart Poettering
dbus1 only checks if these files parse correctly so let's do the same for now.
2014-11-26bus-policy: steal a test case for prefix ownership from dbus1, and make sure ↵Lennart Poettering
it passes with the bus proxy enforcement
2014-11-26test: add test for crash when adding a JOB_NOPMichal Schmidt
2014-11-13tests: add test-executeRonny Chevalier
add tests for the following directives: - WorkingDirectory - Personality - IgnoreSIGPIPE - PrivateTmp - SystemCallFilter: It makes test/TEST-04-SECCOMP obsolete, so it has been removed. - SystemCallErrorNumber - User - Group - Environment
2014-11-08tests: add test-pathRonny Chevalier
It tests all available directives of Path units: - PathChanged - PathModified - PathExists - PathExisysGlob - DirectoryNotEmpty - MakeDirectory - DirectoryMode - Unit
2014-10-07bus-proxyd: assorted cleanups and fixesDaniel Mack
Just some cleanups around policy checks that came up during review. The code is still not productive.
2014-09-24bus-policy: split API for bus-proxydDaniel Mack
Instead of operating on an sd_bus_message object, expose an API that has 4 functions: policy_check_own() policy_check_hello() policy_check_recv() policy_check_send() This also allows dropping extra code to parse message contents - the bus proxy already has dedicated code paths for that, and we can hook into those later. Tests amended accordingly.
2014-09-20bus-policy: add test utilityDaniel Mack
Add some test files and routines for dbus policy checking.
2014-09-20test: udev - restrict nemuric uid's to existing onesTom Gundersen
We now verify the existence of uid's before applying them to devicenodes, so change the test accordingly. We assume that both uid/gid 1 and 2 exist on the test system.
2014-08-07core: warn when merged units have conflicting dependenciesZbigniew Jędrzejewski-Szmek
A unit should not Conflict with itself. It also does not make much sense for a unit to be After or Before itself, or to trigger itself in some way. If one of those dependency types is encountered, warn, instead of dropping it silently like other dependency types. % build/systemd-analyze verify test/loopy3.service ... Dependency Conflicts dropped when merging unit loopy4.service into loopy3.service Dependency ConflictedBy dropped when merging unit loopy4.service into loopy3.service
2014-08-07core: do not add dependencies to selfZbigniew Jędrzejewski-Szmek
Adds a pair of files which cause a segfault (also with systemd-analyze verify). https://bugzilla.redhat.com/show_bug.cgi?id=1124843
2014-07-20test-engine: fix access to unit load pathZbigniew Jędrzejewski-Szmek
Also add a bit of debugging output to help diagnose problems, add missing units, and simplify cppflags. Move test-engine to normal tests from manual tests, it should now work without destroying the system.
2014-06-10tests: do not use systemctl status --failedRonny Chevalier
since v212 calling systemctl status without arguments will show a overall system state
2014-02-18test: add missing test unitsLennart Poettering
2014-02-14test: add basic seccomp testsRonny Chevalier
2014-02-14test: print the important commands to make debugging easierZbigniew Jędrzejewski-Szmek
2014-02-14test: make the image biggerZbigniew Jędrzejewski-Szmek
I got some errors about lack of disk space... 100MB either way shouldn't matter.
2013-12-10test: wrap $LOOPDEV in quotesZbigniew Jędrzejewski-Szmek
Otherwise things go awry if it is not set ('[ -b ]' is not the same as '[ -b "" ]'!).
2013-12-10test: rework run_qemuRonny Chevalier
It tries to find a suitable QEMU binary and will use KVM if present. We can now configure QEMU from outside with 4 variables : - $QEMU_BIN : path to QEMU's binary - $KERNEL_APPEND : arguments appended to kernel cmdline - $KERNEL_BIN : path to a kernel Default /boot/vmlinuz-$KERNEL_VER - $INITRD : path to an initramfs Default /boot/initramfs-${KERNEL_VER}.img - $QEMU_SMP : number of CPU simulated by QEMU. Default 1 (from Alexander Graf's script: http://www.spinics.net/lists/kvm/msg72389.html)
2013-12-10test: fix TEST-02-CRYPTSETUPRonny Chevalier
missing generate_module_dependencies call which prevents dm_mod and dm_crypt modules to be loaded
2013-11-22cgroups: Cache controller masks and optimize queues.David Strauss
2013-11-07test: remove duplicated codeRonny Chevalier
2013-09-17TEST-03-JOBS/test.sh: do not output the "failed" if it does not existHarald Hoyer
2013-09-17TEST-01-BASIC, TEST-02-CRYPTSETUP: fixed stripHarald Hoyer
also output more status about failed jobs
2013-08-14test: add licence header and switch to LGPLKay Sievers
Checked with and got OK from Martin.
2013-04-24test: make it easier to override kernel versionZbigniew Jędrzejewski-Szmek
2013-04-15Fix spelling errors using 'codespell' toolAnatol Pomozov
2013-02-23test: test irreversible jobsMichal Schmidt
2013-01-29test: some trivial fixes to test scriptsZbigniew Jędrzejewski-Szmek
- fix typo - use compiled systemd-nspawn - drop --capability=... from systemd-nspawn invocation, is is the default now - simplify sudo make invocations
2013-01-28update .gitignoreKay Sievers
2013-01-25test: add test for jobsMichal Schmidt
Add a test case for job merging with --ignore-dependencies. test.sh is copied from TEST-01-*, only lightly modified (this should be refactored better in the future). test-jobs.sh is the core of this test.
2013-01-25test: factor out testsuite.target, end.serviceMichal Schmidt
Tests can use the same testsuite.target. Add end.service to call poweroff instead of doing it from ExecStopPost where it may be skipped on failure of ExecStart.
2013-01-25test: use non-blocking systemctl calls in testsuite.serviceMichal Schmidt
"systemctl poweroff" called from testsuite.service will cause this unit itself to stop. To avoid deadlock, the call must not be synchronous.
2012-12-17licence: remove references to old FSF addressSami Kerola
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=57206
2012-11-15sched: Only setting CPUSchedulingPriority=rr doesn't workHolger Hans Peter Freyther
A service that only sets the scheduling policy to round-robin fails to be started. This is because the cpu_sched_priority is initialized to 0 and is not adjusted when the policy is changed. Clamp the cpu_sched_priority when the scheduler policy is set. Use the current policy to validate the new priority. Change the manual page to state that the given range only applies to the real-time scheduling policies. Add a testcase that verifies this change: $ make test-sched-prio; ./test-sched-prio [test/sched_idle_bad.service:6] CPU scheduling priority is out of range, ignoring: 1 [test/sched_rr_bad.service:7] CPU scheduling priority is out of range, ignoring: 0 [test/sched_rr_bad.service:8] CPU scheduling priority is out of range, ignoring: 100
2012-11-12use the same email address everywhereKay Sievers
2012-10-09udev: fix rule-syntax-check.pyKay Sievers