Skip Menu |
 

This queue is for tickets about the JSON-Any CPAN distribution.

Report information
The Basics
Id: 30509
Status: resolved
Priority: 0/
Queue: JSON-Any

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.12
Fixed in: (no value)



Subject: Only JSON::Syck installed -> tests failing
If only JSON::Syck is installed and I try to install JSON::Any then I get this: Cannot determine perl version info from lib/JSON/Any.pm *** Module::AutoInstall version 1.03 *** Checking for Perl dependencies... [Core Features] - Test::More ...loaded. (0.72) - Carp ...loaded. (1.08) [JSON] - JSON ...missing. [JSON::XS] - JSON::XS ...missing. [JSON::PC] - JSON::PC ...missing. [JSON::DWIW] - JSON::DWIW ...missing. [JSON::Syck] - JSON::Syck ...loaded. (0.26) *** Module::AutoInstall configuration finished. Checking if your kit is complete... Looks good Writing Makefile for JSON::Any make[3]: Entering directory `/home/sand/.cpan/build/JSON-Any-1.12-uk9qz6' cp lib/JSON/Any.pm blib/lib/JSON/Any.pm Manifying blib/man3/JSON::Any.3 make[3]: Leaving directory `/home/sand/.cpan/build/JSON-Any-1.12-uk9qz6' (/usr/bin/make exited with 0) CPAN::Reporter: make result is 'pass', No errors. PERIGRIN/JSON-Any-1.12.tar.gz /usr/bin/make -- OK Running make test make[3]: Entering directory `/home/sand/.cpan/build/JSON-Any-1.12-uk9qz6' PERL_DL_NONLAZY=1 /home/src/perl/repoperls/installed-perls/perl/pm8lYjb/perl-5.8.0@32222/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/00-load.t t/01-JSON.t t/02-JSON-XS.t t/03-JSON-DWIW.t t/04-ENV.t t/05-JSON-Syck.t t/10_unicode.t t/kwalitee.t t/pod-coverage.t t/pod.t t/00-load.........# Testing JSON::Any 1.12, Perl 5.010000, /home/src/perl/repoperls/installed-perls/perl/pm8lYjb/perl-5.8.0@32222/bin/perl ok t/01-JSON.........skipped all skipped: JSON.pm not installed: Couldn't find a JSON Package. at (eval 3) line 1 t/02-JSON-XS......skipped all skipped: JSON::XS not installed: Couldn't find a JSON Package. at (eval 3) line 1 t/03-JSON-DWIW....skipped all skipped: JSON::DWIW not installed: Couldn't find a JSON Package. at (eval 3) line 1 t/04-ENV..........ok 2/2 skipped: various reasons t/05-JSON-Syck....ok t/10_unicode......# Couldn't find a JSON Package. at t/10_unicode.t line 13 # Couldn't find a JSON Package. at t/10_unicode.t line 13 # Couldn't find a JSON Package. at t/10_unicode.t line 13 # JSON::Syck does not support utf8 at t/10_unicode.t line 14 # Couldn't find a JSON Package. at t/10_unicode.t line 13 # No tests run! dubious ^ITest returned status 255 (wstat 65280, 0xff00) t/kwalitee........skipped all skipped: Test::Kwalitee not installed; skipping t/pod-coverage....skipped all skipped: Test::Pod::Coverage 1.04 required for testing POD coverage t/pod.............skipped all skipped: Test::Pod 1.14 required for testing POD Failed Test Stat Wstat Total Fail List of Failed ------------------------------------------------------------------------------- t/10_unicode.t 255 65280 ?? ?? ?? 6 tests and 2 subtests skipped. Failed 1/10 test scripts. 0/11 subtests failed. Is this intentional behaviour? What's the point of JSON::Any if it denies JSON::Syck? Should then not a different JSON be declared as dependency? I would not mind if this would be demanded. But failing is against my expectation. BTW, this was with bleadperl@32222. Thanks,
From: cpan [...] prather.org
Download (untitled) / with headers
text/plain 1.6k
On Mon Nov 05 19:15:38 2007, ANDK wrote: Show quoted text
> t/05-JSON-Syck....ok
Well here it says JSON::Syck was fine. So we're good there the problem is with the unicode test below. Show quoted text
> t/10_unicode......# Couldn't find a JSON Package. at t/10_unicode.t > line 13 > # Couldn't find a JSON Package. at t/10_unicode.t line 13 > # Couldn't find a JSON Package. at t/10_unicode.t line 13 > # JSON::Syck does not support utf8 at t/10_unicode.t line 14 > # Couldn't find a JSON Package. at t/10_unicode.t line 13 > # No tests run! > dubious > ^ITest returned status 255 (wstat 65280, 0xff00)
This is where we ran into an issue. JSON::Syck isn't supported for UNICDOE (which it explains here). The fact that this test failed instead of running a skip_all or some such when it couldn't find a valid test case is a bug (and I'll fix it shortly). Show quoted text
> Failed Test Stat Wstat Total Fail List of Failed >
------------------------------------------------------------------------------- Show quoted text
> t/10_unicode.t 255 65280 ?? ?? ?? > 6 tests and 2 subtests skipped. > Failed 1/10 test scripts. 0/11 subtests failed.
Show quoted text
> Is this intentional behaviour? What's the point of JSON::Any if it > denies JSON::Syck? Should then not a different JSON be declared as > dependency? I would not mind if this would be demanded. But failing is > against my expectation.
I intentionally chose not to require every JSON package under the sun for testing because that would defeat the purpose. I *do* declare JSON as the default requirement but I don't enforce it because as you rightly point out if you have *any* of the supported JSON backends this package should install cleanly. I'll have a fixed release asap. -Chris
Download (untitled) / with headers
text/plain 431b
On Tue Nov 06 14:42:44 2007, PERIGRIN wrote: Show quoted text
> This is where we ran into an issue. JSON::Syck isn't supported for > UNICDOE (which it explains here). The fact that this test failed > instead of running a skip_all or some such when it couldn't find a > valid test case is a bug (and I'll fix it shortly).
This should be fixed in 1.13 heading to CPAN now. I have tested with whatever patchlevel perl-current is on bleadperl. -Chris
Closing ticket as I've tested again with SVN and it seems to be working


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.