ruby-yajl →
1.2.0-3.1 →
armhf → 2017-11-13 07:19:37
sbuild (Debian sbuild) 0.71.0 (24 Aug 2016) on bm-wb-02
+==============================================================================+
| ruby-yajl 1.2.0-3.1 (armhf) Mon, 13 Nov 2017 07:10:37 +0000 |
+==============================================================================+
Package: ruby-yajl
Version: 1.2.0-3.1
Source Version: 1.2.0-3.1
Distribution: buster-staging
Machine Architecture: armhf
Host Architecture: armhf
Build Architecture: armhf
I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/buster-staging-armhf-sbuild-c571f5e6-4bea-4771-beef-2f1b19799a16' with '<<CHROOT>>'
+------------------------------------------------------------------------------+
| Update chroot |
+------------------------------------------------------------------------------+
Get:1 http://172.17.0.1/private buster-staging InRelease [11.3 kB]
Get:2 http://172.17.0.1/private buster-staging/main Sources [10.3 MB]
Get:3 http://172.17.0.1/private buster-staging/main armhf Packages [12.2 MB]
Fetched 22.5 MB in 24s (918 kB/s)
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument
W: store: aptMethod::Configuration: could not load seccomp policy: Invalid argument
+------------------------------------------------------------------------------+
| Fetch source files |
+------------------------------------------------------------------------------+
Check APT
---------
Checking available source versions...
Download source files with APT
------------------------------
Reading package lists...
NOTICE: 'ruby-yajl' packaging is maintained in the 'Git' version control system at:
git://anonscm.debian.org/pkg-ruby-extras/ruby-yajl.git
Please use:
git clone git://anonscm.debian.org/pkg-ruby-extras/ruby-yajl.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 581 kB of source archives.
Get:1 http://172.17.0.1/private buster-staging/main ruby-yajl 1.2.0-3.1 (dsc) [2316 B]
Get:2 http://172.17.0.1/private buster-staging/main ruby-yajl 1.2.0-3.1 (tar) [573 kB]
Get:3 http://172.17.0.1/private buster-staging/main ruby-yajl 1.2.0-3.1 (diff) [6048 B]
Fetched 581 kB in 0s (1416 kB/s)
Download complete and in download only mode
W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument
I: NOTICE: Log filtering will replace 'build/ruby-yajl-E1pqd0/ruby-yajl-1.2.0' with '<<PKGBUILDDIR>>'
I: NOTICE: Log filtering will replace 'build/ruby-yajl-E1pqd0' with '<<BUILDDIR>>'
+------------------------------------------------------------------------------+
| Install build-essential |
+------------------------------------------------------------------------------+
Setup apt archive
-----------------
Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive/sbuild-build-depends-core-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning: sbuild-build-depends-core-dummy
dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
gpg: keybox '/<<BUILDDIR>>/resolver-Ydg2v6/gpg/pubring.kbx' created
gpg: /<<BUILDDIR>>/resolver-Ydg2v6/gpg/trustdb.gpg: trustdb created
gpg: key 35506D9A48F77B2E: public key "Sbuild Signer (Sbuild Build Dependency Archive Key) <buildd-tools-devel@lists.alioth.debian.org>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: key 35506D9A48F77B2E: "Sbuild Signer (Sbuild Build Dependency Archive Key) <buildd-tools-devel@lists.alioth.debian.org>" not changed
gpg: key 35506D9A48F77B2E: secret key imported
gpg: Total number processed: 1
gpg: unchanged: 1
gpg: secret keys read: 1
gpg: secret keys imported: 1
gpg: using "Sbuild Signer" as default secret key for signing
Ign:1 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ InRelease
Get:2 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Release [957 B]
Get:3 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Release.gpg [370 B]
Get:4 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Sources [349 B]
Get:5 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Packages [431 B]
Fetched 2107 B in 0s (3063 B/s)
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
W: copy: aptMethod::Configuration: could not load seccomp policy: Invalid argument
W: store: aptMethod::Configuration: could not load seccomp policy: Invalid argument
Reading package lists...
Install core build dependencies (apt-based resolver)
----------------------------------------------------
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
ca-certificates e2fsprogs-l10n libsasl2-modules libssl1.1 openssl
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
Need to get 848 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ sbuild-build-depends-core-dummy 0.invalid.0 [848 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 848 B in 0s (0 B/s)
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 15098 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy_0.invalid.0_armhf.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
W: copy: aptMethod::Configuration: could not load seccomp policy: Invalid argument
+------------------------------------------------------------------------------+
| Check architectures |
+------------------------------------------------------------------------------+
Arch check ok (armhf included in any)
+------------------------------------------------------------------------------+
| Install package build dependencies |
+------------------------------------------------------------------------------+
Setup apt archive
-----------------
Merged Build-Depends: debhelper (>= 7.0.50~), gem2deb (>= 0.7.5~), ruby-rspec
Filtered Build-Depends: debhelper (>= 7.0.50~), gem2deb (>= 0.7.5~), ruby-rspec
dpkg-deb: building package 'sbuild-build-depends-ruby-yajl-dummy' in '/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive/sbuild-build-depends-ruby-yajl-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-ruby-yajl-dummy
dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
gpg: using "Sbuild Signer" as default secret key for signing
Ign:1 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ InRelease
Get:2 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Release [963 B]
Get:3 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Release.gpg [370 B]
Get:4 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Sources [512 B]
Get:5 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ Packages [594 B]
Fetched 2439 B in 0s (3440 B/s)
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
W: copy: aptMethod::Configuration: could not load seccomp policy: Invalid argument
W: store: aptMethod::Configuration: could not load seccomp policy: Invalid argument
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 packages were automatically installed and are no longer required:
e2fsprogs-l10n libsasl2-modules
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdmainutils debhelper devscripts
dh-autoreconf dh-python dh-strip-nondeterminism file gem2deb
gem2deb-test-runner gettext gettext-base groff-base intltool-debian
libarchive-zip-perl libbsd0 libcroco3 libexpat1 libfile-homedir-perl
libfile-stripnondeterminism-perl libfile-which-perl libglib2.0-0 libgmp-dev
libgmpxx4ldbl libicu57 libmagic-mgc libmagic1 libmpdec2 libpipeline1
libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib libruby2.3
libsigsegv2 libssl1.0.2 libtimedate-perl libtool libxml2 libyaml-0-2 m4
man-db mime-support po-debconf python3 python3-minimal python3.6
python3.6-minimal rake ruby ruby-all-dev ruby-did-you-mean ruby-diff-lcs
ruby-minitest ruby-net-telnet 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.3 ruby2.3-dev rubygems-integration
Suggested packages:
autoconf-archive gnu-standards autoconf-doc wamerican | wordlist whois
vacation dh-make dwz adequate autopkgtest bls-standalone bsd-mailx | mailx
check-all-the-things cvs-buildpackage devscripts-el diffoscope disorderfs
dose-extra duck faketime gnuplot how-can-i-help libauthen-sasl-perl
libfile-desktopentry-perl libnet-smtps-perl libterm-size-perl
libyaml-syck-perl mozilla-devscripts mutt piuparts quilt ratt reprotest
ssh-client svn-buildpackage w3m gettext-doc libasprintf-dev libgettextpo-dev
groff gmp-doc libgmp10-doc libmpfr-dev libtool-doc gfortran
| fortran95-compiler gcj-jdk m4-doc less www-browser libmail-box-perl
python3-doc python3-tk python3-venv python3.6-venv python3.6-doc
binfmt-support ri ruby-dev bundler
Recommended packages:
at dctrl-tools dput | dupload libdistro-info-perl libencode-locale-perl
libgit-wrapper-perl liblist-compare-perl liburi-perl libwww-perl
licensecheck lintian patchutils python3-apt python3-debian python3-magic
python3-requests python3-unidiff python3-xdg strace unzip wdiff wget | curl
debian-keyring equivs liblwp-protocol-https-perl libsoap-lite-perl apt-file
curl | wget | lynx-cur libarchive-cpio-perl libglib2.0-data shared-mime-info
xdg-user-dirs libltdl-dev libmail-sendmail-perl zip fonts-lato libjs-jquery
The following NEW packages will be installed:
autoconf automake autopoint autotools-dev bsdmainutils debhelper devscripts
dh-autoreconf dh-python dh-strip-nondeterminism file gem2deb
gem2deb-test-runner gettext gettext-base groff-base intltool-debian
libarchive-zip-perl libbsd0 libcroco3 libexpat1 libfile-homedir-perl
libfile-stripnondeterminism-perl libfile-which-perl libglib2.0-0 libgmp-dev
libgmpxx4ldbl libicu57 libmagic-mgc libmagic1 libmpdec2 libpipeline1
libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib libruby2.3
libsigsegv2 libssl1.0.2 libtimedate-perl libtool libxml2 libyaml-0-2 m4
man-db mime-support po-debconf python3 python3-minimal python3.6
python3.6-minimal rake ruby ruby-all-dev ruby-did-you-mean ruby-diff-lcs
ruby-minitest ruby-net-telnet 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.3 ruby2.3-dev rubygems-integration
sbuild-build-depends-ruby-yajl-dummy
0 upgraded, 70 newly installed, 0 to remove and 13 not upgraded.
Need to get 30.4 MB of archives.
After this operation, 114 MB of additional disk space will be used.
Get:1 copy:/<<BUILDDIR>>/resolver-Ydg2v6/apt_archive ./ sbuild-build-depends-ruby-yajl-dummy 0.invalid.0 [880 B]
Get:2 http://172.17.0.1/private buster-staging/main armhf groff-base armhf 1.22.3-9 [1005 kB]
Get:3 http://172.17.0.1/private buster-staging/main armhf libbsd0 armhf 0.8.6-3 [95.9 kB]
Get:4 http://172.17.0.1/private buster-staging/main armhf bsdmainutils armhf 9.0.14 [178 kB]
Get:5 http://172.17.0.1/private buster-staging/main armhf libpipeline1 armhf 1.4.2-1 [24.2 kB]
Get:6 http://172.17.0.1/private buster-staging/main armhf man-db armhf 2.7.6.1-2 [1014 kB]
Get:7 http://172.17.0.1/private buster-staging/main armhf libpython3.6-minimal armhf 3.6.3-1 [564 kB]
Get:8 http://172.17.0.1/private buster-staging/main armhf libexpat1 armhf 2.2.3-2 [73.6 kB]
Get:9 http://172.17.0.1/private buster-staging/main armhf python3.6-minimal armhf 3.6.3-1 [1232 kB]
Get:10 http://172.17.0.1/private buster-staging/main armhf python3-minimal armhf 3.6.3-2 [35.7 kB]
Get:11 http://172.17.0.1/private buster-staging/main armhf mime-support all 3.60 [36.7 kB]
Get:12 http://172.17.0.1/private buster-staging/main armhf libmpdec2 armhf 2.4.2-1 [67.5 kB]
Get:13 http://172.17.0.1/private buster-staging/main armhf libpython3.6-stdlib armhf 3.6.3-1 [2055 kB]
Get:14 http://172.17.0.1/private buster-staging/main armhf python3.6 armhf 3.6.3-1 [218 kB]
Get:15 http://172.17.0.1/private buster-staging/main armhf libpython3-stdlib armhf 3.6.3-2 [19.1 kB]
Get:16 http://172.17.0.1/private buster-staging/main armhf dh-python all 2.20170125 [86.8 kB]
Get:17 http://172.17.0.1/private buster-staging/main armhf python3 armhf 3.6.3-2 [22.1 kB]
Get:18 http://172.17.0.1/private buster-staging/main armhf libssl1.0.2 armhf 1.0.2m-3 [887 kB]
Get:19 http://172.17.0.1/private buster-staging/main armhf libmagic-mgc armhf 1:5.32-1 [225 kB]
Get:20 http://172.17.0.1/private buster-staging/main armhf libmagic1 armhf 1:5.32-1 [105 kB]
Get:21 http://172.17.0.1/private buster-staging/main armhf file armhf 1:5.32-1 [63.7 kB]
Get:22 http://172.17.0.1/private buster-staging/main armhf gettext-base armhf 0.19.8.1-4 [117 kB]
Get:23 http://172.17.0.1/private buster-staging/main armhf libicu57 armhf 57.1-8 [7411 kB]
Get:24 http://172.17.0.1/private buster-staging/main armhf libxml2 armhf 2.9.4+dfsg1-5 [609 kB]
Get:25 http://172.17.0.1/private buster-staging/main armhf libsigsegv2 armhf 2.11-1 [29.3 kB]
Get:26 http://172.17.0.1/private buster-staging/main armhf m4 armhf 1.4.18-1 [185 kB]
Get:27 http://172.17.0.1/private buster-staging/main armhf autoconf all 2.69-11 [341 kB]
Get:28 http://172.17.0.1/private buster-staging/main armhf autotools-dev all 20161112.1+nmu1 [74.2 kB]
Get:29 http://172.17.0.1/private buster-staging/main armhf automake all 1:1.15.1-3 [736 kB]
Get:30 http://172.17.0.1/private buster-staging/main armhf autopoint all 0.19.8.1-4 [434 kB]
Get:31 http://172.17.0.1/private buster-staging/main armhf libtool all 2.4.6-2 [545 kB]
Get:32 http://172.17.0.1/private buster-staging/main armhf dh-autoreconf all 14 [15.9 kB]
Get:33 http://172.17.0.1/private buster-staging/main armhf libarchive-zip-perl all 1.59-1 [95.5 kB]
Get:34 http://172.17.0.1/private buster-staging/main armhf libfile-stripnondeterminism-perl all 0.040-1 [18.4 kB]
Get:35 http://172.17.0.1/private buster-staging/main armhf libtimedate-perl all 2.3000-2 [42.2 kB]
Get:36 http://172.17.0.1/private buster-staging/main armhf dh-strip-nondeterminism all 0.040-1 [11.8 kB]
Get:37 http://172.17.0.1/private buster-staging/main armhf libglib2.0-0 armhf 2.54.1-1 [2653 kB]
Get:38 http://172.17.0.1/private buster-staging/main armhf libcroco3 armhf 0.6.12-1 [132 kB]
Get:39 http://172.17.0.1/private buster-staging/main armhf gettext armhf 0.19.8.1-4 [1218 kB]
Get:40 http://172.17.0.1/private buster-staging/main armhf intltool-debian all 0.35.0+20060710.4 [26.3 kB]
Get:41 http://172.17.0.1/private buster-staging/main armhf po-debconf all 1.0.20 [247 kB]
Get:42 http://172.17.0.1/private buster-staging/main armhf debhelper all 10.10.5 [978 kB]
Get:43 http://172.17.0.1/private buster-staging/main armhf libfile-which-perl all 1.21-1 [14.3 kB]
Get:44 http://172.17.0.1/private buster-staging/main armhf libfile-homedir-perl all 1.002-1 [42.3 kB]
Get:45 http://172.17.0.1/private buster-staging/main armhf devscripts armhf 2.17.11 [966 kB]
Get:46 http://172.17.0.1/private buster-staging/main armhf rubygems-integration all 1.11 [4994 B]
Get:47 http://172.17.0.1/private buster-staging/main armhf ruby-did-you-mean all 1.0.0-2 [11.2 kB]
Get:48 http://172.17.0.1/private buster-staging/main armhf ruby-minitest all 5.10.3-1 [53.5 kB]
Get:49 http://172.17.0.1/private buster-staging/main armhf ruby-net-telnet all 0.1.1-2 [12.5 kB]
Get:50 http://172.17.0.1/private buster-staging/main armhf ruby-power-assert all 0.3.0-1 [7902 B]
Get:51 http://172.17.0.1/private buster-staging/main armhf ruby-test-unit all 3.2.5-1 [71.7 kB]
Get:52 http://172.17.0.1/private buster-staging/main armhf libyaml-0-2 armhf 0.1.7-2 [39.9 kB]
Get:53 http://172.17.0.1/private buster-staging/main armhf libruby2.3 armhf 2.3.3-1+deb9u1+rpi1 [2865 kB]
Get:54 http://172.17.0.1/private buster-staging/main armhf ruby2.3 armhf 2.3.3-1+deb9u1+rpi1 [187 kB]
Get:55 http://172.17.0.1/private buster-staging/main armhf ruby armhf 1:2.3.3 [10.8 kB]
Get:56 http://172.17.0.1/private buster-staging/main armhf rake all 12.0.0-1 [45.7 kB]
Get:57 http://172.17.0.1/private buster-staging/main armhf gem2deb-test-runner armhf 0.36 [20.9 kB]
Get:58 http://172.17.0.1/private buster-staging/main armhf libgmpxx4ldbl armhf 2:6.1.2+dfsg-1.1 [21.5 kB]
Get:59 http://172.17.0.1/private buster-staging/main armhf libgmp-dev armhf 2:6.1.2+dfsg-1.1 [561 kB]
Get:60 http://172.17.0.1/private buster-staging/main armhf ruby2.3-dev armhf 2.3.3-1+deb9u1+rpi1 [1031 kB]
Get:61 http://172.17.0.1/private buster-staging/main armhf ruby-all-dev armhf 1:2.3.3 [10.2 kB]
Get:62 http://172.17.0.1/private buster-staging/main armhf ruby-setup all 3.4.1-9 [34.2 kB]
Get:63 http://172.17.0.1/private buster-staging/main armhf gem2deb armhf 0.36 [58.2 kB]
Get:64 http://172.17.0.1/private buster-staging/main armhf ruby-diff-lcs all 1.3-1 [25.7 kB]
Get:65 http://172.17.0.1/private buster-staging/main armhf ruby-rspec-support all 3.5.0c3e0m0s0-1 [28.2 kB]
Get:66 http://172.17.0.1/private buster-staging/main armhf ruby-rspec-expectations all 3.5.0c3e0m0s0-1 [97.5 kB]
Get:67 http://172.17.0.1/private buster-staging/main armhf ruby-rspec-mocks all 3.5.0c3e0m0s0-1 [92.4 kB]
Get:68 http://172.17.0.1/private buster-staging/main armhf ruby-thread-order all 1.1.0-1 [5096 B]
Get:69 http://172.17.0.1/private buster-staging/main armhf ruby-rspec-core all 3.5.0c3e0m0s0-1 [184 kB]
Get:70 http://172.17.0.1/private buster-staging/main armhf ruby-rspec all 3.5.0c3e0m0s0-1 [7122 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 30.4 MB in 5s (5948 kB/s)
Selecting previously unselected package groff-base.
(Reading database ... 15098 files and directories currently installed.)
Preparing to unpack .../00-groff-base_1.22.3-9_armhf.deb ...
Unpacking groff-base (1.22.3-9) ...
Selecting previously unselected package libbsd0:armhf.
Preparing to unpack .../01-libbsd0_0.8.6-3_armhf.deb ...
Unpacking libbsd0:armhf (0.8.6-3) ...
Selecting previously unselected package bsdmainutils.
Preparing to unpack .../02-bsdmainutils_9.0.14_armhf.deb ...
Unpacking bsdmainutils (9.0.14) ...
Selecting previously unselected package libpipeline1:armhf.
Preparing to unpack .../03-libpipeline1_1.4.2-1_armhf.deb ...
Unpacking libpipeline1:armhf (1.4.2-1) ...
Selecting previously unselected package man-db.
Preparing to unpack .../04-man-db_2.7.6.1-2_armhf.deb ...
Unpacking man-db (2.7.6.1-2) ...
Selecting previously unselected package libpython3.6-minimal:armhf.
Preparing to unpack .../05-libpython3.6-minimal_3.6.3-1_armhf.deb ...
Unpacking libpython3.6-minimal:armhf (3.6.3-1) ...
Selecting previously unselected package libexpat1:armhf.
Preparing to unpack .../06-libexpat1_2.2.3-2_armhf.deb ...
Unpacking libexpat1:armhf (2.2.3-2) ...
Selecting previously unselected package python3.6-minimal.
Preparing to unpack .../07-python3.6-minimal_3.6.3-1_armhf.deb ...
Unpacking python3.6-minimal (3.6.3-1) ...
Selecting previously unselected package python3-minimal.
Preparing to unpack .../08-python3-minimal_3.6.3-2_armhf.deb ...
Unpacking python3-minimal (3.6.3-2) ...
Selecting previously unselected package mime-support.
Preparing to unpack .../09-mime-support_3.60_all.deb ...
Unpacking mime-support (3.60) ...
Selecting previously unselected package libmpdec2:armhf.
Preparing to unpack .../10-libmpdec2_2.4.2-1_armhf.deb ...
Unpacking libmpdec2:armhf (2.4.2-1) ...
Selecting previously unselected package libpython3.6-stdlib:armhf.
Preparing to unpack .../11-libpython3.6-stdlib_3.6.3-1_armhf.deb ...
Unpacking libpython3.6-stdlib:armhf (3.6.3-1) ...
Selecting previously unselected package python3.6.
Preparing to unpack .../12-python3.6_3.6.3-1_armhf.deb ...
Unpacking python3.6 (3.6.3-1) ...
Selecting previously unselected package libpython3-stdlib:armhf.
Preparing to unpack .../13-libpython3-stdlib_3.6.3-2_armhf.deb ...
Unpacking libpython3-stdlib:armhf (3.6.3-2) ...
Selecting previously unselected package dh-python.
Preparing to unpack .../14-dh-python_2.20170125_all.deb ...
Unpacking dh-python (2.20170125) ...
Setting up libpython3.6-minimal:armhf (3.6.3-1) ...
Setting up libexpat1:armhf (2.2.3-2) ...
Setting up python3.6-minimal (3.6.3-1) ...
Setting up python3-minimal (3.6.3-2) ...
Selecting previously unselected package python3.
(Reading database ... 16624 files and directories currently installed.)
Preparing to unpack .../00-python3_3.6.3-2_armhf.deb ...
Unpacking python3 (3.6.3-2) ...
Selecting previously unselected package libssl1.0.2:armhf.
Preparing to unpack .../01-libssl1.0.2_1.0.2m-3_armhf.deb ...
Unpacking libssl1.0.2:armhf (1.0.2m-3) ...
Selecting previously unselected package libmagic-mgc.
Preparing to unpack .../02-libmagic-mgc_1%3a5.32-1_armhf.deb ...
Unpacking libmagic-mgc (1:5.32-1) ...
Selecting previously unselected package libmagic1:armhf.
Preparing to unpack .../03-libmagic1_1%3a5.32-1_armhf.deb ...
Unpacking libmagic1:armhf (1:5.32-1) ...
Selecting previously unselected package file.
Preparing to unpack .../04-file_1%3a5.32-1_armhf.deb ...
Unpacking file (1:5.32-1) ...
Selecting previously unselected package gettext-base.
Preparing to unpack .../05-gettext-base_0.19.8.1-4_armhf.deb ...
Unpacking gettext-base (0.19.8.1-4) ...
Selecting previously unselected package libicu57:armhf.
Preparing to unpack .../06-libicu57_57.1-8_armhf.deb ...
Unpacking libicu57:armhf (57.1-8) ...
Selecting previously unselected package libxml2:armhf.
Preparing to unpack .../07-libxml2_2.9.4+dfsg1-5_armhf.deb ...
Unpacking libxml2:armhf (2.9.4+dfsg1-5) ...
Selecting previously unselected package libsigsegv2:armhf.
Preparing to unpack .../08-libsigsegv2_2.11-1_armhf.deb ...
Unpacking libsigsegv2:armhf (2.11-1) ...
Selecting previously unselected package m4.
Preparing to unpack .../09-m4_1.4.18-1_armhf.deb ...
Unpacking m4 (1.4.18-1) ...
Selecting previously unselected package autoconf.
Preparing to unpack .../10-autoconf_2.69-11_all.deb ...
Unpacking autoconf (2.69-11) ...
Selecting previously unselected package autotools-dev.
Preparing to unpack .../11-autotools-dev_20161112.1+nmu1_all.deb ...
Unpacking autotools-dev (20161112.1+nmu1) ...
Selecting previously unselected package automake.
Preparing to unpack .../12-automake_1%3a1.15.1-3_all.deb ...
Unpacking automake (1:1.15.1-3) ...
Selecting previously unselected package autopoint.
Preparing to unpack .../13-autopoint_0.19.8.1-4_all.deb ...
Unpacking autopoint (0.19.8.1-4) ...
Selecting previously unselected package libtool.
Preparing to unpack .../14-libtool_2.4.6-2_all.deb ...
Unpacking libtool (2.4.6-2) ...
Selecting previously unselected package dh-autoreconf.
Preparing to unpack .../15-dh-autoreconf_14_all.deb ...
Unpacking dh-autoreconf (14) ...
Selecting previously unselected package libarchive-zip-perl.
Preparing to unpack .../16-libarchive-zip-perl_1.59-1_all.deb ...
Unpacking libarchive-zip-perl (1.59-1) ...
Selecting previously unselected package libfile-stripnondeterminism-perl.
Preparing to unpack .../17-libfile-stripnondeterminism-perl_0.040-1_all.deb ...
Unpacking libfile-stripnondeterminism-perl (0.040-1) ...
Selecting previously unselected package libtimedate-perl.
Preparing to unpack .../18-libtimedate-perl_2.3000-2_all.deb ...
Unpacking libtimedate-perl (2.3000-2) ...
Selecting previously unselected package dh-strip-nondeterminism.
Preparing to unpack .../19-dh-strip-nondeterminism_0.040-1_all.deb ...
Unpacking dh-strip-nondeterminism (0.040-1) ...
Selecting previously unselected package libglib2.0-0:armhf.
Preparing to unpack .../20-libglib2.0-0_2.54.1-1_armhf.deb ...
Unpacking libglib2.0-0:armhf (2.54.1-1) ...
Selecting previously unselected package libcroco3:armhf.
Preparing to unpack .../21-libcroco3_0.6.12-1_armhf.deb ...
Unpacking libcroco3:armhf (0.6.12-1) ...
Selecting previously unselected package gettext.
Preparing to unpack .../22-gettext_0.19.8.1-4_armhf.deb ...
Unpacking gettext (0.19.8.1-4) ...
Selecting previously unselected package intltool-debian.
Preparing to unpack .../23-intltool-debian_0.35.0+20060710.4_all.deb ...
Unpacking intltool-debian (0.35.0+20060710.4) ...
Selecting previously unselected package po-debconf.
Preparing to unpack .../24-po-debconf_1.0.20_all.deb ...
Unpacking po-debconf (1.0.20) ...
Selecting previously unselected package debhelper.
Preparing to unpack .../25-debhelper_10.10.5_all.deb ...
Unpacking debhelper (10.10.5) ...
Selecting previously unselected package libfile-which-perl.
Preparing to unpack .../26-libfile-which-perl_1.21-1_all.deb ...
Unpacking libfile-which-perl (1.21-1) ...
Selecting previously unselected package libfile-homedir-perl.
Preparing to unpack .../27-libfile-homedir-perl_1.002-1_all.deb ...
Unpacking libfile-homedir-perl (1.002-1) ...
Selecting previously unselected package devscripts.
Preparing to unpack .../28-devscripts_2.17.11_armhf.deb ...
Unpacking devscripts (2.17.11) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../29-rubygems-integration_1.11_all.deb ...
Unpacking rubygems-integration (1.11) ...
Selecting previously unselected package ruby-did-you-mean.
Preparing to unpack .../30-ruby-did-you-mean_1.0.0-2_all.deb ...
Unpacking ruby-did-you-mean (1.0.0-2) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../31-ruby-minitest_5.10.3-1_all.deb ...
Unpacking ruby-minitest (5.10.3-1) ...
Selecting previously unselected package ruby-net-telnet.
Preparing to unpack .../32-ruby-net-telnet_0.1.1-2_all.deb ...
Unpacking ruby-net-telnet (0.1.1-2) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../33-ruby-power-assert_0.3.0-1_all.deb ...
Unpacking ruby-power-assert (0.3.0-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../34-ruby-test-unit_3.2.5-1_all.deb ...
Unpacking ruby-test-unit (3.2.5-1) ...
Selecting previously unselected package libyaml-0-2:armhf.
Preparing to unpack .../35-libyaml-0-2_0.1.7-2_armhf.deb ...
Unpacking libyaml-0-2:armhf (0.1.7-2) ...
Selecting previously unselected package libruby2.3:armhf.
Preparing to unpack .../36-libruby2.3_2.3.3-1+deb9u1+rpi1_armhf.deb ...
Unpacking libruby2.3:armhf (2.3.3-1+deb9u1+rpi1) ...
Selecting previously unselected package ruby2.3.
Preparing to unpack .../37-ruby2.3_2.3.3-1+deb9u1+rpi1_armhf.deb ...
Unpacking ruby2.3 (2.3.3-1+deb9u1+rpi1) ...
Selecting previously unselected package ruby.
Preparing to unpack .../38-ruby_1%3a2.3.3_armhf.deb ...
Unpacking ruby (1:2.3.3) ...
Selecting previously unselected package rake.
Preparing to unpack .../39-rake_12.0.0-1_all.deb ...
Unpacking rake (12.0.0-1) ...
Selecting previously unselected package gem2deb-test-runner.
Preparing to unpack .../40-gem2deb-test-runner_0.36_armhf.deb ...
Unpacking gem2deb-test-runner (0.36) ...
Selecting previously unselected package libgmpxx4ldbl:armhf.
Preparing to unpack .../41-libgmpxx4ldbl_2%3a6.1.2+dfsg-1.1_armhf.deb ...
Unpacking libgmpxx4ldbl:armhf (2:6.1.2+dfsg-1.1) ...
Selecting previously unselected package libgmp-dev:armhf.
Preparing to unpack .../42-libgmp-dev_2%3a6.1.2+dfsg-1.1_armhf.deb ...
Unpacking libgmp-dev:armhf (2:6.1.2+dfsg-1.1) ...
Selecting previously unselected package ruby2.3-dev:armhf.
Preparing to unpack .../43-ruby2.3-dev_2.3.3-1+deb9u1+rpi1_armhf.deb ...
Unpacking ruby2.3-dev:armhf (2.3.3-1+deb9u1+rpi1) ...
Selecting previously unselected package ruby-all-dev:armhf.
Preparing to unpack .../44-ruby-all-dev_1%3a2.3.3_armhf.deb ...
Unpacking ruby-all-dev:armhf (1:2.3.3) ...
Selecting previously unselected package ruby-setup.
Preparing to unpack .../45-ruby-setup_3.4.1-9_all.deb ...
Unpacking ruby-setup (3.4.1-9) ...
Selecting previously unselected package gem2deb.
Preparing to unpack .../46-gem2deb_0.36_armhf.deb ...
Unpacking gem2deb (0.36) ...
Selecting previously unselected package ruby-diff-lcs.
Preparing to unpack .../47-ruby-diff-lcs_1.3-1_all.deb ...
Unpacking ruby-diff-lcs (1.3-1) ...
Selecting previously unselected package ruby-rspec-support.
Preparing to unpack .../48-ruby-rspec-support_3.5.0c3e0m0s0-1_all.deb ...
Unpacking ruby-rspec-support (3.5.0c3e0m0s0-1) ...
Selecting previously unselected package ruby-rspec-expectations.
Preparing to unpack .../49-ruby-rspec-expectations_3.5.0c3e0m0s0-1_all.deb ...
Unpacking ruby-rspec-expectations (3.5.0c3e0m0s0-1) ...
Selecting previously unselected package ruby-rspec-mocks.
Preparing to unpack .../50-ruby-rspec-mocks_3.5.0c3e0m0s0-1_all.deb ...
Unpacking ruby-rspec-mocks (3.5.0c3e0m0s0-1) ...
Selecting previously unselected package ruby-thread-order.
Preparing to unpack .../51-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 .../52-ruby-rspec-core_3.5.0c3e0m0s0-1_all.deb ...
Unpacking ruby-rspec-core (3.5.0c3e0m0s0-1) ...
Selecting previously unselected package ruby-rspec.
Preparing to unpack .../53-ruby-rspec_3.5.0c3e0m0s0-1_all.deb ...
Unpacking ruby-rspec (3.5.0c3e0m0s0-1) ...
Selecting previously unselected package sbuild-build-depends-ruby-yajl-dummy.
Preparing to unpack .../54-sbuild-build-depends-ruby-yajl-dummy_0.invalid.0_armhf.deb ...
Unpacking sbuild-build-depends-ruby-yajl-dummy (0.invalid.0) ...
Setting up libarchive-zip-perl (1.59-1) ...
Setting up mime-support (3.60) ...
Setting up libfile-which-perl (1.21-1) ...
Setting up libtimedate-perl (2.3000-2) ...
Setting up libsigsegv2:armhf (2.11-1) ...
Setting up libfile-homedir-perl (1.002-1) ...
Setting up groff-base (1.22.3-9) ...
Setting up libglib2.0-0:armhf (2.54.1-1) ...
No schema files found: doing nothing.
Setting up gettext-base (0.19.8.1-4) ...
Setting up libpipeline1:armhf (1.4.2-1) ...
Setting up m4 (1.4.18-1) ...
Setting up libicu57:armhf (57.1-8) ...
Setting up libbsd0:armhf (0.8.6-3) ...
Setting up libxml2:armhf (2.9.4+dfsg1-5) ...
Setting up libmagic-mgc (1:5.32-1) ...
Setting up libmagic1:armhf (1:5.32-1) ...
Setting up libcroco3:armhf (0.6.12-1) ...
Setting up libssl1.0.2:armhf (1.0.2m-3) ...
Setting up ruby-did-you-mean (1.0.0-2) ...
Setting up libyaml-0-2:armhf (0.1.7-2) ...
Processing triggers for libc-bin (2.24-17) ...
Setting up autotools-dev (20161112.1+nmu1) ...
Setting up ruby-net-telnet (0.1.1-2) ...
Setting up rubygems-integration (1.11) ...
Setting up bsdmainutils (9.0.14) ...
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 libgmpxx4ldbl:armhf (2:6.1.2+dfsg-1.1) ...
Setting up ruby-minitest (5.10.3-1) ...
Setting up autopoint (0.19.8.1-4) ...
Setting up libmpdec2:armhf (2.4.2-1) ...
Setting up ruby-power-assert (0.3.0-1) ...
Setting up libfile-stripnondeterminism-perl (0.040-1) ...
Setting up libgmp-dev:armhf (2:6.1.2+dfsg-1.1) ...
Setting up libpython3.6-stdlib:armhf (3.6.3-1) ...
Setting up python3.6 (3.6.3-1) ...
Setting up gettext (0.19.8.1-4) ...
Setting up autoconf (2.69-11) ...
Setting up file (1:5.32-1) ...
Setting up intltool-debian (0.35.0+20060710.4) ...
Setting up automake (1:1.15.1-3) ...
update-alternatives: using /usr/bin/automake-1.15 to provide /usr/bin/automake (automake) in auto mode
Setting up man-db (2.7.6.1-2) ...
Not building database; man-db/auto-update is not 'true'.
Setting up libtool (2.4.6-2) ...
Setting up libpython3-stdlib:armhf (3.6.3-2) ...
Setting up po-debconf (1.0.20) ...
Setting up rake (12.0.0-1) ...
Setting up dh-autoreconf (14) ...
Setting up python3 (3.6.3-2) ...
Setting up ruby-test-unit (3.2.5-1) ...
Setting up devscripts (2.17.11) ...
Setting up libruby2.3:armhf (2.3.3-1+deb9u1+rpi1) ...
Setting up dh-python (2.20170125) ...
Setting up debhelper (10.10.5) ...
Setting up ruby2.3 (2.3.3-1+deb9u1+rpi1) ...
Setting up ruby2.3-dev:armhf (2.3.3-1+deb9u1+rpi1) ...
Setting up dh-strip-nondeterminism (0.040-1) ...
Setting up ruby (1:2.3.3) ...
Setting up ruby-diff-lcs (1.3-1) ...
Setting up gem2deb-test-runner (0.36) ...
Setting up ruby-all-dev:armhf (1:2.3.3) ...
Setting up ruby-thread-order (1.1.0-1) ...
Setting up ruby-rspec-support (3.5.0c3e0m0s0-1) ...
Setting up ruby-setup (3.4.1-9) ...
Setting up gem2deb (0.36) ...
Setting up ruby-rspec-expectations (3.5.0c3e0m0s0-1) ...
Setting up ruby-rspec-mocks (3.5.0c3e0m0s0-1) ...
Setting up ruby-rspec-core (3.5.0c3e0m0s0-1) ...
Setting up ruby-rspec (3.5.0c3e0m0s0-1) ...
Setting up sbuild-build-depends-ruby-yajl-dummy (0.invalid.0) ...
Processing triggers for libc-bin (2.24-17) ...
W: No sandbox user '_apt' on the system, can not drop privileges
W: copy: aptMethod::Configuration: could not load seccomp policy: Invalid argument
W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument
+------------------------------------------------------------------------------+
| Build environment |
+------------------------------------------------------------------------------+
Kernel: Linux 3.19.0-trunk-armmp armhf (armv7l)
Toolchain package versions: binutils_2.29.1-6+rpi1 dpkg-dev_1.19.0.4 g++-7_7.2.0-12 gcc-7_7.2.0-12 libc6-dev_2.24-17 libstdc++-7-dev_7.2.0-12 libstdc++6_7.2.0-12 linux-libc-dev_4.9.51-1+rpi3+b1
Package versions: adduser_3.116 apt_1.6~alpha3 autoconf_2.69-11 automake_1:1.15.1-3 autopoint_0.19.8.1-4 autotools-dev_20161112.1+nmu1 base-files_10+rpi1 base-passwd_3.5.44 bash_4.4-5 binutils_2.29.1-6+rpi1 binutils-arm-linux-gnueabihf_2.29.1-6+rpi1 binutils-common_2.29.1-6+rpi1 bsdmainutils_9.0.14 bsdutils_1:2.30.2-0.1 build-essential_12.4 bzip2_1.0.6-8.1 ca-certificates_20170717 coreutils_8.28-1 cpio_2.11+dfsg-6 cpp_4:7.2.0-1d1 cpp-7_7.2.0-12 dash_0.5.8-2.5 debconf_1.5.64 debhelper_10.10.5 debianutils_4.8.2 devscripts_2.17.11 dh-autoreconf_14 dh-python_2.20170125 dh-strip-nondeterminism_0.040-1 diffutils_1:3.6-1 dirmngr_2.2.1-5 dmsetup_2:1.02.142-1 dpkg_1.19.0.4 dpkg-dev_1.19.0.4 e2fslibs_1.43.7-1 e2fsprogs_1.43.7-1 e2fsprogs-l10n_1.43.7-1 fakeroot_1.22-1 fdisk_2.30.2-0.1 file_1:5.32-1 findutils_4.6.0+git+20170729-2 g++_4:7.2.0-1d1 g++-7_7.2.0-12 gcc_4:7.2.0-1d1 gcc-4.6-base_4.6.4-5+rpi1 gcc-4.7-base_4.7.3-11+rpi1 gcc-4.8-base_4.8.5-4 gcc-4.9-base_4.9.3-14 gcc-5-base_5.4.1-4 gcc-7_7.2.0-12 gcc-7-base_7.2.0-12 gem2deb_0.36 gem2deb-test-runner_0.36 gettext_0.19.8.1-4 gettext-base_0.19.8.1-4 gnupg_2.2.1-5 gnupg-agent_2.2.1-5 gnupg-l10n_2.2.1-5 gnupg-utils_2.2.1-5 gpg_2.2.1-5 gpg-agent_2.2.1-5 gpg-wks-client_2.2.1-5 gpg-wks-server_2.2.1-5 gpgconf_2.2.1-5 gpgsm_2.2.1-5 gpgv_2.2.1-5 grep_3.1-2 groff-base_1.22.3-9 gzip_1.6-5 hostname_3.18 init-system-helpers_1.51 initramfs-tools_0.130 initramfs-tools-core_0.130 intltool-debian_0.35.0+20060710.4 klibc-utils_2.0.4-9+rpi1 kmod_24-1 libacl1_2.2.52-3 libapparmor1_2.11.1-2 libapt-pkg5.0_1.6~alpha3 libarchive-zip-perl_1.59-1 libasan4_7.2.0-12 libassuan0_2.4.3-3 libatomic1_7.2.0-12 libattr1_1:2.4.47-2 libaudit-common_1:2.8.1-1 libaudit1_1:2.8.1-1 libbinutils_2.29.1-6+rpi1 libblkid1_2.30.2-0.1 libbsd0_0.8.6-3 libbz2-1.0_1.0.6-8.1 libc-bin_2.24-17 libc-dev-bin_2.24-17 libc6_2.24-17 libc6-dev_2.24-17 libcap-ng0_0.7.7-3.1+b1 libcap2_1:2.25-1.1 libcc1-0_7.2.0-12 libcilkrts5_7.2.0-12 libcomerr2_1.43.7-1 libcroco3_0.6.12-1 libcryptsetup4_2:1.7.5-1 libdb5.3_5.3.28-13.1 libdbus-1-3_1.11.22-1 libdebconfclient0_0.232 libdevmapper1.02.1_2:1.02.142-1 libdpkg-perl_1.19.0.4 libdrm-common_2.4.84-2+rpi1 libdrm2_2.4.84-2+rpi1 libexpat1_2.2.3-2 libfakeroot_1.22-1 libfdisk1_2.30.2-0.1 libffi6_3.2.1-6 libfile-homedir-perl_1.002-1 libfile-stripnondeterminism-perl_0.040-1 libfile-which-perl_1.21-1 libgcc-7-dev_7.2.0-12 libgcc1_1:7.2.0-12 libgcrypt20_1.7.9-1 libgdbm3_1.8.3-14 libglib2.0-0_2.54.1-1 libgmp-dev_2:6.1.2+dfsg-1.1 libgmp10_2:6.1.2+dfsg-1.1 libgmpxx4ldbl_2:6.1.2+dfsg-1.1 libgnutls30_3.5.16-1 libgomp1_7.2.0-12 libgpg-error0_1.27-4 libhogweed4_3.3-2 libicu57_57.1-8 libidn11_1.33-2 libidn2-0_2.0.2-5 libip4tc0_1.6.1-2+b1 libisl15_0.18-1 libklibc_2.0.4-9+rpi1 libkmod2_24-1 libksba8_1.3.5-2 libldap-2.4-2_2.4.45+dfsg-1 libldap-common_2.4.45+dfsg-1 liblz4-1_0.0~r131-2 liblzma5_5.2.2-1.3 libmagic-mgc_1:5.32-1 libmagic1_1:5.32-1 libmount1_2.30.2-0.1 libmpc3_1.0.3-2 libmpdec2_2.4.2-1 libmpfr4_3.1.6-1 libncurses5_6.0+20170902-1 libncursesw5_6.0+20170902-1 libnettle6_3.3-2 libnih-dbus1_1.0.3-8 libnih1_1.0.3-8 libnpth0_1.5-2 libp11-kit0_0.23.9-2 libpam-modules_1.1.8-3.6 libpam-modules-bin_1.1.8-3.6 libpam-runtime_1.1.8-3.6 libpam0g_1.1.8-3.6 libpcre3_2:8.39-4 libperl5.24_5.24.1-7 libperl5.26_5.26.1-2 libpipeline1_1.4.2-1 libplymouth4_0.9.3-1 libpng16-16_1.6.34-1 libprocps6_2:3.3.12-3 libpython3-stdlib_3.6.3-2 libpython3.6-minimal_3.6.3-1 libpython3.6-stdlib_3.6.3-1 libreadline7_7.0-3 libruby2.3_2.3.3-1+deb9u1+rpi1 libsasl2-2_2.1.27~101-g0780600+dfsg-3 libsasl2-modules_2.1.27~101-g0780600+dfsg-3 libsasl2-modules-db_2.1.27~101-g0780600+dfsg-3 libseccomp2_2.3.1-2.1 libselinux1_2.7-2 libsemanage-common_2.7-2 libsemanage1_2.7-2 libsepol1_2.7-1 libsigsegv2_2.11-1 libsmartcols1_2.30.2-0.1 libsqlite3-0_3.20.1-2 libss2_1.43.7-1 libssl1.0.2_1.0.2m-3 libssl1.1_1.1.0f-5 libstdc++-7-dev_7.2.0-12 libstdc++6_7.2.0-12 libsystemd0_235-2 libtasn1-6_4.12-2.1 libtimedate-perl_2.3000-2 libtinfo5_6.0+20170902-1 libtool_2.4.6-2 libubsan0_7.2.0-12 libudev1_235-2 libunistring2_0.9.7-2 libustr-1.0-1_1.0.4-6 libuuid1_2.30.2-0.1 libxml2_2.9.4+dfsg1-5 libyaml-0-2_0.1.7-2 linux-base_4.5 linux-libc-dev_4.9.51-1+rpi3+b1 login_1:4.5-1 lsb-base_9.20170808+rpi1 m4_1.4.18-1 make_4.1-9.1 makedev_2.3.1-93 man-db_2.7.6.1-2 mawk_1.3.3-17 mime-support_3.60 mount_2.30.2-0.1 mountall_2.54 multiarch-support_2.24-17 ncurses-base_6.0+20170902-1 ncurses-bin_6.0+20170902-1 openssl_1.1.0f-5 passwd_1:4.5-1 patch_2.7.5-1 perl_5.26.1-2 perl-base_5.26.1-2 perl-modules-5.24_5.24.1-7 perl-modules-5.26_5.26.1-2 pinentry-curses_1.0.0-3 plymouth_0.9.3-1 po-debconf_1.0.20 procps_2:3.3.12-3 python3_3.6.3-2 python3-minimal_3.6.3-2 python3.6_3.6.3-1 python3.6-minimal_3.6.3-1 rake_12.0.0-1 raspbian-archive-keyring_20120528.2 readline-common_7.0-3 ruby_1:2.3.3 ruby-all-dev_1:2.3.3 ruby-did-you-mean_1.0.0-2 ruby-diff-lcs_1.3-1 ruby-minitest_5.10.3-1 ruby-net-telnet_0.1.1-2 ruby-power-assert_0.3.0-1 ruby-rspec_3.5.0c3e0m0s0-1 ruby-rspec-core_3.5.0c3e0m0s0-1 ruby-rspec-expectations_3.5.0c3e0m0s0-1 ruby-rspec-mocks_3.5.0c3e0m0s0-1 ruby-rspec-support_3.5.0c3e0m0s0-1 ruby-setup_3.4.1-9 ruby-test-unit_3.2.5-1 ruby-thread-order_1.1.0-1 ruby2.3_2.3.3-1+deb9u1+rpi1 ruby2.3-dev_2.3.3-1+deb9u1+rpi1 rubygems-integration_1.11 sbuild-build-depends-core-dummy_0.invalid.0 sbuild-build-depends-ruby-yajl-dummy_0.invalid.0 sed_4.4-1 sensible-utils_0.0.10 systemd_235-2 sysvinit-utils_2.88dsf-59.10 tar_1.29b-2 tzdata_2017c-1 udev_235-2 util-linux_2.30.2-0.1 xz-utils_5.2.2-1.3 zlib1g_1:1.2.8.dfsg-5
+------------------------------------------------------------------------------+
| Build |
+------------------------------------------------------------------------------+
Unpack source
-------------
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/sbuild-nonexistent/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Wed Nov 8 06:41:30 2017 UTC
gpgv: using RSA key 4644409808C171E05531DDEE054CB8F31343CF44
gpgv: issuer "carnil@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./ruby-yajl_1.2.0-3.1.dsc
dpkg-source: info: extracting ruby-yajl in /<<PKGBUILDDIR>>
dpkg-source: info: unpacking ruby-yajl_1.2.0.orig.tar.gz
dpkg-source: info: unpacking ruby-yajl_1.2.0-3.1.debian.tar.xz
dpkg-source: info: applying mocks-test-fix
dpkg-source: info: applying RSpec3-test-fix
dpkg-source: info: applying Don-t-advance-our-end-pointer-until-we-ve-checked-we.patch
Check disc space
----------------
Sufficient free space for build
User Environment
----------------
APT_CONFIG=/var/lib/sbuild/apt.conf
DEB_BUILD_OPTIONS=parallel=4
HOME=/sbuild-nonexistent
LC_ALL=POSIX
LOGNAME=buildd
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=buster-staging-armhf-sbuild
SCHROOT_CHROOT_NAME=buster-staging-armhf-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=109
SCHROOT_GROUP=buildd
SCHROOT_SESSION_ID=buster-staging-armhf-sbuild-c571f5e6-4bea-4771-beef-2f1b19799a16
SCHROOT_UID=104
SCHROOT_USER=buildd
SHELL=/bin/sh
TERM=linux
USER=buildd
dpkg-buildpackage
-----------------
dpkg-buildpackage: info: source package ruby-yajl
dpkg-buildpackage: info: source version 1.2.0-3.1
dpkg-buildpackage: info: source distribution unstable
dpkg-source --before-build ruby-yajl-1.2.0
dpkg-buildpackage: info: host architecture armhf
fakeroot debian/rules clean
dh clean --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_auto_clean -O--buildsystem=ruby
dh_auto_clean: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --clean
dh_ruby --clean
dh_clean -O--buildsystem=ruby
dh_clean: Compatibility levels before 9 are deprecated (level 7 in use)
debian/rules build-arch
dh build-arch --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_update_autotools_config -a -O--buildsystem=ruby
dh_auto_configure -a -O--buildsystem=ruby
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --configure
dh_auto_build -a -O--buildsystem=ruby
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --build
dh_ruby --build
dh_auto_test -a -O--buildsystem=ruby
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --test
fakeroot debian/rules binary-arch
dh binary-arch --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
dh_testroot -a -O--buildsystem=ruby
dh_prep -a -O--buildsystem=ruby
dh_auto_install -a -O--buildsystem=ruby
dh_auto_install: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-yajl
dh_ruby --install
┌──────────────────────────────────────────────────────────────────────────────┐
│ Install files │
└──────────────────────────────────────────────────────────────────────────────┘
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
┌──────────────────────────────────────────────────────────────────────────────┐
│ Build native extensions for ruby2.3 │
└──────────────────────────────────────────────────────────────────────────────┘
/usr/bin/ruby2.3 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /<<PKGBUILDDIR>> debian/ruby-yajl
current directory: /<<PKGBUILDDIR>>/ext/yajl
/usr/bin/ruby2.3 -r ./siteconf20171113-9700-knh8og.rb extconf.rb
creating Makefile
current directory: /<<PKGBUILDDIR>>/ext/yajl
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'
current 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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_encode.o -c yajl_encode.c
gcc -I. -I/usr/include/arm-linux-gnueabihf/ruby-2.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -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.3.0 -I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -fPIC -g -O2 -fdebug-prefix-map=/ruby2.3-2.3.3=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall -funroll-loops -o yajl_version.o -c yajl_version.c
rm -f yajl.so
gcc -shared -o yajl.so yajl.o yajl_alloc.o yajl_buf.o yajl_encode.o yajl_ext.o yajl_gen.o yajl_lex.o yajl_parser.o yajl_version.o -L. -L/usr/lib/arm-linux-gnueabihf -L. -Wl,-z,relro -Wl,-z,now -fstack-protector -rdynamic -Wl,-export-dynamic -lruby-2.3 -lpthread -lgmp -ldl -lcrypt -lm -lc
make[1]: Leaving directory '/<<PKGBUILDDIR>>/ext/yajl'
current directory: /<<PKGBUILDDIR>>/ext/yajl
make V=1 "DESTDIR=" install
make[1]: Entering directory '/<<PKGBUILDDIR>>/ext/yajl'
/bin/mkdir -p . ./.gem.20171113-9700-j7llfn/yajl
exit > .RUBYARCHDIR.-.yajl.time
/usr/bin/install -c -m 0755 yajl.so ./.gem.20171113-9700-j7llfn/yajl
make[1]: Leaving directory '/<<PKGBUILDDIR>>/ext/yajl'
dh_installchangelogs -pruby-yajl /<<PKGBUILDDIR>>/CHANGELOG.md upstream
┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata │
└──────────────────────────────────────────────────────────────────────────────┘
generating gemspec at /<<PKGBUILDDIR>>/debian/ruby-yajl/usr/share/rubygems-integration/2.3.0/specifications/yajl-ruby-1.2.0.gemspec
/usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb │
└──────────────────────────────────────────────────────────────────────────────┘
RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.3.0:/<<PKGBUILDDIR>>/debian/ruby-yajl/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-yajl/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/arm-linux-gnueabihf/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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
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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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
One-off JSON examples
should not blow up with a bad surrogate trailer
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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /<<PKGBUILDDIR>>/spec/parsing/one_off_spec.rb:28: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
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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 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 5.68 seconds (files took 1.77 seconds to load)
410 examples, 0 failures
┌──────────────────────────────────────────────────────────────────────────────┐
│ dh_ruby --install finished │
└──────────────────────────────────────────────────────────────────────────────┘
dh_installdocs -a -O--buildsystem=ruby
dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use)
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_installexamples: Compatibility levels before 9 are deprecated (level 7 in use)
dh_perl -a -O--buildsystem=ruby
dh_link -a -O--buildsystem=ruby
dh_strip_nondeterminism -a -O--buildsystem=ruby
dh_compress -X.rb -a -O--buildsystem=ruby
dh_fixperms -a -O--buildsystem=ruby
dh_missing -a -O--buildsystem=ruby
dh_strip -a -O--buildsystem=ruby
dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
dh_makeshlibs -a -O--buildsystem=ruby
dh_makeshlibs: Compatibility levels before 9 are deprecated (level 7 in use)
dh_shlibdeps -a -O--buildsystem=ruby
dh_shlibdeps: Compatibility levels before 9 are deprecated (level 7 in use)
dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/ruby-yajl/usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.3.0/yajl/yajl.so was not linked against libdl.so.2 (it uses 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.3.0/yajl/yajl.so was not linked against libm.so.6 (it uses 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.3.0/yajl/yajl.so was not linked against libgmp.so.10 (it uses 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.3.0/yajl/yajl.so was not linked against libcrypt.so.1 (it uses none of the library's symbols)
dh_ruby_fixdepends -a -O--buildsystem=ruby
dh_installdeb -a -O--buildsystem=ruby
dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use)
dh_gencontrol -a -O--buildsystem=ruby
dh_md5sums -a -O--buildsystem=ruby
dh_builddeb -a -O--buildsystem=ruby
dpkg-deb: building package 'ruby-yajl-dbgsym' in '../ruby-yajl-dbgsym_1.2.0-3.1_armhf.deb'.
dpkg-deb: building package 'ruby-yajl' in '../ruby-yajl_1.2.0-3.1_armhf.deb'.
dpkg-genbuildinfo --build=any
dpkg-genchanges --build=any -mRaspbian wandboard test autobuilder <root@raspbian.org> >../ruby-yajl_1.2.0-3.1_armhf.changes
dpkg-genchanges: info: binary-only arch-specific upload (source code and arch-indep packages not included)
dpkg-source --after-build ruby-yajl-1.2.0
dpkg-buildpackage: info: binary-only upload (no source included)
--------------------------------------------------------------------------------
Build finished at 2017-11-13T07:19:30Z
Finished
--------
I: Built successfully
+------------------------------------------------------------------------------+
| Post Build Chroot |
+------------------------------------------------------------------------------+
+------------------------------------------------------------------------------+
| Changes |
+------------------------------------------------------------------------------+
ruby-yajl_1.2.0-3.1_armhf.changes:
----------------------------------
Format: 1.8
Date: Wed, 08 Nov 2017 07:31:37 +0100
Source: ruby-yajl
Binary: ruby-yajl
Architecture: armhf
Version: 1.2.0-3.1
Distribution: buster-staging
Urgency: medium
Maintainer: Raspbian wandboard test autobuilder <root@raspbian.org>
Changed-By: Salvatore Bonaccorso <carnil@debian.org>
Description:
ruby-yajl - Ruby interface to Yajl, a JSON stream-based parser library
Closes: 880691
Changes:
ruby-yajl (1.2.0-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* CVE-2017-16516: Crafted JSON file allows to crash ruby process with a
SIGABRT in the yajl_string_decode function (Closes: #880691)
Checksums-Sha1:
b85b4f4f15bedde043dd0028fb2317930ca06b24 42784 ruby-yajl-dbgsym_1.2.0-3.1_armhf.deb
9270036521aa4242f4ad40f9654fefc601e0b9ca 5759 ruby-yajl_1.2.0-3.1_armhf.buildinfo
6bf074f584ff07e2df068c6da05ae3d6a34b760c 38956 ruby-yajl_1.2.0-3.1_armhf.deb
Checksums-Sha256:
9479d33a59ad6304f1456d3bd325eee062924a04262988040cdeb72fe557acac 42784 ruby-yajl-dbgsym_1.2.0-3.1_armhf.deb
67d61a7cf3830997e495a6d6b6bc8dbbe61e64766a0eadb85752bb112ecf0507 5759 ruby-yajl_1.2.0-3.1_armhf.buildinfo
e2e12b37a578b7151bd42e48c10847296f470c0c1a1fa4309a41628b36f2523d 38956 ruby-yajl_1.2.0-3.1_armhf.deb
Files:
fa696d9d88b25c56a59a901a3524f1f4 42784 debug optional ruby-yajl-dbgsym_1.2.0-3.1_armhf.deb
1c0447599ddcd20b3e6d3ca0e7fb7e4b 5759 ruby optional ruby-yajl_1.2.0-3.1_armhf.buildinfo
80d61e1b142fe47337b992f577a12728 38956 ruby optional ruby-yajl_1.2.0-3.1_armhf.deb
+------------------------------------------------------------------------------+
| Package contents |
+------------------------------------------------------------------------------+
ruby-yajl-dbgsym_1.2.0-3.1_armhf.deb
------------------------------------
new Debian package, version 2.0.
size 42784 bytes: control archive=552 bytes.
416 bytes, 13 lines control
106 bytes, 1 lines md5sums
Package: ruby-yajl-dbgsym
Source: ruby-yajl
Version: 1.2.0-3.1
Auto-Built-Package: debug-symbols
Architecture: armhf
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Installed-Size: 60
Depends: ruby-yajl (= 1.2.0-3.1)
Section: debug
Priority: optional
Description: debug symbols for ruby-yajl
Build-Ids: 02e3e0d247585b638627590a3a895c2e217fecc5
Ruby-Versions: ruby2.3
drwxr-xr-x root/root 0 2017-11-08 06:31 ./
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/debug/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/debug/.build-id/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/debug/.build-id/02/
-rw-r--r-- root/root 51024 2017-11-08 06:31 ./usr/lib/debug/.build-id/02/e3e0d247585b638627590a3a895c2e217fecc5.debug
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/share/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/share/doc/
lrwxrwxrwx root/root 0 2017-11-08 06:31 ./usr/share/doc/ruby-yajl-dbgsym -> ruby-yajl
ruby-yajl_1.2.0-3.1_armhf.deb
-----------------------------
new Debian package, version 2.0.
size 38956 bytes: control archive=1748 bytes.
1018 bytes, 27 lines control
2433 bytes, 29 lines md5sums
Package: ruby-yajl
Version: 1.2.0-3.1
Architecture: armhf
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Installed-Size: 127
Depends: ruby (>= 1:2.3~0), libc6 (>= 2.4), libgmp10, libruby2.3 (>= 2.3.0~preview2)
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.3
drwxr-xr-x root/root 0 2017-11-08 06:31 ./
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/arm-linux-gnueabihf/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/arm-linux-gnueabihf/ruby/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.3.0/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.3.0/yajl/
-rw-r--r-- root/root 38192 2017-11-08 06:31 ./usr/lib/arm-linux-gnueabihf/ruby/vendor_ruby/2.3.0/yajl/yajl.so
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/
-rw-r--r-- root/root 2654 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl.rb
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/
-rw-r--r-- root/root 355 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/bzip2.rb
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/
-rw-r--r-- root/root 899 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_reader.rb
-rw-r--r-- root/root 392 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/bzip2/stream_writer.rb
-rw-r--r-- root/root 243 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/deflate.rb
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/deflate/
-rw-r--r-- root/root 1334 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/deflate/stream_reader.rb
-rw-r--r-- root/root 546 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/deflate/stream_writer.rb
-rw-r--r-- root/root 234 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/gzip.rb
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/gzip/
-rw-r--r-- root/root 903 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/gzip/stream_reader.rb
-rw-r--r-- root/root 368 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/gzip/stream_writer.rb
-rw-r--r-- root/root 7376 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/http_stream.rb
-rw-r--r-- root/root 314 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/json_gem.rb
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/
-rw-r--r-- root/root 1354 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/encoding.rb
-rw-r--r-- root/root 653 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/json_gem/parsing.rb
-rw-r--r-- root/root 36 2017-11-08 06:31 ./usr/lib/ruby/vendor_ruby/yajl/version.rb
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/share/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/share/doc/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./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 1315 2017-11-08 06:31 ./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 2017-11-08 06:31 ./usr/share/doc/ruby-yajl/copyright
drwxr-xr-x root/root 0 2017-11-08 06:31 ./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 2017-11-08 06:31 ./usr/share/rubygems-integration/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/share/rubygems-integration/2.3.0/
drwxr-xr-x root/root 0 2017-11-08 06:31 ./usr/share/rubygems-integration/2.3.0/specifications/
-rw-r--r-- root/root 12167 2017-11-08 06:31 ./usr/share/rubygems-integration/2.3.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: 4724
Build-Time: 60
Distribution: buster-staging
Host Architecture: armhf
Install-Time: 423
Job: ruby-yajl_1.2.0-3.1
Machine Architecture: armhf
Package: ruby-yajl
Package-Time: 533
Source-Version: 1.2.0-3.1
Space: 4724
Status: successful
Version: 1.2.0-3.1
--------------------------------------------------------------------------------
Finished at 2017-11-13T07:19:30Z
Build needed 00:08:53, 4724k disc space