Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

test: fix TestSocketActivation on systemd-v219 #1768

Merged
merged 1 commit into from Nov 23, 2015

Conversation

alban
Copy link
Member

@alban alban commented Nov 19, 2015

Fixes #1739

@alban
Copy link
Member Author

alban commented Nov 23, 2015

rebased.

@@ -86,9 +86,14 @@ func TestSocketActivation(t *testing.T) {

rnd := r.Int()

// Write unit files directly to /run/systemd/system because systemd-v219 does
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is a bit confusing. I would write something like:

Write unit files directly to runtime system units directory (/run/systemd/system) to avoid calling LinkUnitFiles - it is buggy in systemd v219 as it does not work with absolute paths.

@krnowak
Copy link
Collaborator

krnowak commented Nov 23, 2015

I'm not fond of cluttering host directories with our testing stuff, but we were interacting with host systemd anyway.

One nit, otherwise LFAD.

@alban alban force-pushed the alban/test-socket-activation branch from 358222b to 3c8b762 Compare November 23, 2015 13:30
@alban
Copy link
Member Author

alban commented Nov 23, 2015

@krnowak Thanks. Updated.

krnowak added a commit that referenced this pull request Nov 23, 2015
test: fix TestSocketActivation on systemd-v219
@krnowak krnowak merged commit 6b38e13 into rkt:master Nov 23, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants