agent: Display trace details#505
Conversation
|
/test |
|
@chavafg - the opensuse CI has fallen over with a Java exception - looks like |
|
/retest |
Log the trace mode and type when tracing is enabled. The change makes it clearer that static tracing is enabled when the agent parsers the kernel command line (`config.go`) and dynamic tracing is enabled by gRPC (`grpc.go`). Specifics of change: - Rename variables to match the terms defined in `TRACING.md`. - Pass trace mode and trace type arguments to `enableTracing()`. - Change the tense of the message displayed by `enableTracing()` so that the message indicates that tracing *is* enabled, not *about to be*. Fixes kata-containers#504. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
231e21f to
2ada1d1
Compare
|
Ping @kata-containers/agent. /retest |
|
CI 18.04 failed with a net/quay error - I'll nudge that one, and we'll see if that clears. I've not looked at the other fails (I'm just going to presume they are similar for now). |
|
Looks like something got wedged upstream: |
|
/me puts a coin in the slot and re-cranks... |
|
/test |
|
Power CI failing with a weird message: /cc @nitkon |
|
@jodh-intel : Cleared the workspace and reran the CI. Now It is failing because of Edit: |
|
Thanks @nitkon. Hmm, could that be because of this... |
|
@nitkon - can you possibly raise an issue for the ppc64 issue? I'm going to merge this as that's the only failure which is unrelated to this change... |
Log the trace mode and type when tracing is enabled. The change makes it clearer that static tracing is enabled when the agent parsers the kernel command line (
config.go) and dynamic tracing is enabled by gRPC (grpc.go).Specifics of change:
TRACING.md.enableTracing().enableTracing()so that the message indicates that tracing is enabled, not about to be.Fixes #504.
Signed-off-by: James O. D. Hunt james.o.hunt@intel.com