Hi! On the client side, you may bypass this and send two (or several) reports with the same "signature" by either skipping history (e.g. in cpanm-reporter, passing the "--skip-history" argument) or manually deleting the entry from your history file (a flat file usually under ~/.cpanreporter/reports-sent.db)
Hope it helps. Cheers! garu On Wed, Sep 27, 2017 at 8:16 PM Doug Bell <d...@preaction.me> wrote: > > > On Sep 27, 2017, at 6:35 AM, Nigel Horne <n...@bandsman.co.uk> wrote: > > > > If I test a module with two variants of Perl, say > darwin-thread-multi-ld-2level and darwin-thread-multi-2level, two reports > are sent, which is fine. However if I try to submit from Perls built with > different compilers (say gcc and clang or icc) that are both > x86_64-linux-thread-multi, the second test is marked as a duplicate and not > submitted which is especially wrong if one compiler fails and one > succeeds. Is this deliberate or and oversight? Is this behaviour that I > can change? > > > > -Nigel > > I think if they show different results, they should be submitted. I'm > pretty sure there's nothing in the server that tries detecting duplicate > reports, so it must be the reporter client doing it. I'm not sure if > there's a way to disable that or bypass it. Does someone else know? >
