On 11 July 2016 at 01:24, Slaven Rezic wrote:
> s it possible to blacklist/whitelist distributions for
> parallel testing?
If you mandate a new enough version of Test::Harness, there's a
control file it will pick up and use.
On 2 July 2016 at 09:05, Karen Etheridge wrote:
>
> Hopefully there is enough information in these reports to diagnose the root
> issue; if not, no doubt the collective wisdom exists on this list. thank
> you!
+1
These seriously broken smoker setups degrade the overall
On 5 February 2017 at 15:52, James E Keenan wrote:
> reports across many versions of Perl and many different OSes. Instead, all
> I see is:
>
> 5.14.2: One test on Darwin
> 5.24.1: One test on Cygwin
> 5.25.9: One test on Linux
> 5.25.10: One test on Linux
>
> Something is
On 7 February 2017 at 03:34, Alceu Rodrigues de Freitas Junior via
cpan-testers-discuss wrote:
> I just released a new distribution
> (http://search.cpan.org/~arfreitas/Linux-NFS-BigDir-0.001/) but I see that
> is getting a lot of fails because h2ph is not
On 2 March 2017 at 01:28, Nigel Horne wrote:
>> I have one location where https://metabase.cpantesters.org/beta/ works but
>> https://metabase.cpantesters.org/api/v1/ doesn't.
>
> Still the case this morning (US time). /beta/ works, but /api/v1 gives 500
> HTTP status.
On 4 September 2016 at 11:39, Alceu R. de Freitas Jr. via
cpan-testers-discuss wrote:
>
> I'm willing to fix the smoker as long as I got a positive feedback (like
> yours). On the other hand, "turn off your smoker or block my id" hardly
> qualifies as positive.
On 5 September 2016 at 04:10, Slaven Rezic wrote:
>>
>> Of course I can try to compile the interpreter without perlbrew, but that
>> leads to the questions: are we looking for to validate CPAN modules against
>> the interpreter shipped with OpenBSD or the standard perl?
>>
>
>
On 27 March 2017 at 16:10, Dan Collins wrote:
> I've had a chance to make sure that this test environment isn't horribly
> broken...
Yeah, there's enough broken you sort of need a double-testing system.
Start with =0 , and then upon hitting a failure, retry with =1 ...
TL;DR:
- Testers, please set PERL_USE_UNSAFE_INC=0 to make the bugs actually show up.
- P5P: I don't know what to say, but testers aren't yet to really even
start showing the real . in @INC Bugs, please proceed with caution.
I'm getting a little afraid that not enough testers are running in
On 21 March 2017 at 09:09, Doug Bell wrote:
>
> How can the user interactively fix a configuration problem that would also
> then be considered a failure in configuration? If the configure script
> allows it, it must be normal operation, no? If it involves editing the
>
On 21 March 2017 at 08:02, Doug Bell wrote:
> * "X" is the main type
> * PASS = 1
> * FAIL = 2
> * NA = 3
> * UNKNOWN = 4
> * "Y" is the step of the process we made it to
> * 0 is "complete/unknown"
> * 1 is "extract"
> * 2 is "build"
> * 3 is "test"
> * 4 is "install"
> *
I've seen a lot of test failures from DDICK this week that all end up
being explainable
as "Didn't satisfy dependencies of my dependencies"
This is annoying as its a transient breakage, so the places the fail
is being reported
is not a place I can reasonably fix the issue.
For instance:
On 24 April 2017 at 06:01, Alceu Rodrigues de Freitas Junior via
cpan-testers-discuss wrote:
> It occurred to me that I would still need h2ph to invoke the getdents
> syscall anyway, unless there is some alternatives I'm not aware.
>
> Maybe using XS?
That was
On 6 July 2017 at 17:37, Doug Bell wrote:
> To me, that makes it a non-solution:
> Forcing everyone using the data to figure out which data is invalid is too
> high a burden. If we simply hide the data from any and all APIs that CPAN
> Testers has, that is, to me, worse than
On 2 May 2017 at 05:43, Diab Jerius wrote:
> Is this expected behavior for -TRIAL releases?
>
> Thanks!
I'd chalk it up to the processing delay between the two.
If you go down the "recent" list on metacpan, everything released
since April 27th exhibits this behaviour,
On 15 October 2017 at 02:34, James E Keenan wrote:
> Fellow CPANtesters,
>
> Greetings from the 2017 Perl 5 Core Hackathon in Amsterdam! I am writing to
> you as a follow-up to a discussion which participants had this afternoon
> entitled "What Do We Want and Need from Smoke
On 23 January 2018 at 09:56, Alceu Rodrigues de Freitas Junior via
cpan-testers-discuss wrote:
>>> 6. Not every CPAN contributor writes tests that allow execution of
>>> tests in parallel, or even to run in parallel with another perl
>>> executing the same
On Tue, 14 Jul 2020 at 15:36, Doug Bell wrote:
>
>
> >
> > I guess this "oh, this thing I haven't used in a while, is now
> > completely broken" pattern is the price we'll be paying more of for
> > modernity.
>
> No, it's the price we all pay for ignoring necessary maintenance of working
>
On Sat, 11 Jul 2020 at 08:53, Felipe Gasper wrote:
>
> Hello,
>
> For a few days now I’ve been monitoring CPAN Testers results and
> seeing “Service Unavailable” when I try to load an individual test report.
>
> Have others been seeing this?
>
> Thank you!
Indeed. It was
19 matches
Mail list logo