ruby-yajl →
1.2.0-3 →
armhf → 2015-07-14 08:59:58
sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bm-wb-04
╔══════════════════════════════════════════════════════════════════════════════╗
║ ruby-yajl 1.2.0-3 (armhf) 14 Jul 2015 08:49 ║
╚══════════════════════════════════════════════════════════════════════════════╝
Package: ruby-yajl
Version: 1.2.0-3
Source Version: 1.2.0-3
Distribution: stretch-staging
Machine Architecture: armhf
Host Architecture: armhf
Build Architecture: armhf
I: NOTICE: Log filtering will replace 'build/ruby-yajl-wM0aDw/ruby-yajl-1.2.0' with '«PKGBUILDDIR»'
I: NOTICE: Log filtering will replace 'build/ruby-yajl-wM0aDw' with '«BUILDDIR»'
I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/stretch-staging-armhf-sbuild-7b8de8a2-0f23-46ce-b977-f5b9149e1e70' with '«CHROOT»'
┌──────────────────────────────────────────────────────────────────────────────┐
│ Update chroot │
└──────────────────────────────────────────────────────────────────────────────┘
Get:1 http://172.17.0.1 stretch-staging InRelease [11.3 kB]
Get:2 http://172.17.0.1 stretch-staging/main Sources [8089 kB]
Get:3 http://172.17.0.1 stretch-staging/main armhf Packages [9945 kB]
Ign http://172.17.0.1 stretch-staging/main Translation-en
Fetched 18.0 MB in 34s (518 kB/s)
Reading package lists...
┌──────────────────────────────────────────────────────────────────────────────┐
│ Fetch source files │
└──────────────────────────────────────────────────────────────────────────────┘
Check APT
─────────
Checking available source versions...
Download source files with APT
──────────────────────────────
Reading package lists...
Building dependency tree...
NOTICE: 'ruby-yajl' packaging is maintained in the 'Git' version control system at:
git://anonscm.debian.org/pkg-ruby-extras/ruby-yajl.git
Need to get 580 kB of source archives.
Get:1 http://172.17.0.1/private/ stretch-staging/main ruby-yajl 1.2.0-3 (dsc) [2139 B]
Get:2 http://172.17.0.1/private/ stretch-staging/main ruby-yajl 1.2.0-3 (tar) [573 kB]
Get:3 http://172.17.0.1/private/ stretch-staging/main ruby-yajl 1.2.0-3 (diff) [5116 B]
Fetched 580 kB in 0s (2653 kB/s)
Download complete and in download only mode
Check architectures
───────────────────
Check dependencies
──────────────────
Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package `sbuild-build-depends-core-dummy' in `/«BUILDDIR»/resolver-W3F3hT/apt_archive/sbuild-build-depends-core-dummy.deb'.
OK
Ign file: ./ InRelease
Get:1 file: ./ Release.gpg [299 B]
Get:2 file: ./ Release [2119 B]
Ign file: ./ Translation-en
Reading package lists...
Reading package lists...
┌──────────────────────────────────────────────────────────────────────────────┐
│ Install core build dependencies (apt-based resolver) │
└──────────────────────────────────────────────────────────────────────────────┘
Installing build dependencies
Reading package lists...
Building dependency tree...
The following NEW packages will be installed:
sbuild-build-depends-core-dummy
debconf: delaying package configuration, since apt-utils is not installed
0 upgraded, 1 newly installed, 0 to remove and 81 not upgraded.
Need to get 0 B/812 B of archives.
After this operation, 0 B of additional disk space will be used.
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 11998 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
Merged Build-Depends: libc6-dev | libc-dev, gcc (>= 4:4.9.1), g++ (>= 4:4.9.1), make, dpkg-dev (>= 1.17.11), debhelper (>= 7.0.50~), gem2deb (>= 0.7.5~), ruby-rspec
Filtered Build-Depends: libc6-dev, gcc (>= 4:4.9.1), g++ (>= 4:4.9.1), make, dpkg-dev (>= 1.17.11), debhelper (>= 7.0.50~), gem2deb (>= 0.7.5~), ruby-rspec
dpkg-deb: building package `sbuild-build-depends-ruby-yajl-dummy' in `/«BUILDDIR»/resolver-7RD9IL/apt_archive/sbuild-build-depends-ruby-yajl-dummy.deb'.
OK
Ign file: ./ InRelease
Get:1 file: ./ Release.gpg [299 B]
Get:2 file: ./ Release [2119 B]
Ign file: ./ Translation-en
Reading package lists...
Reading package lists...
┌──────────────────────────────────────────────────────────────────────────────┐
│ Install ruby-yajl build dependencies (apt-based resolver) │
└──────────────────────────────────────────────────────────────────────────────┘
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
bsdmainutils ca-certificates debhelper devscripts dh-python file gem2deb
gem2deb-test-runner gettext gettext-base groff-base intltool-debian
libasprintf0c2 libcroco3 libexpat1 libffi6 libglib2.0-0 libgmp-dev libgmp10
libgmpxx4ldbl libmagic1 libmpdec2 libpipeline1 libpython3-stdlib
libpython3.4-minimal libpython3.4-stdlib libruby2.1 libruby2.2 libsqlite3-0
libssl1.0.0 libunistring0 libxml2 libyaml-0-2 man-db mime-support openssl
po-debconf python3 python3-chardet python3-debian python3-minimal
python3-pkg-resources python3-six python3.4 python3.4-minimal ruby
ruby-all-dev ruby-diff-lcs ruby-power-assert ruby-rspec ruby-rspec-core
ruby-rspec-expectations ruby-rspec-mocks ruby-rspec-support ruby-setup
ruby-test-unit ruby-thread-order ruby2.1 ruby2.1-dev ruby2.2 ruby2.2-dev
rubygems-integration
Suggested packages:
wamerican wordlist whois vacation dh-make bsd-mailx mailx cvs-buildpackage
debbindiff devscripts-el gnuplot libauthen-sasl-perl
libfile-desktopentry-perl libnet-smtp-ssl-perl libterm-size-perl
libyaml-syck-perl mutt ssh-client svn-buildpackage w3m gettext-doc groff
gmp-doc libgmp10-doc libmpfr-dev less www-browser libmail-box-perl
python3-doc python3-tk python3-venv python3-setuptools python3.4-venv
python3.4-doc binfmt-support ri ruby-dev bundler
Recommended packages:
at dctrl-tools dput dupload libdistro-info-perl libencode-locale-perl
libjson-perl liburi-perl libwww-perl lintian patchutils python3-magic strace
unzip wdiff wget curl debian-keyring equivs liblwp-protocol-https-perl
libsoap-lite-perl apt-file autopoint libasprintf-dev libgettextpo-dev
libglib2.0-data shared-mime-info xdg-user-dirs xml-core
libmail-sendmail-perl python3-apt libjs-jquery fonts-lato
The following NEW packages will be installed:
bsdmainutils ca-certificates debhelper devscripts dh-python file gem2deb
gem2deb-test-runner gettext gettext-base groff-base intltool-debian
libasprintf0c2 libcroco3 libexpat1 libffi6 libglib2.0-0 libgmp-dev
libgmpxx4ldbl libmagic1 libmpdec2 libpipeline1 libpython3-stdlib
libpython3.4-minimal libpython3.4-stdlib libruby2.1 libruby2.2 libsqlite3-0
libssl1.0.0 libunistring0 libxml2 libyaml-0-2 man-db mime-support openssl
po-debconf python3 python3-chardet python3-debian python3-minimal
python3-pkg-resources python3-six python3.4 python3.4-minimal ruby
ruby-all-dev ruby-diff-lcs ruby-power-assert ruby-rspec ruby-rspec-core
ruby-rspec-expectations ruby-rspec-mocks ruby-rspec-support ruby-setup
ruby-test-unit ruby-thread-order ruby2.1 ruby2.1-dev ruby2.2 ruby2.2-dev
rubygems-integration sbuild-build-depends-ruby-yajl-dummy
The following packages will be upgraded:
libgmp10
1 upgraded, 62 newly installed, 0 to remove and 80 not upgraded.
Need to get 25.5 MB/25.5 MB of archives.
After this operation, 86.3 MB of additional disk space will be used.
Get:1 http://172.17.0.1/private/ stretch-staging/main libpipeline1 armhf 1.4.0-1 [24.0 kB]
Get:2 http://172.17.0.1/private/ stretch-staging/main groff-base armhf 1.22.3-1 [1085 kB]
Get:3 http://172.17.0.1/private/ stretch-staging/main bsdmainutils armhf 9.0.6 [177 kB]
Get:4 http://172.17.0.1/private/ stretch-staging/main man-db armhf 2.7.0.2-5 [972 kB]
Get:5 http://172.17.0.1/private/ stretch-staging/main libasprintf0c2 armhf 0.19.4-1 [31.5 kB]
Get:6 http://172.17.0.1/private/ stretch-staging/main libmagic1 armhf 1:5.22+15-2 [244 kB]
Get:7 http://172.17.0.1/private/ stretch-staging/main libxml2 armhf 2.9.1+dfsg1-5 [703 kB]
Get:8 http://172.17.0.1/private/ stretch-staging/main libffi6 armhf 3.1-2 [18.1 kB]
Get:9 http://172.17.0.1/private/ stretch-staging/main libglib2.0-0 armhf 2.44.1-1.1 [2312 kB]
Get:10 http://172.17.0.1/private/ stretch-staging/main libcroco3 armhf 0.6.8-3 [121 kB]
Get:11 http://172.17.0.1/private/ stretch-staging/main libexpat1 armhf 2.1.0-6 [60.2 kB]
Get:12 http://172.17.0.1/private/ stretch-staging/main libmpdec2 armhf 2.4.1-1 [65.8 kB]
Get:13 http://172.17.0.1/private/ stretch-staging/main libssl1.0.0 armhf 1.0.2d-1 [882 kB]
Get:14 http://172.17.0.1/private/ stretch-staging/main libpython3.4-minimal armhf 3.4.3-7 [487 kB]
Get:15 http://172.17.0.1/private/ stretch-staging/main mime-support all 3.58 [36.0 kB]
Get:16 http://172.17.0.1/private/ stretch-staging/main libsqlite3-0 armhf 3.8.10.2-1 [389 kB]
Get:17 http://172.17.0.1/private/ stretch-staging/main libpython3.4-stdlib armhf 3.4.3-7 [1983 kB]
Get:18 http://172.17.0.1/private/ stretch-staging/main libunistring0 armhf 0.9.3-5.2 [253 kB]
Get:19 http://172.17.0.1/private/ stretch-staging/main libyaml-0-2 armhf 0.1.6-3 [41.5 kB]
Get:20 http://172.17.0.1/private/ stretch-staging/main python3.4-minimal armhf 3.4.3-7 [1142 kB]
Get:21 http://172.17.0.1/private/ stretch-staging/main python3-minimal armhf 3.4.3-4 [34.8 kB]
Get:22 http://172.17.0.1/private/ stretch-staging/main python3.4 armhf 3.4.3-7 [219 kB]
Get:23 http://172.17.0.1/private/ stretch-staging/main libpython3-stdlib armhf 3.4.3-4 [18.2 kB]
Get:24 http://172.17.0.1/private/ stretch-staging/main dh-python all 1.20150705-1 [66.7 kB]
Get:25 http://172.17.0.1/private/ stretch-staging/main python3 armhf 3.4.3-4 [21.3 kB]
Get:26 http://172.17.0.1/private/ stretch-staging/main file armhf 1:5.22+15-2 [59.9 kB]
Get:27 http://172.17.0.1/private/ stretch-staging/main gettext-base armhf 0.19.4-1 [117 kB]
Get:28 http://172.17.0.1/private/ stretch-staging/main openssl armhf 1.0.2d-1 [683 kB]
Get:29 http://172.17.0.1/private/ stretch-staging/main ca-certificates all 20150426 [208 kB]
Get:30 http://172.17.0.1/private/ stretch-staging/main gettext armhf 0.19.4-1 [1168 kB]
Get:31 http://172.17.0.1/private/ stretch-staging/main intltool-debian all 0.35.0+20060710.2 [25.9 kB]
Get:32 http://172.17.0.1/private/ stretch-staging/main po-debconf all 1.0.18 [248 kB]
Get:33 http://172.17.0.1/private/ stretch-staging/main debhelper all 9.20150628 [817 kB]
Get:34 http://172.17.0.1/private/ stretch-staging/main devscripts armhf 2.15.5 [907 kB]
Get:35 http://172.17.0.1/private/ stretch-staging/main rubygems-integration all 1.9 [4754 B]
Get:36 http://172.17.0.1/private/ stretch-staging/main libgmp10 armhf 2:6.0.0+dfsg-7+rpi1 [188 kB]
Get:37 http://172.17.0.1/private/ stretch-staging/main libruby2.1 armhf 2.1.5-3 [3020 kB]
Get:38 http://172.17.0.1/private/ stretch-staging/main ruby2.1 armhf 2.1.5-3 [276 kB]
Get:39 http://172.17.0.1/private/ stretch-staging/main ruby all 1:2.1.5.1 [9756 B]
Get:40 http://172.17.0.1/private/ stretch-staging/main libruby2.2 armhf 2.2.2-2 [2849 kB]
Get:41 http://172.17.0.1/private/ stretch-staging/main ruby2.2 armhf 2.2.2-2 [213 kB]
Get:42 http://172.17.0.1/private/ stretch-staging/main ruby-power-assert all 0.2.3-1 [7236 B]
Get:43 http://172.17.0.1/private/ stretch-staging/main ruby-test-unit all 3.1.2-1 [60.0 kB]
Get:44 http://172.17.0.1/private/ stretch-staging/main gem2deb-test-runner all 0.18.3 [16.2 kB]
Get:45 http://172.17.0.1/private/ stretch-staging/main python3-pkg-resources all 17.0-1 [43.7 kB]
Get:46 http://172.17.0.1/private/ stretch-staging/main python3-chardet all 2.3.0-1 [96.1 kB]
Get:47 http://172.17.0.1/private/ stretch-staging/main python3-six all 1.9.0-3 [13.7 kB]
Get:48 http://172.17.0.1/private/ stretch-staging/main python3-debian all 0.1.27 [50.9 kB]
Get:49 http://172.17.0.1/private/ stretch-staging/main libgmpxx4ldbl armhf 2:6.0.0+dfsg-7+rpi1 [21.6 kB]
Get:50 http://172.17.0.1/private/ stretch-staging/main libgmp-dev armhf 2:6.0.0+dfsg-7+rpi1 [553 kB]
Get:51 http://172.17.0.1/private/ stretch-staging/main ruby2.1-dev armhf 2.1.5-3 [982 kB]
Get:52 http://172.17.0.1/private/ stretch-staging/main ruby2.2-dev armhf 2.2.2-2 [989 kB]
Get:53 http://172.17.0.1/private/ stretch-staging/main ruby-all-dev all 1:2.1.5.1 [9188 B]
Get:54 http://172.17.0.1/private/ stretch-staging/main ruby-setup all 3.4.1-9 [34.2 kB]
Get:55 http://172.17.0.1/private/ stretch-staging/main gem2deb all 0.18.3 [51.6 kB]
Get:56 http://172.17.0.1/private/ stretch-staging/main ruby-diff-lcs all 1.2.5-1 [26.7 kB]
Get:57 http://172.17.0.1/private/ stretch-staging/main ruby-rspec-support all 3.3.0c0e0m0s0-1 [24.3 kB]
Get:58 http://172.17.0.1/private/ stretch-staging/main ruby-rspec-expectations all 3.3.0c0e0m0s0-1 [90.1 kB]
Get:59 http://172.17.0.1/private/ stretch-staging/main ruby-rspec-mocks all 3.3.0c0e0m0s0-1 [87.0 kB]
Get:60 http://172.17.0.1/private/ stretch-staging/main ruby-thread-order all 1.1.0-1 [5096 B]
Get:61 http://172.17.0.1/private/ stretch-staging/main ruby-rspec-core all 3.3.0c0e0m0s0-1 [174 kB]
Get:62 http://172.17.0.1/private/ stretch-staging/main ruby-rspec all 3.3.0c0e0m0s0-1 [6544 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 25.5 MB in 7s (3359 kB/s)
Selecting previously unselected package libpipeline1:armhf.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 11998 files and directories currently installed.)
Preparing to unpack .../libpipeline1_1.4.0-1_armhf.deb ...
Unpacking libpipeline1:armhf (1.4.0-1) ...
Selecting previously unselected package groff-base.
Preparing to unpack .../groff-base_1.22.3-1_armhf.deb ...
Unpacking groff-base (1.22.3-1) ...
Selecting previously unselected package bsdmainutils.
Preparing to unpack .../bsdmainutils_9.0.6_armhf.deb ...
Unpacking bsdmainutils (9.0.6) ...
Selecting previously unselected package man-db.
Preparing to unpack .../man-db_2.7.0.2-5_armhf.deb ...
Unpacking man-db (2.7.0.2-5) ...
Selecting previously unselected package libasprintf0c2:armhf.
Preparing to unpack .../libasprintf0c2_0.19.4-1_armhf.deb ...
Unpacking libasprintf0c2:armhf (0.19.4-1) ...
Selecting previously unselected package libmagic1:armhf.
Preparing to unpack .../libmagic1_1%3a5.22+15-2_armhf.deb ...
Unpacking libmagic1:armhf (1:5.22+15-2) ...
Selecting previously unselected package libxml2:armhf.
Preparing to unpack .../libxml2_2.9.1+dfsg1-5_armhf.deb ...
Unpacking libxml2:armhf (2.9.1+dfsg1-5) ...
Selecting previously unselected package libffi6:armhf.
Preparing to unpack .../libffi6_3.1-2_armhf.deb ...
Unpacking libffi6:armhf (3.1-2) ...
Selecting previously unselected package libglib2.0-0:armhf.
Preparing to unpack .../libglib2.0-0_2.44.1-1.1_armhf.deb ...
Unpacking libglib2.0-0:armhf (2.44.1-1.1) ...
Selecting previously unselected package libcroco3:armhf.
Preparing to unpack .../libcroco3_0.6.8-3_armhf.deb ...
Unpacking libcroco3:armhf (0.6.8-3) ...
Selecting previously unselected package libexpat1:armhf.
Preparing to unpack .../libexpat1_2.1.0-6_armhf.deb ...
Unpacking libexpat1:armhf (2.1.0-6) ...
Selecting previously unselected package libmpdec2:armhf.
Preparing to unpack .../libmpdec2_2.4.1-1_armhf.deb ...
Unpacking libmpdec2:armhf (2.4.1-1) ...
Selecting previously unselected package libssl1.0.0:armhf.
Preparing to unpack .../libssl1.0.0_1.0.2d-1_armhf.deb ...
Unpacking libssl1.0.0:armhf (1.0.2d-1) ...
Selecting previously unselected package libpython3.4-minimal:armhf.
Preparing to unpack .../libpython3.4-minimal_3.4.3-7_armhf.deb ...
Unpacking libpython3.4-minimal:armhf (3.4.3-7) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../mime-support_3.58_all.deb ...
Unpacking mime-support (3.58) ...
Selecting previously unselected package libsqlite3-0:armhf.
Preparing to unpack .../libsqlite3-0_3.8.10.2-1_armhf.deb ...
Unpacking libsqlite3-0:armhf (3.8.10.2-1) ...
Selecting previously unselected package libpython3.4-stdlib:armhf.
Preparing to unpack .../libpython3.4-stdlib_3.4.3-7_armhf.deb ...
Unpacking libpython3.4-stdlib:armhf (3.4.3-7) ...
Selecting previously unselected package libunistring0:armhf.
Preparing to unpack .../libunistring0_0.9.3-5.2_armhf.deb ...
Unpacking libunistring0:armhf (0.9.3-5.2) ...
Selecting previously unselected package libyaml-0-2:armhf.
Preparing to unpack .../libyaml-0-2_0.1.6-3_armhf.deb ...
Unpacking libyaml-0-2:armhf (0.1.6-3) ...
Selecting previously unselected package python3.4-minimal.
Preparing to unpack .../python3.4-minimal_3.4.3-7_armhf.deb ...
Unpacking python3.4-minimal (3.4.3-7) ...
Selecting previously unselected package python3-minimal.
Preparing to unpack .../python3-minimal_3.4.3-4_armhf.deb ...
Unpacking python3-minimal (3.4.3-4) ...
Selecting previously unselected package python3.4.
Preparing to unpack .../python3.4_3.4.3-7_armhf.deb ...
Unpacking python3.4 (3.4.3-7) ...
Selecting previously unselected package libpython3-stdlib:armhf.
Preparing to unpack .../libpython3-stdlib_3.4.3-4_armhf.deb ...
Unpacking libpython3-stdlib:armhf (3.4.3-4) ...
Selecting previously unselected package dh-python.
Preparing to unpack .../dh-python_1.20150705-1_all.deb ...
Unpacking dh-python (1.20150705-1) ...
Setting up libssl1.0.0:armhf (1.0.2d-1) ...
Setting up libpython3.4-minimal:armhf (3.4.3-7) ...
Setting up libexpat1:armhf (2.1.0-6) ...
Setting up python3.4-minimal (3.4.3-7) ...
Setting up python3-minimal (3.4.3-4) ...
Processing triggers for libc-bin (2.19-18) ...
Selecting previously unselected package python3.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13612 files and directories currently installed.)
Preparing to unpack .../python3_3.4.3-4_armhf.deb ...
Unpacking python3 (3.4.3-4) ...
Selecting previously unselected package file.
Preparing to unpack .../file_1%3a5.22+15-2_armhf.deb ...
Unpacking file (1:5.22+15-2) ...
Selecting previously unselected package gettext-base.
Preparing to unpack .../gettext-base_0.19.4-1_armhf.deb ...
Unpacking gettext-base (0.19.4-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2d-1_armhf.deb ...
Unpacking openssl (1.0.2d-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20150426_all.deb ...
Unpacking ca-certificates (20150426) ...
Selecting previously unselected package gettext.
Preparing to unpack .../gettext_0.19.4-1_armhf.deb ...
Unpacking gettext (0.19.4-1) ...
Selecting previously unselected package intltool-debian.
Preparing to unpack .../intltool-debian_0.35.0+20060710.2_all.deb ...
Unpacking intltool-debian (0.35.0+20060710.2) ...
Selecting previously unselected package po-debconf.
Preparing to unpack .../po-debconf_1.0.18_all.deb ...
Unpacking po-debconf (1.0.18) ...
Selecting previously unselected package debhelper.
Preparing to unpack .../debhelper_9.20150628_all.deb ...
Unpacking debhelper (9.20150628) ...
Selecting previously unselected package devscripts.
Preparing to unpack .../devscripts_2.15.5_armhf.deb ...
Unpacking devscripts (2.15.5) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.9_all.deb ...
Unpacking rubygems-integration (1.9) ...
Preparing to unpack .../libgmp10_2%3a6.0.0+dfsg-7+rpi1_armhf.deb ...
Unpacking libgmp10:armhf (2:6.0.0+dfsg-7+rpi1) over (2:6.0.0+dfsg-6+rpi1) ...
Selecting previously unselected package libruby2.1:armhf.
Preparing to unpack .../libruby2.1_2.1.5-3_armhf.deb ...
Unpacking libruby2.1:armhf (2.1.5-3) ...
Selecting previously unselected package ruby2.1.
Preparing to unpack .../ruby2.1_2.1.5-3_armhf.deb ...
Unpacking ruby2.1 (2.1.5-3) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.1.5.1_all.deb ...
Unpacking ruby (1:2.1.5.1) ...
Selecting previously unselected package libruby2.2:armhf.
Preparing to unpack .../libruby2.2_2.2.2-2_armhf.deb ...
Unpacking libruby2.2:armhf (2.2.2-2) ...
Selecting previously unselected package ruby2.2.
Preparing to unpack .../ruby2.2_2.2.2-2_armhf.deb ...
Unpacking ruby2.2 (2.2.2-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.3-1_all.deb ...
Unpacking ruby-power-assert (0.2.3-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.2-1_all.deb ...
Unpacking ruby-test-unit (3.1.2-1) ...
Selecting previously unselected package gem2deb-test-runner.
Preparing to unpack .../gem2deb-test-runner_0.18.3_all.deb ...
Unpacking gem2deb-test-runner (0.18.3) ...
Selecting previously unselected package python3-pkg-resources.
Preparing to unpack .../python3-pkg-resources_17.0-1_all.deb ...
Unpacking python3-pkg-resources (17.0-1) ...
Selecting previously unselected package python3-chardet.
Preparing to unpack .../python3-chardet_2.3.0-1_all.deb ...
Unpacking python3-chardet (2.3.0-1) ...
Selecting previously unselected package python3-six.
Preparing to unpack .../python3-six_1.9.0-3_all.deb ...
Unpacking python3-six (1.9.0-3) ...
Selecting previously unselected package python3-debian.
Preparing to unpack .../python3-debian_0.1.27_all.deb ...
Unpacking python3-debian (0.1.27) ...
Selecting previously unselected package libgmpxx4ldbl:armhf.
Preparing to unpack .../libgmpxx4ldbl_2%3a6.0.0+dfsg-7+rpi1_armhf.deb ...
Unpacking libgmpxx4ldbl:armhf (2:6.0.0+dfsg-7+rpi1) ...
Selecting previously unselected package libgmp-dev:armhf.
Preparing to unpack .../libgmp-dev_2%3a6.0.0+dfsg-7+rpi1_armhf.deb ...
Unpacking libgmp-dev:armhf (2:6.0.0+dfsg-7+rpi1) ...
Selecting previously unselected package ruby2.1-dev:armhf.
Preparing to unpack .../ruby2.1-dev_2.1.5-3_armhf.deb ...
Unpacking ruby2.1-dev:armhf (2.1.5-3) ...
Selecting previously unselected package ruby2.2-dev:armhf.
Preparing to unpack .../ruby2.2-dev_2.2.2-2_armhf.deb ...
Unpacking ruby2.2-dev:armhf (2.2.2-2) ...
Selecting previously unselected package ruby-all-dev.
Preparing to unpack .../ruby-all-dev_1%3a2.1.5.1_all.deb ...
Unpacking ruby-all-dev (1:2.1.5.1) ...
Selecting previously unselected package ruby-setup.
Preparing to unpack .../ruby-setup_3.4.1-9_all.deb ...
Unpacking ruby-setup (3.4.1-9) ...
Selecting previously unselected package gem2deb.
Preparing to unpack .../gem2deb_0.18.3_all.deb ...
Unpacking gem2deb (0.18.3) ...
Selecting previously unselected package ruby-diff-lcs.
Preparing to unpack .../ruby-diff-lcs_1.2.5-1_all.deb ...
Unpacking ruby-diff-lcs (1.2.5-1) ...
Selecting previously unselected package ruby-rspec-support.
Preparing to unpack .../ruby-rspec-support_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec-support (3.3.0c0e0m0s0-1) ...
Selecting previously unselected package ruby-rspec-expectations.
Preparing to unpack .../ruby-rspec-expectations_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec-expectations (3.3.0c0e0m0s0-1) ...
Selecting previously unselected package ruby-rspec-mocks.
Preparing to unpack .../ruby-rspec-mocks_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec-mocks (3.3.0c0e0m0s0-1) ...
Selecting previously unselected package ruby-thread-order.
Preparing to unpack .../ruby-thread-order_1.1.0-1_all.deb ...
Unpacking ruby-thread-order (1.1.0-1) ...
Selecting previously unselected package ruby-rspec-core.
Preparing to unpack .../ruby-rspec-core_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec-core (3.3.0c0e0m0s0-1) ...
Selecting previously unselected package ruby-rspec.
Preparing to unpack .../ruby-rspec_3.3.0c0e0m0s0-1_all.deb ...
Unpacking ruby-rspec (3.3.0c0e0m0s0-1) ...
Selecting previously unselected package sbuild-build-depends-ruby-yajl-dummy.
Preparing to unpack .../sbuild-build-depends-ruby-yajl-dummy.deb ...
Unpacking sbuild-build-depends-ruby-yajl-dummy (0.invalid.0) ...
Setting up libpipeline1:armhf (1.4.0-1) ...
Setting up groff-base (1.22.3-1) ...
Setting up bsdmainutils (9.0.6) ...
update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write) in auto mode
update-alternatives: using /usr/bin/bsd-from to provide /usr/bin/from (from) in auto mode
Setting up man-db (2.7.0.2-5) ...
Not building database; man-db/auto-update is not 'true'.
Setting up libasprintf0c2:armhf (0.19.4-1) ...
Setting up libmagic1:armhf (1:5.22+15-2) ...
Setting up libxml2:armhf (2.9.1+dfsg1-5) ...
Setting up libffi6:armhf (3.1-2) ...
Setting up libglib2.0-0:armhf (2.44.1-1.1) ...
No schema files found: doing nothing.
Setting up libcroco3:armhf (0.6.8-3) ...
Setting up libmpdec2:armhf (2.4.1-1) ...
Setting up mime-support (3.58) ...
Setting up libsqlite3-0:armhf (3.8.10.2-1) ...
Setting up libpython3.4-stdlib:armhf (3.4.3-7) ...
Setting up libunistring0:armhf (0.9.3-5.2) ...
Setting up libyaml-0-2:armhf (0.1.6-3) ...
Setting up python3.4 (3.4.3-7) ...
Setting up libpython3-stdlib:armhf (3.4.3-4) ...
Setting up file (1:5.22+15-2) ...
Setting up gettext-base (0.19.4-1) ...
Setting up openssl (1.0.2d-1) ...
Setting up ca-certificates (20150426) ...
Setting up gettext (0.19.4-1) ...
Setting up intltool-debian (0.35.0+20060710.2) ...
Setting up po-debconf (1.0.18) ...
Setting up debhelper (9.20150628) ...
Setting up rubygems-integration (1.9) ...
Setting up libgmp10:armhf (2:6.0.0+dfsg-7+rpi1) ...
Setting up libruby2.1:armhf (2.1.5-3) ...
Setting up ruby2.1 (2.1.5-3) ...
Setting up ruby (1:2.1.5.1) ...
Setting up libruby2.2:armhf (2.2.2-2) ...
Setting up ruby2.2 (2.2.2-2) ...
Setting up ruby-power-assert (0.2.3-1) ...
Setting up ruby-test-unit (3.1.2-1) ...
Setting up gem2deb-test-runner (0.18.3) ...
Setting up libgmpxx4ldbl:armhf (2:6.0.0+dfsg-7+rpi1) ...
Setting up libgmp-dev:armhf (2:6.0.0+dfsg-7+rpi1) ...
Setting up ruby2.1-dev:armhf (2.1.5-3) ...
Setting up ruby2.2-dev:armhf (2.2.2-2) ...
Setting up ruby-all-dev (1:2.1.5.1) ...
Setting up ruby-setup (3.4.1-9) ...
Setting up ruby-diff-lcs (1.2.5-1) ...
Setting up ruby-rspec-support (3.3.0c0e0m0s0-1) ...
Setting up ruby-rspec-expectations (3.3.0c0e0m0s0-1) ...
Setting up ruby-rspec-mocks (3.3.0c0e0m0s0-1) ...
Setting up ruby-thread-order (1.1.0-1) ...
Setting up ruby-rspec-core (3.3.0c0e0m0s0-1) ...
Setting up ruby-rspec (3.3.0c0e0m0s0-1) ...
Setting up dh-python (1.20150705-1) ...
Setting up python3 (3.4.3-4) ...
Setting up devscripts (2.15.5) ...
Setting up python3-pkg-resources (17.0-1) ...
Setting up python3-chardet (2.3.0-1) ...
Setting up python3-six (1.9.0-3) ...
Setting up python3-debian (0.1.27) ...
Setting up gem2deb (0.18.3) ...
Setting up sbuild-build-depends-ruby-yajl-dummy (0.invalid.0) ...
Processing triggers for libc-bin (2.19-18) ...
Processing triggers for ca-certificates (20150426) ...
Updating certificates in /etc/ssl/certs...
180 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
┌──────────────────────────────────────────────────────────────────────────────┐
│ Build environment │
└──────────────────────────────────────────────────────────────────────────────┘
Kernel: Linux 3.19.0-trunk-armmp armhf (armv7l)
Toolchain package versions: binutils_2.25-5 dpkg-dev_1.17.25 g++-4.9_4.9.2-10 gcc-4.9_4.9.2-10 libc6-dev_2.19-18 libstdc++-4.9-dev_4.9.2-10 libstdc++6_4.9.2-10 linux-libc-dev_3.16.7-ckt4-1+rpi1
Package versions: acl_2.2.52-2 adduser_3.113+nmu3 apt_1.0.9.8 base-files_8+rpi1 base-passwd_3.5.37 bash_4.3-11 binutils_2.25-5 bsdmainutils_9.0.6 bsdutils_1:2.25.2-6 build-essential_11.7 bzip2_1.0.6-7 ca-certificates_20150426 coreutils_8.23-4 cpio_2.11+dfsg-4.1 cpp_4:4.9.2-2 cpp-4.9_4.9.2-10 dash_0.5.7-4 debconf_1.5.56 debconf-i18n_1.5.56 debfoster_2.7-2 debhelper_9.20150628 debianutils_4.4 devscripts_2.15.5 dh-python_1.20150705-1 diffutils_1:3.3-1 dmsetup_2:1.02.90-2.2 dpkg_1.17.25 dpkg-dev_1.17.25 e2fslibs_1.42.12-1.1 e2fsprogs_1.42.12-1.1 fakeroot_1.20.2-1 file_1:5.22+15-2 findutils_4.4.2-9 g++_4:4.9.2-2 g++-4.9_4.9.2-10 gcc_4:4.9.2-2 gcc-4.6-base_4.6.4-5+rpi1 gcc-4.7-base_4.7.3-11+rpi1 gcc-4.8-base_4.8.4-1 gcc-4.9_4.9.2-10 gcc-4.9-base_4.9.2-10 gem2deb_0.18.3 gem2deb-test-runner_0.18.3 gettext_0.19.4-1 gettext-base_0.19.4-1 gnupg_1.4.18-7 gpgv_1.4.18-7 grep_2.20-4.1 groff-base_1.22.3-1 gzip_1.6-4 hostname_3.15 init_1.22 init-system-helpers_1.22 initramfs-tools_0.120 initscripts_2.88dsf-59 insserv_1.14.0-5 intltool-debian_0.35.0+20060710.2 klibc-utils_2.0.4-2+rpi1 kmod_18-3 libacl1_2.2.52-2 libapt-pkg4.12_1.0.9.8 libasan1_4.9.2-10 libasprintf0c2_0.19.4-1 libatomic1_4.9.2-10 libattr1_1:2.4.47-2 libaudit-common_1:2.4-1 libaudit1_1:2.4-1 libblkid1_2.25.2-6 libbz2-1.0_1.0.6-7 libc-bin_2.19-18 libc-dev-bin_2.19-18 libc6_2.19-18 libc6-dev_2.19-18 libcap2_1:2.24-8 libcap2-bin_1:2.24-8 libcloog-isl4_0.18.2-1 libcomerr2_1.42.12-1.1 libcroco3_0.6.8-3 libcryptsetup4_2:1.6.6-5 libdb5.3_5.3.28-9 libdbus-1-3_1.8.16-1 libdebconfclient0_0.192 libdevmapper1.02.1_2:1.02.90-2.2 libdpkg-perl_1.17.25 libdrm2_2.4.58-2 libexpat1_2.1.0-6 libfakeroot_1.20.2-1 libffi6_3.1-2 libgc1c2_1:7.2d-6.4 libgcc-4.9-dev_4.9.2-10 libgcc1_1:4.9.2-10 libgcrypt20_1.6.3-2 libgdbm3_1.8.3-13.1 libglib2.0-0_2.44.1-1.1 libgmp-dev_2:6.0.0+dfsg-7+rpi1 libgmp10_2:6.0.0+dfsg-7+rpi1 libgmpxx4ldbl_2:6.0.0+dfsg-7+rpi1 libgomp1_4.9.2-10 libgpg-error0_1.17-3 libisl10_0.12.2-2 libklibc_2.0.4-2+rpi1 libkmod2_18-3 liblocale-gettext-perl_1.05-8+b1 liblzma5_5.1.1alpha+20120614-2 libmagic1_1:5.22+15-2 libmount1_2.25.2-6 libmpc3_1.0.2-1 libmpdec2_2.4.1-1 libmpfr4_3.1.2-2 libncurses5_5.9+20140913-1 libncursesw5_5.9+20140913-1 libnih-dbus1_1.0.3-4.3 libnih1_1.0.3-4.3 libpam-modules_1.1.8-3.1 libpam-modules-bin_1.1.8-3.1 libpam-runtime_1.1.8-3.1 libpam0g_1.1.8-3.1 libpcre3_2:8.35-3.3 libpipeline1_1.4.0-1 libpng12-0_1.2.50-2 libprocps3_2:3.3.9-9 libpython3-stdlib_3.4.3-4 libpython3.4-minimal_3.4.3-7 libpython3.4-stdlib_3.4.3-7 libreadline6_6.3-8 libruby2.1_2.1.5-3 libruby2.2_2.2.2-2 libselinux1_2.3-2 libsemanage-common_2.3-1 libsemanage1_2.3-1 libsepol1_2.3-2 libslang2_2.3.0-2 libsmartcols1_2.25.2-6 libsqlite3-0_3.8.10.2-1 libss2_1.42.12-1.1 libssl1.0.0_1.0.2d-1 libstdc++-4.9-dev_4.9.2-10 libstdc++6_4.9.2-10 libsystemd0_215-17 libtext-charwidth-perl_0.04-7+b4 libtext-iconv-perl_1.7-5+b5 libtext-wrapi18n-perl_0.06-7 libtimedate-perl_2.3000-2 libtinfo5_5.9+20140913-1 libubsan0_4.9.2-10 libudev1_215-17 libunistring0_0.9.3-5.2 libusb-0.1-4_2:0.1.12-25 libustr-1.0-1_1.0.4-3 libuuid1_2.25.2-6 libxml2_2.9.1+dfsg1-5 libyaml-0-2_0.1.6-3 linux-libc-dev_3.16.7-ckt4-1+rpi1 login_1:4.2-3 lsb-base_4.1+Debian13+rpi1+nmu1 make_4.0-8.1 makedev_2.3.1-93 man-db_2.7.0.2-5 mawk_1.3.3-17 mime-support_3.58 mount_2.25.2-6 mountall_2.54 multiarch-support_2.19-18 ncurses-base_5.9+20140913-1 ncurses-bin_5.9+20140913-1 openssl_1.0.2d-1 passwd_1:4.2-3 patch_2.7.5-1 perl_5.20.2-3 perl-base_5.20.2-3 perl-modules_5.20.2-3 plymouth_0.9.0-9 po-debconf_1.0.18 procps_2:3.3.9-9 python3_3.4.3-4 python3-chardet_2.3.0-1 python3-debian_0.1.27 python3-minimal_3.4.3-4 python3-pkg-resources_17.0-1 python3-six_1.9.0-3 python3.4_3.4.3-7 python3.4-minimal_3.4.3-7 raspbian-archive-keyring_20120528.2 readline-common_6.3-8 ruby_1:2.1.5.1 ruby-all-dev_1:2.1.5.1 ruby-diff-lcs_1.2.5-1 ruby-power-assert_0.2.3-1 ruby-rspec_3.3.0c0e0m0s0-1 ruby-rspec-core_3.3.0c0e0m0s0-1 ruby-rspec-expectations_3.3.0c0e0m0s0-1 ruby-rspec-mocks_3.3.0c0e0m0s0-1 ruby-rspec-support_3.3.0c0e0m0s0-1 ruby-setup_3.4.1-9 ruby-test-unit_3.1.2-1 ruby-thread-order_1.1.0-1 ruby2.1_2.1.5-3 ruby2.1-dev_2.1.5-3 ruby2.2_2.2.2-2 ruby2.2-dev_2.2.2-2 rubygems-integration_1.9 sbuild-build-depends-core-dummy_0.invalid.0 sbuild-build-depends-ruby-yajl-dummy_0.invalid.0 sed_4.2.2-4 sensible-utils_0.0.9 startpar_0.59-3 systemd_215-17 systemd-sysv_215-17 sysv-rc_2.88dsf-59 sysvinit-utils_2.88dsf-59 tar_1.27.1-2 tzdata_2015c-1 udev_215-17 util-linux_2.25.2-6 xz-utils_5.1.1alpha+20120614-2 zlib1g_1:1.2.8.dfsg-2
┌──────────────────────────────────────────────────────────────────────────────┐
│ Build │
└──────────────────────────────────────────────────────────────────────────────┘
Unpack source
─────────────
gpgv: keyblock resource `/sbuild-nonexistent/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made Wed Jul 8 14:53:08 2015 UTC using RSA key ID 93052E03
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./ruby-yajl_1.2.0-3.dsc
dpkg-source: info: extracting ruby-yajl in ruby-yajl-1.2.0
dpkg-source: info: unpacking ruby-yajl_1.2.0.orig.tar.gz
dpkg-source: info: unpacking ruby-yajl_1.2.0-3.debian.tar.xz
dpkg-source: info: applying mocks-test-fix
dpkg-source: info: applying RSpec3-test-fix
Check disc space
────────────────
Sufficient free space for build
User Environment
────────────────
DEB_BUILD_OPTIONS=parallel=4
HOME=/sbuild-nonexistent
LOGNAME=buildd
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=stretch-staging-armhf-sbuild
SCHROOT_CHROOT_NAME=stretch-staging-armhf-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=109
SCHROOT_GROUP=buildd
SCHROOT_SESSION_ID=stretch-staging-armhf-sbuild-7b8de8a2-0f23-46ce-b977-f5b9149e1e70
SCHROOT_UID=104
SCHROOT_USER=buildd
SHELL=/bin/sh
TERM=linux
USER=buildd
dpkg-buildpackage
─────────────────
dpkg-buildpackage: source package ruby-yajl
dpkg-buildpackage: source version 1.2.0-3
dpkg-buildpackage: source distribution unstable
dpkg-source --before-build ruby-yajl-1.2.0
dpkg-buildpackage: host architecture armhf
fakeroot debian/rules clean
dh clean --buildsystem=ruby --with ruby
dh_testdir -O--buildsystem=ruby
dh_auto_clean -O--buildsystem=ruby
dh_ruby --clean
dh_ruby --clean
dh_clean -O--buildsystem=ruby
debian/rules build-arch
dh build-arch --buildsystem=ruby --with ruby
dh_testdir -a -O--buildsystem=ruby
dh_auto_configure -a -O--buildsystem=ruby
dh_ruby --configure
dh_auto_build -a -O--buildsystem=ruby
dh_ruby --build
dh_ruby --build
dh_auto_test -a -O--buildsystem=ruby
dh_ruby --test
fakeroot debian/rules binary-arch
dh binary-arch --buildsystem=ruby --with ruby
dh_testroot -a -O--buildsystem=ruby
dh_prep -a -O--buildsystem=ruby
dh_auto_install -a -O--buildsystem=ruby
dh_ruby --install /«PKGBUILDDIR»/debian/ruby-yajl
dh_ruby --install
install -d /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby
install -D -m644 /«PKGBUILDDIR»/lib/yajl.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/http_stream.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/http_stream.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/bzip2.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/bzip2.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/gzip.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/gzip.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/gzip/stream_writer.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/gzip/stream_writer.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/gzip/stream_reader.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/gzip/stream_reader.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/deflate/stream_writer.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/deflate/stream_writer.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/deflate/stream_reader.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/deflate/stream_reader.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/version.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/version.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/deflate.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/deflate.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/json_gem/encoding.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/json_gem/encoding.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/json_gem/parsing.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/json_gem/parsing.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/json_gem.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/json_gem.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/bzip2/stream_writer.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_writer.rb
install -D -m644 /«PKGBUILDDIR»/lib/yajl/bzip2/stream_reader.rb /«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_reader.rb
Building extension for ruby2.1 ...
/usr/bin/ruby2.1 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /«PKGBUILDDIR» debian/ruby-yajl
/usr/bin/ruby2.1 extconf.rb
creating Makefile
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
rm -f
rm -f yajl.so *.o *.bak mkmf.log .*.time
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
make V=1 "DESTDIR="
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_buf.o -c yajl_buf.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_alloc.o -c yajl_alloc.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_version.o -c yajl_version.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_ext.o -c yajl_ext.c
yajl_ext.c: In function 'rb_yajl_parser_parse':
yajl_ext.c:472:17: warning: variable 'stat' set but not used [-Wunused-but-set-variable]
yajl_status stat;
^
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_gen.o -c yajl_gen.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_lex.o -c yajl_lex.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl.o -c yajl.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_parser.o -c yajl_parser.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.1.0 -I/usr/include/ruby-2.1.0/ruby/backward -I/usr/include/ruby-2.1.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_encode.o -c yajl_encode.c
rm -f yajl.so
gcc -shared -o yajl.so yajl_buf.o yajl_alloc.o yajl_version.o yajl_ext.o yajl_gen.o yajl_lex.o yajl.o yajl_parser.o yajl_encode.o -L. -L/usr/lib/arm-linux-gnueabihf -L. -Wl,-z,relro -L/build/ruby2.1-JN5Nw1/ruby2.1-2.1.5/debian/lib -fstack-protector -rdynamic -Wl,-export-dynamic -lruby-2.1 -lpthread -lgmp -ldl -lcrypt -lm -lc
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
make V=1 "DESTDIR=" install
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
/bin/mkdir -p . ./.gem.20150714-21257-njc1ih/yajl
exit > .RUBYARCHDIR.-.yajl.time
/usr/bin/install -c -m 0755 yajl.so ./.gem.20150714-21257-njc1ih/yajl
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
Building extension for ruby2.2 ...
/usr/bin/ruby2.2 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /«PKGBUILDDIR» debian/ruby-yajl
"make clean"
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
"make clean"
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
/usr/bin/ruby2.2 -r ./siteconf20150714-21318-wv9eqh.rb extconf.rb
creating Makefile
make V=1 "DESTDIR=" clean
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
rm -f
rm -f yajl.so *.o *.bak mkmf.log .*.time
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
make V=1 "DESTDIR="
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_buf.o -c yajl_buf.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_alloc.o -c yajl_alloc.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_version.o -c yajl_version.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_ext.o -c yajl_ext.c
yajl_ext.c: In function 'rb_yajl_parser_parse':
yajl_ext.c:472:17: warning: variable 'stat' set but not used [-Wunused-but-set-variable]
yajl_status stat;
^
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_gen.o -c yajl_gen.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_lex.o -c yajl_lex.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl.o -c yajl.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_parser.o -c yajl_parser.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.2.0 -I/usr/include/ruby-2.2.0/ruby/backward -I/usr/include/ruby-2.2.0 -I. -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_encode.o -c yajl_encode.c
rm -f yajl.so
gcc -shared -o yajl.so yajl_buf.o yajl_alloc.o yajl_version.o yajl_ext.o yajl_gen.o yajl_lex.o yajl.o yajl_parser.o yajl_encode.o -L. -L/usr/lib/arm-linux-gnueabihf -L. -Wl,-z,relro -L/build/ruby2.2-vZsPRs/ruby2.2-2.2.2/debian/lib -fstack-protector -rdynamic -Wl,-export-dynamic -lruby-2.2 -lpthread -lgmp -ldl -lcrypt -lm -lc
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
make V=1 "DESTDIR=" install
make[1]: Entering directory '/«PKGBUILDDIR»/ext/yajl'
/bin/mkdir -p . ./.gem.20150714-21318-lqks2r/yajl
exit > .RUBYARCHDIR.-.yajl.time
/usr/bin/install -c -m 0755 yajl.so ./.gem.20150714-21318-lqks2r/yajl
make[1]: Leaving directory '/«PKGBUILDDIR»/ext/yajl'
dh_installchangelogs -pruby-yajl /«PKGBUILDDIR»/CHANGELOG.md upstream
generating gemspec at /«PKGBUILDDIR»/debian/ruby-yajl/usr/share/rubygems-integration/2.1.0/specifications/yajl-ruby-1.2.0.gemspec
generating gemspec at /«PKGBUILDDIR»/debian/ruby-yajl/usr/share/rubygems-integration/2.2.0/specifications/yajl-ruby-1.2.0.gemspec
/usr/bin/ruby2.1 /usr/bin/gem2deb-test-runner
Running tests for ruby2.1 using debian/ruby-tests.rb...
RUBYLIB=/«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0:/«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby:. ruby2.1 debian/ruby-tests.rb
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Gzip support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Deflate support is going to be removed in 2.0
DEPRECATION WARNING: Yajl::HttpStream is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
Yajl JSON encoder
should encode ohai.json to an StringIO
should encode twitter_stream.json to an StringIO
should encode unicode.json to an StringIO
should encode twitter_search.json to an StringIO
should encode item.json to an StringIO
should encode ohai.json to a Zlib::GzipWriter
should encode twitter_stream.json to a Zlib::GzipWriter
should encode unicode.json to a Zlib::GzipWriter
should encode twitter_search.json to a Zlib::GzipWriter
should encode item.json to a Zlib::GzipWriter
should encode ohai.json and return a String
should encode twitter_stream.json and return a String
should encode unicode.json and return a String
should encode twitter_search.json and return a String
should encode item.json and return a String
should encode ohai.json call the passed block, passing it a String
should encode twitter_stream.json call the passed block, passing it a String
should encode unicode.json call the passed block, passing it a String
should encode twitter_search.json call the passed block, passing it a String
should encode item.json call the passed block, passing it a String
should encode with :pretty turned on and a single space indent, to an IO
should encode with :pretty turned on and a single space indent, and return a String
should encode with :pretty turned on and a tab character indent, to an IO
should encode with :pretty turned on and a tab character indent, and return a String
should encode with it's class method with :pretty and a tab character indent options set, to an IO
should encode with it's class method with :pretty and a tab character indent options set, and return a String
should encode with it's class method with :pretty and a tab character indent options set, to a block
should encode multiple objects into a single stream, to an IO
should encode multiple objects into a single stream, and return a String
should encode all map keys as strings
should check for and call #to_json if it exists on custom objects
should encode a hash where the key and value can be symbols
should encode using a newline or nil terminator
should encode using a newline or nil terminator, to an IO
should encode using a newline or nil terminator, using a block
should not encode NaN
should not encode Infinity or -Infinity
should encode with unicode chars in the key
should be able to escape / characters if html_safe is enabled
should default to *not* escaping / characters
return value of #to_json must be a string
return value of #to_s must be a string
should raise an exception for deeply nested arrays
should raise an exception for deeply nested hashes
Chunked parser
should parse a single chunk
should parse a single chunk, 3 times
should parse in two chunks
should parse in 2 chunks, twice
should parse 2 JSON strings, in 3 chunks
should parse 2 JSON strings in 1 chunk
should parse 2 JSON strings from an IO
should parse a JSON string an IO and fire callback once
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:68:in `block (2 levels) in <top (required)>'.
should parse twitter_stream.json and fire callback 430 times
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:78:in `block (2 levels) in <top (required)>'.
should parse twitter_stream.json and fire callback 430 times, with a block as the callback
should raise a Yajl::ParseError error if multiple JSON strings were found when no on_parse_complete callback assigned
One-off JSON examples
should parse 23456789012E666 and return Infinity
should not parse JSON with a comment, with :allow_comments set to false
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/one_off_spec.rb:21:in `block (2 levels) in <top (required)>'.
should parse JSON with a comment, with :allow_comments set to true
should not parse invalid UTF8 with :check_utf8 set to true
should parse invalid UTF8 with :check_utf8 set to false
should parse using it's class method, from an IO
should parse using it's class method, from a string with symbolized keys
should parse using it's class method, from a utf-8 string with multibyte characters, with symbolized keys
should parse using it's class method, from a string
should parse using it's class method, from a string with a block
should parse numbers greater than 2,147,483,648
Parsing JSON Fixtures
should not be able to parse fail.15.json as an IO
should not be able to parse fail.16.json as an IO
should not be able to parse fail.17.json as an IO
should not be able to parse fail.26.json as an IO
should not be able to parse fail11.json as an IO
should not be able to parse fail12.json as an IO
should not be able to parse fail13.json as an IO
should not be able to parse fail14.json as an IO
should not be able to parse fail19.json as an IO
should not be able to parse fail20.json as an IO
should not be able to parse fail21.json as an IO
should not be able to parse fail22.json as an IO
should not be able to parse fail23.json as an IO
should not be able to parse fail24.json as an IO
should not be able to parse fail25.json as an IO
should not be able to parse fail27.json as an IO
should not be able to parse fail28.json as an IO
should not be able to parse fail3.json as an IO
should not be able to parse fail4.json as an IO
should not be able to parse fail5.json as an IO
should not be able to parse fail6.json as an IO
should not be able to parse fail9.json as an IO
should not be able to parse fail.15.json as a string
should not be able to parse fail.16.json as a string
should not be able to parse fail.17.json as a string
should not be able to parse fail.26.json as a string
should not be able to parse fail11.json as a string
should not be able to parse fail12.json as a string
should not be able to parse fail13.json as a string
should not be able to parse fail14.json as a string
should not be able to parse fail19.json as a string
should not be able to parse fail20.json as a string
should not be able to parse fail21.json as a string
should not be able to parse fail22.json as a string
should not be able to parse fail23.json as a string
should not be able to parse fail24.json as a string
should not be able to parse fail25.json as a string
should not be able to parse fail27.json as a string
should not be able to parse fail28.json as a string
should not be able to parse fail3.json as a string
should not be able to parse fail4.json as a string
should not be able to parse fail5.json as a string
should not be able to parse fail6.json as a string
should not be able to parse fail9.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.contacts.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.doubles.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.item.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.unicode.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.yelp.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.contacts.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.doubles.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.item.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.unicode.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.yelp.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass3.json as a string
ActiveSupport test cases
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":"\/"}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"return\"To\":":{"\/categories":"\/"}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":1}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"a"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"\"a\",", "b"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "'", "b": "5,000"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "a's, b's and c's", "b": "5,000"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"matzue": "松江", "asakusa": "浅草"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34 Z"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": " 2007-01-01 01:12:34 Z "} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 : it's your birthday"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse [] as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":1} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": ""} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":"\""} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": null} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": true} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": false} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "http:\/\/test.host\/posts\/1"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cunicode\u0020escape\u003e"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\\u0020skip double backslashes"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cbr /\u003e"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"b":["\u003ci\u003e","\u003cb\u003e","\u003cu\u003e"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":"\/"}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"return\"To\":":{"\/categories":"\/"}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":1}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"a"]} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"\"a\",", "b"]} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "'", "b": "5,000"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "a's, b's and c's", "b": "5,000"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"matzue": "松江", "asakusa": "浅草"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01"} as a string
should be able to parse {"a": "2007-01-01 01:12:34 Z"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34"} as a string
should be able to parse {"a": " 2007-01-01 01:12:34 Z "} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 : it's your birthday"} as a string
should be able to parse [] as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":1} as a string
should be able to parse {"a": ""} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":"\""} as a string
should be able to parse {"a": null} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": true} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": false} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "http:\/\/test.host\/posts\/1"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cunicode\u0020escape\u003e"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\\u0020skip double backslashes"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cbr /\u003e"} as a string
should be able to parse {"b":["\u003ci\u003e","\u003cb\u003e","\u003cu\u003e"]} as a string
should fail parsing {: 1} as an IO
should fail parsing {: 1} as a string
Yajl HTTP POST request
should parse a raw response
should parse a raw response using instance method
should parse a raw response with hashed body
should parse a raw response and symbolize keys
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should parse a chunked raw response
should throw Exception if chunked response and no block given
should throw InvalidContentType if unable to handle the MIME type
should raise when an HTTP code that isn't 200 is returned
Yajl HTTP PUT request
should parse a raw response
should parse a raw response using instance method
should parse a raw response with hashed body
should parse a raw response and symbolize keys
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should raise when an HTTP code that isn't 200 is returned
Yajl HTTP DELETE request
should parse a raw response
should parse a raw response using instance method
should parse a raw response and symbolize keys
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should raise when an HTTP code that isn't 200 is returned
Passing options to HttpStream instance methods
should not create a new socket it one is provided
should create a new socket if one is not provided
Yajl HTTP GET request
should parse a raw response
should parse a raw response and symbolize keys
should parse a raw response using instance method
should parse a chunked response using instance method
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should raise when an HTTP code that isn't 200 is returned
Yajl HTTP error
should contain the error code in the message
should provide the HTTP response headers
Yajl
dump
should exist as a class-method
should be able to encode to a string
should be able to encode to an IO
should be able to encode with a block supplied
load
should exist as a class-method
should be able to parse from a string
should be able to parse from an IO
should be able to parse from a string with a block supplied
should be able to parse from an IO with a block supplied
JSON Gem compatability API
shoud not mixin #to_json on base objects until compatability has been enabled
should mixin #to_json on base objects after compatability has been enabled
should require yajl/json_gem to enable the compatability API
should allow default parsing options be set with JSON.default_options
should also allow the json gem's symbolize_names key
should encode arbitrary classes via their default to_json method
should have the standard parsing and encoding exceptions mapped
ported tests for Unicode
should be able to encode and parse unicode
ported tests for generation
should be able to unparse
should be able to unparse pretty
ported fixture tests
should not be able to parse fail.15.json as an IO
should not be able to parse fail.16.json as an IO
should not be able to parse fail.17.json as an IO
should not be able to parse fail.26.json as an IO
should not be able to parse fail11.json as an IO
should not be able to parse fail12.json as an IO
should not be able to parse fail13.json as an IO
should not be able to parse fail14.json as an IO
should not be able to parse fail19.json as an IO
should not be able to parse fail20.json as an IO
should not be able to parse fail21.json as an IO
should not be able to parse fail22.json as an IO
should not be able to parse fail23.json as an IO
should not be able to parse fail24.json as an IO
should not be able to parse fail25.json as an IO
should not be able to parse fail27.json as an IO
should not be able to parse fail28.json as an IO
should not be able to parse fail3.json as an IO
should not be able to parse fail4.json as an IO
should not be able to parse fail5.json as an IO
should not be able to parse fail6.json as an IO
should not be able to parse fail9.json as an IO
should not be able to parse fail.15.json as a string
should not be able to parse fail.16.json as a string
should not be able to parse fail.17.json as a string
should not be able to parse fail.26.json as a string
should not be able to parse fail11.json as a string
should not be able to parse fail12.json as a string
should not be able to parse fail13.json as a string
should not be able to parse fail14.json as a string
should not be able to parse fail19.json as a string
should not be able to parse fail20.json as a string
should not be able to parse fail21.json as a string
should not be able to parse fail22.json as a string
should not be able to parse fail23.json as a string
should not be able to parse fail24.json as a string
should not be able to parse fail25.json as a string
should not be able to parse fail27.json as a string
should not be able to parse fail28.json as a string
should not be able to parse fail3.json as a string
should not be able to parse fail4.json as a string
should not be able to parse fail5.json as a string
should not be able to parse fail6.json as a string
should not be able to parse fail9.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.contacts.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.doubles.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.item.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.unicode.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.yelp.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.contacts.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.doubles.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.item.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as a string
should be able to parse pass.ns-invoice100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.unicode.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.yelp.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass3.json as a string
Deprecation Warnings:
Using `should_receive` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:17:in `block (2 levels) in <top (required)>'.
Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /«PKGBUILDDIR»/spec/encoding/encoding_spec.rb:40:in `block (3 levels) in <top (required)>'.
If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.
2 deprecation warnings total
Finished in 6.26 seconds (files took 1.7 seconds to load)
409 examples, 0 failures
/usr/bin/ruby2.2 /usr/bin/gem2deb-test-runner
Running tests for ruby2.2 using debian/ruby-tests.rb...
RUBYLIB=/«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0:/«PKGBUILDDIR»/debian/ruby-yajl/usr/lib/ruby/vendor_ruby:. ruby2.2 debian/ruby-tests.rb
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
Couldn't load yajl/bzip2, maybe you don't have bzip2-ruby installed? Continuing without running bzip2 specs.
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Gzip support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Deflate support is going to be removed in 2.0
DEPRECATION WARNING: Yajl::HttpStream is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
DEPRECATION WARNING: Yajl's Bzip2 support is going to be removed in 2.0
Yajl JSON encoder
should encode ohai.json to an StringIO
should encode twitter_stream.json to an StringIO
should encode unicode.json to an StringIO
should encode twitter_search.json to an StringIO
should encode item.json to an StringIO
should encode ohai.json to a Zlib::GzipWriter
should encode twitter_stream.json to a Zlib::GzipWriter
should encode unicode.json to a Zlib::GzipWriter
should encode twitter_search.json to a Zlib::GzipWriter
should encode item.json to a Zlib::GzipWriter
should encode ohai.json and return a String
should encode twitter_stream.json and return a String
should encode unicode.json and return a String
should encode twitter_search.json and return a String
should encode item.json and return a String
should encode ohai.json call the passed block, passing it a String
should encode twitter_stream.json call the passed block, passing it a String
should encode unicode.json call the passed block, passing it a String
should encode twitter_search.json call the passed block, passing it a String
should encode item.json call the passed block, passing it a String
should encode with :pretty turned on and a single space indent, to an IO
should encode with :pretty turned on and a single space indent, and return a String
should encode with :pretty turned on and a tab character indent, to an IO
should encode with :pretty turned on and a tab character indent, and return a String
should encode with it's class method with :pretty and a tab character indent options set, to an IO
should encode with it's class method with :pretty and a tab character indent options set, and return a String
should encode with it's class method with :pretty and a tab character indent options set, to a block
should encode multiple objects into a single stream, to an IO
should encode multiple objects into a single stream, and return a String
should encode all map keys as strings
should check for and call #to_json if it exists on custom objects
should encode a hash where the key and value can be symbols
should encode using a newline or nil terminator
should encode using a newline or nil terminator, to an IO
should encode using a newline or nil terminator, using a block
should not encode NaN
should not encode Infinity or -Infinity
should encode with unicode chars in the key
should be able to escape / characters if html_safe is enabled
should default to *not* escaping / characters
return value of #to_json must be a string
return value of #to_s must be a string
should raise an exception for deeply nested arrays
should raise an exception for deeply nested hashes
Chunked parser
should parse a single chunk
should parse a single chunk, 3 times
should parse in two chunks
should parse in 2 chunks, twice
should parse 2 JSON strings, in 3 chunks
should parse 2 JSON strings in 1 chunk
should parse 2 JSON strings from an IO
should parse a JSON string an IO and fire callback once
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:68:in `block (2 levels) in <top (required)>'.
should parse twitter_stream.json and fire callback 430 times
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:78:in `block (2 levels) in <top (required)>'.
should parse twitter_stream.json and fire callback 430 times, with a block as the callback
should raise a Yajl::ParseError error if multiple JSON strings were found when no on_parse_complete callback assigned
One-off JSON examples
should parse 23456789012E666 and return Infinity
should not parse JSON with a comment, with :allow_comments set to false
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/one_off_spec.rb:21:in `block (2 levels) in <top (required)>'.
should parse JSON with a comment, with :allow_comments set to true
should not parse invalid UTF8 with :check_utf8 set to true
should parse invalid UTF8 with :check_utf8 set to false
should parse using it's class method, from an IO
should parse using it's class method, from a string with symbolized keys
should parse using it's class method, from a utf-8 string with multibyte characters, with symbolized keys
should parse using it's class method, from a string
should parse using it's class method, from a string with a block
should parse numbers greater than 2,147,483,648
Parsing JSON Fixtures
should not be able to parse fail.15.json as an IO
should not be able to parse fail.16.json as an IO
should not be able to parse fail.17.json as an IO
should not be able to parse fail.26.json as an IO
should not be able to parse fail11.json as an IO
should not be able to parse fail12.json as an IO
should not be able to parse fail13.json as an IO
should not be able to parse fail14.json as an IO
should not be able to parse fail19.json as an IO
should not be able to parse fail20.json as an IO
should not be able to parse fail21.json as an IO
should not be able to parse fail22.json as an IO
should not be able to parse fail23.json as an IO
should not be able to parse fail24.json as an IO
should not be able to parse fail25.json as an IO
should not be able to parse fail27.json as an IO
should not be able to parse fail28.json as an IO
should not be able to parse fail3.json as an IO
should not be able to parse fail4.json as an IO
should not be able to parse fail5.json as an IO
should not be able to parse fail6.json as an IO
should not be able to parse fail9.json as an IO
should not be able to parse fail.15.json as a string
should not be able to parse fail.16.json as a string
should not be able to parse fail.17.json as a string
should not be able to parse fail.26.json as a string
should not be able to parse fail11.json as a string
should not be able to parse fail12.json as a string
should not be able to parse fail13.json as a string
should not be able to parse fail14.json as a string
should not be able to parse fail19.json as a string
should not be able to parse fail20.json as a string
should not be able to parse fail21.json as a string
should not be able to parse fail22.json as a string
should not be able to parse fail23.json as a string
should not be able to parse fail24.json as a string
should not be able to parse fail25.json as a string
should not be able to parse fail27.json as a string
should not be able to parse fail28.json as a string
should not be able to parse fail3.json as a string
should not be able to parse fail4.json as a string
should not be able to parse fail5.json as a string
should not be able to parse fail6.json as a string
should not be able to parse fail9.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.contacts.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.doubles.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.item.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.unicode.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass.yelp.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:27:in `block (3 levels) in <top (required)>'.
should be able to parse pass3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.contacts.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.doubles.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.item.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.unicode.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass.yelp.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/fixtures_spec.rb:35:in `block (3 levels) in <top (required)>'.
should be able to parse pass3.json as a string
ActiveSupport test cases
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":"\/"}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"return\"To\":":{"\/categories":"\/"}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":1}} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"a"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"\"a\",", "b"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "'", "b": "5,000"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "a's, b's and c's", "b": "5,000"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"matzue": "松江", "asakusa": "浅草"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34 Z"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": " 2007-01-01 01:12:34 Z "} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 : it's your birthday"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse [] as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":1} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": ""} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":"\""} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": null} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": true} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": false} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "http:\/\/test.host\/posts\/1"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cunicode\u0020escape\u003e"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\\u0020skip double backslashes"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cbr /\u003e"} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:39:in `block (3 levels) in <top (required)>'.
should be able to parse {"b":["\u003ci\u003e","\u003cb\u003e","\u003cu\u003e"]} as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":"\/"}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"return\"To\":":{"\/categories":"\/"}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":{"\/categories":1}} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"a"]} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"returnTo":[1,"\"a\",", "b"]} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "'", "b": "5,000"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "a's, b's and c's", "b": "5,000"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"matzue": "松江", "asakusa": "浅草"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34 Z"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 01:12:34"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": " 2007-01-01 01:12:34 Z "} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "2007-01-01 : it's your birthday"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse [] as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":1} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": ""} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a":"\""} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": null} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": true} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": false} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "http:\/\/test.host\/posts\/1"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cunicode\u0020escape\u003e"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\\u0020skip double backslashes"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"a": "\u003cbr /\u003e"} as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/parsing/active_support_spec.rb:47:in `block (3 levels) in <top (required)>'.
should be able to parse {"b":["\u003ci\u003e","\u003cb\u003e","\u003cu\u003e"]} as a string
should fail parsing {: 1} as an IO
should fail parsing {: 1} as a string
Yajl HTTP POST request
should parse a raw response
should parse a raw response using instance method
should parse a raw response with hashed body
should parse a raw response and symbolize keys
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should parse a chunked raw response
should throw Exception if chunked response and no block given
should throw InvalidContentType if unable to handle the MIME type
should raise when an HTTP code that isn't 200 is returned
Yajl HTTP PUT request
should parse a raw response
should parse a raw response using instance method
should parse a raw response with hashed body
should parse a raw response and symbolize keys
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should raise when an HTTP code that isn't 200 is returned
Yajl HTTP DELETE request
should parse a raw response
should parse a raw response using instance method
should parse a raw response and symbolize keys
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should raise when an HTTP code that isn't 200 is returned
Passing options to HttpStream instance methods
should not create a new socket it one is provided
should create a new socket if one is not provided
Yajl HTTP GET request
should parse a raw response
should parse a raw response and symbolize keys
should parse a raw response using instance method
should parse a chunked response using instance method
should parse a deflate compressed response
should parse a deflate compressed response and symbolize keys
should parse a gzip compressed response
should parse a gzip compressed response and symbolize keys
should raise when an HTTP code that isn't 200 is returned
Yajl HTTP error
should contain the error code in the message
should provide the HTTP response headers
Yajl
dump
should exist as a class-method
should be able to encode to a string
should be able to encode to an IO
should be able to encode with a block supplied
load
should exist as a class-method
should be able to parse from a string
should be able to parse from an IO
should be able to parse from a string with a block supplied
should be able to parse from an IO with a block supplied
JSON Gem compatability API
shoud not mixin #to_json on base objects until compatability has been enabled
should mixin #to_json on base objects after compatability has been enabled
should require yajl/json_gem to enable the compatability API
should allow default parsing options be set with JSON.default_options
should also allow the json gem's symbolize_names key
should encode arbitrary classes via their default to_json method
should have the standard parsing and encoding exceptions mapped
ported tests for Unicode
should be able to encode and parse unicode
ported tests for generation
should be able to unparse
should be able to unparse pretty
ported fixture tests
should not be able to parse fail.15.json as an IO
should not be able to parse fail.16.json as an IO
should not be able to parse fail.17.json as an IO
should not be able to parse fail.26.json as an IO
should not be able to parse fail11.json as an IO
should not be able to parse fail12.json as an IO
should not be able to parse fail13.json as an IO
should not be able to parse fail14.json as an IO
should not be able to parse fail19.json as an IO
should not be able to parse fail20.json as an IO
should not be able to parse fail21.json as an IO
should not be able to parse fail22.json as an IO
should not be able to parse fail23.json as an IO
should not be able to parse fail24.json as an IO
should not be able to parse fail25.json as an IO
should not be able to parse fail27.json as an IO
should not be able to parse fail28.json as an IO
should not be able to parse fail3.json as an IO
should not be able to parse fail4.json as an IO
should not be able to parse fail5.json as an IO
should not be able to parse fail6.json as an IO
should not be able to parse fail9.json as an IO
should not be able to parse fail.15.json as a string
should not be able to parse fail.16.json as a string
should not be able to parse fail.17.json as a string
should not be able to parse fail.26.json as a string
should not be able to parse fail11.json as a string
should not be able to parse fail12.json as a string
should not be able to parse fail13.json as a string
should not be able to parse fail14.json as a string
should not be able to parse fail19.json as a string
should not be able to parse fail20.json as a string
should not be able to parse fail21.json as a string
should not be able to parse fail22.json as a string
should not be able to parse fail23.json as a string
should not be able to parse fail24.json as a string
should not be able to parse fail25.json as a string
should not be able to parse fail27.json as a string
should not be able to parse fail28.json as a string
should not be able to parse fail3.json as a string
should not be able to parse fail4.json as a string
should not be able to parse fail5.json as a string
should not be able to parse fail6.json as a string
should not be able to parse fail9.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.contacts.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.doubles.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.item.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.unicode.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass.yelp.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass1.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass2.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:193:in `block (4 levels) in <top (required)>'.
should be able to parse pass3.json as an IO
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.codepoints_from_unicode_org.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.contacts.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.db1000.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.dc_simple_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.deep_arrays.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.difficult_json_c_test_case_with_comments.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.doubles.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_array.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.empty_string.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_bulgarian.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.escaped_foobar.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.item.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample3.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4-nows.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample4.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.json-org-sample5.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.map-spain.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-invoice100.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.ns-soap.xml.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-fp-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-4k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.numbers-int-64k.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.twitter-search2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.unicode.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass.yelp.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass1.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass2.json as a string
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect {}.not_to raise_error`. This message can be supressed by setting: `RSpec::Expectations.configuration.warn_about_potential_false_positives = false`. Called from /«PKGBUILDDIR»/spec/json_gem_compatibility/compatibility_spec.rb:201:in `block (4 levels) in <top (required)>'.
should be able to parse pass3.json as a string
Deprecation Warnings:
Using `should_receive` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /«PKGBUILDDIR»/spec/parsing/chunked_spec.rb:17:in `block (2 levels) in <top (required)>'.
Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /«PKGBUILDDIR»/spec/encoding/encoding_spec.rb:40:in `block (3 levels) in <top (required)>'.
If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.
2 deprecation warnings total
Finished in 6.07 seconds (files took 1.66 seconds to load)
409 examples, 0 failures
dh_installdocs -a -O--buildsystem=ruby
dh_ruby_fixdocs -a -O--buildsystem=ruby
debian/rules override_dh_installchangelogs
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_installchangelogs CHANGELOG.md
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_installexamples -a -O--buildsystem=ruby
dh_perl -a -O--buildsystem=ruby
dh_link -a -O--buildsystem=ruby
dh_compress -X.rb -a -O--buildsystem=ruby
dh_fixperms -a -O--buildsystem=ruby
dh_strip -a -O--buildsystem=ruby
dh_makeshlibs -a -O--buildsystem=ruby
dh_shlibdeps -a -O--buildsystem=ruby
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/yajl/yajl.so debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/yajl/yajl.so were not linked against libm.so.6 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/yajl/yajl.so debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/yajl/yajl.so were not linked against libgmp.so.10 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/yajl/yajl.so debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/yajl/yajl.so were not linked against libdl.so.2 (they use none of the library's symbols)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/yajl/yajl.so debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/yajl/yajl.so were not linked against libcrypt.so.1 (they use none of the library's symbols)
dh_ruby_fixdepends -a -O--buildsystem=ruby
dh_installdeb -a -O--buildsystem=ruby
dh_gencontrol -a -O--buildsystem=ruby
dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe
dh_md5sums -a -O--buildsystem=ruby
dh_builddeb -a -O--buildsystem=ruby
dpkg-deb: building package `ruby-yajl' in `../ruby-yajl_1.2.0-3_armhf.deb'.
dpkg-genchanges -B -mRaspbian wandboard test autobuilder <root@raspbian.org> >../ruby-yajl_1.2.0-3_armhf.changes
dpkg-genchanges: binary-only arch-specific upload (source code and arch-indep packages not included)
dpkg-source --after-build ruby-yajl-1.2.0
dpkg-buildpackage: binary-only upload (no source included)
────────────────────────────────────────────────────────────────────────────────
Build finished at 20150714-0859
Finished
────────
I: Built successfully
┌──────────────────────────────────────────────────────────────────────────────┐
│ Post Build Chroot │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ Changes │
└──────────────────────────────────────────────────────────────────────────────┘
ruby-yajl_1.2.0-3_armhf.changes:
────────────────────────────────
Format: 1.8
Date: Wed, 08 Jul 2015 16:51:20 +0200
Source: ruby-yajl
Binary: ruby-yajl
Architecture: armhf
Version: 1.2.0-3
Distribution: stretch-staging
Urgency: medium
Maintainer: Raspbian wandboard test autobuilder <root@raspbian.org>
Changed-By: Christian Hofstaedtler <zeha@debian.org>
Description:
ruby-yajl - Ruby interface to Yajl, a JSON stream-based parser library
Closes: 791775
Changes:
ruby-yajl (1.2.0-3) unstable; urgency=medium
.
[ Balasankar C ]
* Team upload
* Fix FTBFS by patching tests to support new versions of RSpec and mocks
(Closes: #791775)
* Add myself to Uploaders
.
[ Christian Hofstaedtler ]
* Set Standards-Version to 3.9.6 (no addtl. changes)
Checksums-Sha1:
f58580cb6019a9cfcd79295a7c6c8a7e7f85dbf0 40516 ruby-yajl_1.2.0-3_armhf.deb
Checksums-Sha256:
96dcd2354084008adf6ead18b90bc56a15dea4d1684e0723f6b66d32c96ed830 40516 ruby-yajl_1.2.0-3_armhf.deb
Files:
10dac419827624586e063782ff6f96b7 40516 ruby optional ruby-yajl_1.2.0-3_armhf.deb
┌──────────────────────────────────────────────────────────────────────────────┐
│ Package contents │
└──────────────────────────────────────────────────────────────────────────────┘
ruby-yajl_1.2.0-3_armhf.deb
───────────────────────────
new debian package, version 2.0.
size 40516 bytes: control archive=1864 bytes.
1057 bytes, 27 lines control
2641 bytes, 31 lines md5sums
Package: ruby-yajl
Version: 1.2.0-3
Architecture: armhf
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Installed-Size: 134
Depends: ruby (>= 1:2.1) | ruby (>= 1:2.2), libc6 (>= 2.4), libgmp10, libruby2.1 (>= 2.1.0) | libruby2.2 (>= 2.2.0~1)
Conflicts: libyajl-ruby
Replaces: libyajl-ruby
Section: ruby
Priority: optional
Homepage: http://github.com/brianmario/yajl-ruby
Description: Ruby interface to Yajl, a JSON stream-based parser library
Supported features include,
.
JSON parsing and encoding directly to and from an IO stream
(file, socket, etc) or String. Compressed stream parsing and
encoding supported for Bzip2, Gzip and Deflate.
.
Parse and encode *multiple* JSON objects to and from streams or strings
continuously.
.
JSON gem compatibility API - allows yajl-ruby to be used as a drop-in
replacement for the JSON gem
.
Basic HTTP client (only GET requests supported for now) which parses JSON
directly off the response body *as it's being received*
Ruby-Versions: ruby2.1 ruby2.2
drwxr-xr-x root/root 0 2015-07-14 08:59 ./
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/arm-linux-gnueabihf/
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/arm-linux-gnueabihf/ruby/
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/yajl/
-rw-r--r-- root/root 38436 2015-07-14 08:59 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.1.0/yajl/yajl.so
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/yajl/
-rw-r--r-- root/root 38444 2015-07-14 08:59 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.2.0/yajl/yajl.so
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/
-rw-r--r-- root/root 2654 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl.rb
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/
-rw-r--r-- root/root 355 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/bzip2.rb
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/
-rw-r--r-- root/root 899 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_reader.rb
-rw-r--r-- root/root 392 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_writer.rb
-rw-r--r-- root/root 243 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/deflate.rb
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/deflate/
-rw-r--r-- root/root 1334 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/deflate/stream_reader.rb
-rw-r--r-- root/root 546 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/deflate/stream_writer.rb
-rw-r--r-- root/root 234 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/gzip.rb
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/gzip/
-rw-r--r-- root/root 903 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/gzip/stream_reader.rb
-rw-r--r-- root/root 368 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/gzip/stream_writer.rb
-rw-r--r-- root/root 7376 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/http_stream.rb
-rw-r--r-- root/root 314 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/json_gem.rb
drwxr-xr-x root/root 0 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/
-rw-r--r-- root/root 1354 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/encoding.rb
-rw-r--r-- root/root 653 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/parsing.rb
-rw-r--r-- root/root 36 2015-07-14 08:58 ./usr/lib/ruby/vendor_ruby/yajl/version.rb
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/doc/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/doc/ruby-yajl/
-rw-r--r-- root/root 4990 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/README.md.gz
-rw-r--r-- root/root 1176 2015-07-08 14:51 ./usr/share/doc/ruby-yajl/changelog.Debian.gz
-rw-r--r-- root/root 7113 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/changelog.gz
-rw-r--r-- root/root 3063 2015-07-08 14:47 ./usr/share/doc/ruby-yajl/copyright
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/doc/ruby-yajl/examples/
drwxr-xr-x root/root 0 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/
-rw-r--r-- root/root 842 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/chunked_encoding.rb
-rw-r--r-- root/root 332 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/one_shot.rb
-rw-r--r-- root/root 338 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/encoding/to_an_io.rb
drwxr-xr-x root/root 0 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/http/
-rw-r--r-- root/root 389 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/http/twitter_search_api.rb
-rw-r--r-- root/root 714 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/http/twitter_stream_api.rb
drwxr-xr-x root/root 0 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/
-rw-r--r-- root/root 355 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/from_file.rb
-rw-r--r-- root/root 286 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/from_stdin.rb
-rw-r--r-- root/root 341 2013-12-19 14:41 ./usr/share/doc/ruby-yajl/examples/parsing/from_string.rb
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/rubygems-integration/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/rubygems-integration/2.1.0/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/rubygems-integration/2.1.0/specifications/
-rw-r--r-- root/root 10345 2015-07-14 08:59 ./usr/share/rubygems-integration/2.1.0/specifications/yajl-ruby-1.2.0.gemspec
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/rubygems-integration/2.2.0/
drwxr-xr-x root/root 0 2015-07-14 08:59 ./usr/share/rubygems-integration/2.2.0/specifications/
-rw-r--r-- root/root 10345 2015-07-14 08:59 ./usr/share/rubygems-integration/2.2.0/specifications/yajl-ruby-1.2.0.gemspec
┌──────────────────────────────────────────────────────────────────────────────┐
│ Post Build │
└──────────────────────────────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────────────────────────────┐
│ Cleanup │
└──────────────────────────────────────────────────────────────────────────────┘
Purging /«BUILDDIR»
Not cleaning session: cloned chroot in use
┌──────────────────────────────────────────────────────────────────────────────┐
│ Summary │
└──────────────────────────────────────────────────────────────────────────────┘
Build Architecture: armhf
Build-Space: 4632
Build-Time: 90
Distribution: stretch-staging
Host Architecture: armhf
Install-Time: 454
Job: ruby-yajl_1.2.0-3
Machine Architecture: armhf
Package: ruby-yajl
Package-Time: 619
Source-Version: 1.2.0-3
Space: 4632
Status: successful
Version: 1.2.0-3
────────────────────────────────────────────────────────────────────────────────
Finished at 20150714-0859
Build needed 00:10:19, 4632k disc space