I'll explore if there's a quick fix, but it might have to wait until Monday.
In the mean time, please store your reports locally or just give those
smokers a summer holiday.
-- David
David Golden wrote:
> In the mean time, please store your reports locally or just give those
> smokers a summer holiday.
By the way, is there any interest in something like "Test::Reporter::Transport::MetabaseFallback"?
I have some preliminary realization of transport which tries to send report to Metabase and if there's any error, it
saves it in a file. If sending is successful, it also sends a small batch of saved reports if they exist in the file cache.
If anyone is interested, I can bundle it and release to CPAN.
--
Serguei Trouchelle
I have uploaded metabase-relayd version 0.28 to CPAN which resolves this issue.
Thanks,
--
Chris Williams
aka BinGOs
PGP ID 0x4658671F
http://www.gumbynet.org.uk
==========================
+1
I'd be willing to consider a patch directly for T::R::T::Metabase for
that. It shouldn't add any more dependencies and is less pain for
casual end-users so they don't have to think about it if/when Metabase
is down.
-- David
Thanks.
I take it that when all is sorted, all that I'll need to do will be to change offline=1 to offline=0 and restart metabase-relayd and all the queued items will be magically sent?
-Nigel
> By the way, is there any interest in something like
> "Test::Reporter::Transport::MetabaseFallback"?
> I have some preliminary realization of transport which tries to send report
> to Metabase and if there's any error, it saves it in a file. If sending is
> successful, it also sends a small batch of saved reports if they exist in
> the file cache.
> If anyone is interested, I can bundle it and release to CPAN.
This would be splendid, especially if it's a drop-in replacement for the
normal T:R:T:Metabase requiring no extra config.
--
David Cantrell | Bourgeois reactionary pig