Summary: | test-unit-file: fails due to assertion | ||
---|---|---|---|
Product: | systemd | Reporter: | Michał Górny <mgorny> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED WONTFIX | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Michał Górny
2013-03-28 10:43:36 UTC
Since http://cgit.freedesktop.org/systemd/systemd/commit/?id=751e757 we return error without dumping core. This is really a misconfiguration in the environment, so a legitimate failure. What's exactly the 'misconfiguration'? Are people expected to run tests as root? (In reply to comment #2) > What's exactly the 'misconfiguration'? Are people expected to run tests as > root? No, people are not expected to have unreadable unit files. systemd will serve their contents over dbus anyway, so it's unlikely that chmod'ding files does what people who do it expect. Well, you could say straight that it fails because file in /etc/systemd is not world-readable. Not that tests which rely on system configuration of *build host* are any good... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.