>>>>> On Tue, 31 Dec 2019 20:22:49 -0800, Karen Etheridge <p...@froods.org> 
>>>>> said:

  > I have been getting blasted with these types of failures again too. e.g.:
  > http://www.cpantesters.org/cpan/report/a3e7fbf8-2c2b-11ea-9cc5-910b4c49479c
  > http://www.cpantesters.org/cpan/report/a8244f3e-2a0d-11ea-bad3-922c4c49479c

  > Nigel, I'll be honest with you: I automatically ignore every report I
  > receive from you, because the false positive rate is so outrageously
  > high it's not even worth looking anymore.

Automatically ignoring will not help finding the bug that is triggered
in Nigel's setup.

I think it is worthwhile to report when Nigel's smoker start acting up.
I'd also find it worthwhile that Nigel stops his smokers when it happens
and reports at least to me, as the author of CPAN.pm, what happened in
his environment, so that we can figure out how to prevent it or at least
to shut down the smoker automatically.

My impression is that Nigel's smokers have been running fine for a long
time, but at least the solaris one is now acting up in weird ways. I
just found this one:

http://www.cpantesters.org/cpan/report/4d53df1a-2c66-11ea-abbc-55fa4b49479c

It is an "unknown" that reports during t/00-report-prereqs.t that
Package::DeprecationManager 0.17 is installed. It goes on the run a
zillion tests OK. But all of a sudden it does not find
Package::DeprecationManager anymore. It also can't locate Moose anymore.

As if somebody had removed the whole directory in which the test was
running.

Nigel, please stop this and maybe other smokers and help find out the
root cause. I'm sorry that this happens, I can imagine that the bug is
entirely mine, but I don't know what it is and how to fix it. I need
your input and your intuition to pinpoint the bug.

Thank you!
-- 
andreas

Reply via email to