Open tdresser opened 6 years ago
@deepanjanroy
Can you provide more detail? What OS[s] does this happen on? Which metrics? Does it happen reliably for any particular traces?
Sorry, that was a terrible bug report.
This is when I write code which is legitimately broken, during metric computation. Instead of dumping the error to stdout, run_metric just silently dies.
This specific example was withing constructLoadingExpectation_.
There's a try-catch in UserModelBuilder that converts exceptions to model.importWarnings so that old traces can be imported. Maybe map_single_trace_cmdline.html should print importWarnings after importing the trace? @eakuefner
Ben and I talked about this offline -- definitely printing import warnings is a good idea and it'll probably require this information to be plumbed through MreResult. Happy to help review if someone wants to take a look at this.
It looks like there are cases where run_metric will silently die.
I think it's the best way to iterate on a new metric definition, so silently dying is unfortunate.