Skip Menu |

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

Report information
The Basics
Id: 85234
Status: resolved
Worked: 10 min
Priority: 0/
Queue: JSON-XS

People
Owner: Nobody in particular
Requestors: chisel [...] chizography.net
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 2.33
Fixed in: (no value)



Subject: fails to install against perl-5.18.0-RC2
Running Mkbootstrap for JSON::XS () cp XS.pm blib/lib/JSON/XS.pm cp XS/Boolean.pm blib/lib/JSON/XS/Boolean.pm chmod 644 XS.bs cp bin/json_xs blib/script/json_xs /disk/jkns/workspace/perl-5.18/build/tmp/perl-nap-5.18.0-2013.518.00-build/opt/xt/xt-perl/bin/perl -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/json_xs cp XS.bs blib/arch/auto/JSON/XS/XS.bs chmod 644 blib/arch/auto/JSON/XS/XS.bs gcc -c -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -DVERSION=\"2.33\" -DXS_VERSION=\"2.33\" -fpic "-I/disk/jkns/workspace/perl-5.18/build/tmp/perl-nap-5.18.0-2013.518.00-build/opt/xt/xt-perl/lib/5.18.0/x86_64-linux/CORE" XS.c XS.xs: In function 'ptr_to_index': XS.xs:190: warning: pointer targets in passing argument 1 of 'Perl_utf8_distance' differ in signedness XS.xs:190: warning: pointer targets in passing argument 2 of 'Perl_utf8_distance' differ in signedness XS.xs: In function 'encode_str': XS.xs:369: warning: pointer targets in passing argument 1 of 'decode_utf8' differ in signedness XS.xs:422: warning: pointer targets in passing argument 1 of 'encode_utf8' differ in signedness XS.xs:422: warning: pointer targets in assignment differ in signedness XS.xs: In function 'encode_sv': XS.xs:789: warning: ignoring return value of 'gcvt', declared with attribute warn_unused_result XS.xs: In function 'decode_str': XS.xs:1011: warning: suggest explicit braces to avoid ambiguous 'else' XS.xs:1037: warning: pointer targets in passing argument 1 of 'encode_utf8' differ in signedness XS.xs:1037: warning: pointer targets in assignment differ in signedness XS.xs:1057: warning: pointer targets in passing argument 1 of 'decode_utf8' differ in signedness XS.xs: In function 'decode_num': XS.xs:1208: warning: suggest explicit braces to avoid ambiguous 'else' XS.xs: In function 'decode_hv': XS.xs:1317: warning: comparison is always false due to limited range of data type XS.xs:1334: warning: value computed is not used XS.xs:1353: warning: value computed is not used XS.xs: In function 'decode_json': XS.xs:1605: warning: pointer targets in passing argument 2 of 'Perl_pv_uni_display' differ in signedness XS.xs:1706:26: warning: multi-line comment XS.xs: In function 'incr_parse': XS.xs:1765: warning: label 'modechange' defined but not used XS.c: In function 'XS_JSON__XS_CLONE': XS.c:1934: warning: unused variable 'items' XS.xs: In function 'XS_JSON__XS_filter_json_single_key_object': XS.xs:1901: warning: value computed is not used XS.xs:1904: warning: value computed is not used XS.xs: In function 'XS_JSON__XS_incr_parse': XS.xs:1944: warning: suggest explicit braces to avoid ambiguous 'else' XS.xs:1966: warning: suggest explicit braces to avoid ambiguous 'else' rm -f blib/arch/auto/JSON/XS/XS.so gcc -shared -L/usr/local/lib -L/usr/lib64 -L/lib64 -fstack-protector XS.o -o blib/arch/auto/JSON/XS/XS.so \ \ chmod 755 blib/arch/auto/JSON/XS/XS.so Manifying blib/man1/json_xs.1 Manifying blib/man3/JSON::XS.3 Manifying blib/man3/JSON::XS::Boolean.3 NETAPORTER/JSON-XS-2.33.tar.gz /usr/bin/make -j 3 -j 3 -- OK Running make test PERL_DL_NONLAZY=1 /disk/jkns/workspace/perl-5.18/build/tmp/perl-nap-5.18.0-2013.518.00-build/opt/xt/xt-perl/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00_load.t ............. ok t/01_utf8.t ............. ok t/02_error.t ............ ok t/03_types.t ............ ok t/04_dwiw_encode.t ...... ok t/05_dwiw_decode.t ...... ok t/06_pc_pretty.t ........ ok t/07_pc_esc.t ........... ok t/08_pc_base.t .......... ok t/09_pc_extra_number.t .. ok t/10_pc_keysort.t ....... ok t/11_pc_expo.t .......... ok t/12_blessed.t .......... ok t/13_limit.t ............ ok t/14_latin1.t ........... ok t/15_prefix.t ........... ok t/16_tied.t ............. ok t/17_relaxed.t .......... ok t/18_json_checker.t ..... ok # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Failed test 'data' # at t/19_incr.t line 22. # Looks like you failed 49 tests of 697. t/19_incr.t ............. Dubious, test returned 49 (wstat 12544, 0x3100) Failed 49/697 subtests t/20_faihu.t ............ ok t/21_evans.t ............ ok t/22_comment_at_eof.t ... ok t/99_binary.t ........... ok Test Summary Report ------------------- t/19_incr.t (Wstat: 12544 Tests: 697 Failed: 49) Failed tests: 5, 17, 20, 23, 26, 32, 38, 44, 47, 50, 53 59, 62, 68, 71, 74, 80, 86, 95, 110, 122 128, 134, 140, 146, 149, 155, 161, 179 182, 191, 200, 206, 212, 215, 221, 233 242, 245, 251, 260, 266, 272, 275, 278 281, 284, 290, 296 Non-zero exit status: 49 Files=24, Tests=25564, 4 wallclock secs ( 2.41 usr 0.04 sys + 2.95 cusr 0.17 csys = 5.57 CPU) Result: FAIL
Subject: Re: [rt.cpan.org #85234] fails to install against perl-5.18.0-RC2
Date: Tue, 14 May 2013 13:54:10 +0200
To: Chisel Wright via RT <bug-JSON-XS [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
Hi! Please send your bug report it to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss potentially vital bug reports such as yours (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de> Last updated: 2012-04-22
On Tue May 14 12:54:31 2013, schmorp@schmorp.de wrote: Show quoted text
> Unfortunately, ignoring rt.cpan.org is not an option either: for people > reporting possible bugs there is no indication that their report will > be ignored, and for module authors it means they miss potentially vital > bug reports such as yours (and of course it's a great impression if > rt.cpan.org has lots of bug reports that are unanswered, making a module > look unmaintained when in fact the opposite might be true).
This is incorrect; if you set your metadata to refer to a different bug tracker it clearly says: Please visit the preferred bug tracker to report your issue. in a big yellow box for pages for that distro. e.g. https://rt.cpan.org/Dist/Display.html?Queue=Test-DBIx-Class-Schema Surely setting this metadata will help reduce the amount of tickets going (wrongly) to rt.cpan.org and save you from having to send so many responses like this.


This bug is identical in every way to rt#84151

https://rt.cpan.org/Public/Bug/Display.html?id=84151

Please try the patch listed in that bug, and perhaps, add yourself as a requestor to that bug, and then maybe close this one.

No point in having 2 bug requests for the same bug, after all, that one of the benefits of having a public bug tracker.

As pointed out this report is identical to rt#84151 https://rt.cpan.org/Public/Bug/Display.html?id=84151 The patch in the other ticket applies cleanly under 5.18 and the tests now pass. I'll close this ticket shortly.
Closing as a duplicate of rt#84151