On Sat, Oct 29, 2011 at 9:05 PM, Serguei Trouchelle <s...@cpan.org> wrote: > About the issue with different information in tail log and report, it was > addressed some time ago and Metabase contains correct information. Probably, > a server part responsible for writing log files seems to still have the same > problem and is using client information and not report's one. But Metabase > itself should be unaffected by this.
We "cope" with the fact that the information is different, but it's not good to rely on continued coping. We need a transport mechanism that serializes a Metabase report instead of relying on Test::Reporter::Transport::File to serialize an email-style report and then regenerate it. I don't currently have tuits to do the work, but I would be willing to help guide someone who is. Effectively, clone T::R::T::Metabase, lobotomize all the Metabase::Client::Simple parts out of it, and call ->save() on the test report instead of sending it. That's still "heavier" in terms of dependencies than T::R::T::Socket, but it's lighter than T::R::T::Metabase, so it's progress. -- David
