| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Not used for testing, but still might be useful for development.
|
| |
|
|
| |
Not used for testing, but still might be useful for development.
|
| |
|
|
| |
Not used for testing, but still might be useful for development.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This reworks the cloud metadata mock server in a significant way.
Most importantly this makes it possible for the client to add and
modify the resources for later retrieval using the PUT method.
This allows the test to create the fixture for itself.
The default set of resources is still provided, so that the too remains
useful as a development aid. If that is not desirable, the --empty
parameter might be passed to cause the server to start with no
resources.
|
| |
|
|
|
|
|
|
|
| |
"tools/test-cloud-meta-mock.py""
This changed the fd passing protocol making it not compatible with
systemd-socket-activate(1).
This reverts commit 342ee618c75b350cf5cccf49f2bade85c5dfa3ea.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
"tools/test-cloud-meta-mock.py"
"preexec_fn" is not great, because it is not generally safe in multi
threaded code (and we don't know whether the test didn't start other
threads already, like a GDBus worker thread). Well, it probably is safe,
if you only call async signal safe code, but it's not clear what os.dup2()
does under the hood.
Just avoid that. We can pass on the FD directly.
|
|
|
Useful for testing/development.
|
