09:57 < milian> there is a bug in lttng-analyses when I try to use the timerange arg for e.g. lttng-schedlog: in command.py:627 the second arg passed to parse_trace_collection_time_range is
self_handles, but the argument order for parse_trace_collection_time_range is different
09:57 < milian> collection, time_range, gmt, handles
09:57 < milian> it gets passed: collection, handles, time_range, gmt
09:57 < milian> there is a bug in lttng-analyses when I try to use the timerange arg for e.g. lttng-schedlog: in command.py:627 the second arg passed to parse_trace_collection_time_range is self_handles, but the argument order for parse_trace_collection_time_range is different 09:57 < milian> collection, time_range, gmt, handles 09:57 < milian> it gets passed: collection, handles, time_range, gmt