Actions
Bug #807
closedLoad command: strange behavior with lttng load
Start date:
06/17/2014
Due date:
% Done:
100%
Estimated time:
Description
To reproduce:
- lttng create test
- lttng create test2
- lttng save -a
- lttng destroy -a
- lttng load
Step number 5 should output:
Session has been loaded successfully ( Good behavior so far)
- lttng load
This output:
Error: Failed to load session test2: Session name already exists
Error: Failed to load session test: Session name already exists
Error: Session name already exists
( Still good behaviour)
Let retry one more time:- lttng load
This time we get:
Session has been loaded successfully
Hummm...
let's list the session after we get an error:- lttng load
Error: Failed to load session test2: Session name already exists
Error: Failed to load session test: Session name already exists
Error: Session name already exists
- lttng list
Currently no available tracing session
Seem like we delete the tracing session
Updated by David Goulet over 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset tools|commit:5252df626db3d88190b6fa67d7ee712e4500c4e4.
Actions