This repository has been archived by the owner on May 12, 2021. It is now read-only.
Runtime tracing broken #1277
Assignees
Labels
medium-priority
Urgent issue (resolve before unprioritised issues)
release-gating
Release must wait for this to be resolved before release
Comments
jodh-intel
added
medium-priority
This was referenced Feb 25, 2019
jodh-intel
added a commit
to jodh-intel/runtimes
that referenced
this issue
Mar 4, 2019
The store refactor (kata-containers#1066) inadvertently broke runtime tracing as it created new contexts containing trace spans. Reworking the store changes to re-use the existing context resolves the problem since runtime tracing assumes a single context. Fixes kata-containers#1277. Signed-off-by: James O. D. Hunt <[email protected]>
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Setting
enable_tracing=trueinconfiguration.tomlisn't behaving as expected - I'm seeing lots of load/store operations in the trace but nothing else.Could be related to the recent #1066.
The text was updated successfully, but these errors were encountered: