You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Localhost file monitor was taking down the
API server at startup if it can't read the
/etc/resolver directory, which apparently
it can't on CI. Adapted the monitor to log
an error and proceed to file monitoring
which doesn't look like it'll throw.
- Currently we don't collect logs on CI builds,
and we don't have permission to run the log
command there. This PR adds a `--log-root`
parameter for `container system start`,
which gets propagated everywhere via the
`CONTAINER_LOG_ROOT` variable, similarly
to what we do for `--app-root` and `--install-root`.
- Use FilePath from swift-system for the log
root. Foundation URL is a bit of a footgun
for filesystem paths, so unless we identify
a showstopper, we should incrementally
transition to this type everywhere except
where we really need network URLs.
- Set log root for the CI test phase, and
archive/upload logs when tests fail.
- Output the hostname of the CI runner at the
start of the test phase so we can identify
runner-specific issues where they exist.
- Breaking change to CLI output - plumb log
root into container system status, rework
the command for consistency with resource
list/inspect commands (i.e. table and JSON
output), and add a unit test.
- Adds command reference documentation for
`--log-root`.
0 commit comments