Mock Version: 1.3.4 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-is-my-json-valid.spec'], chrootPath='/var/lib/mock/697667-epel-7-x86_64-1515418424.789050/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'}shell=Falselogger=timeout=0uid=1001gid=135user='mockbuild'nspawn_args=[]printOutput=True) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-is-my-json-valid.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'} and shell False warning: Could not canonicalize hostname: copr-builder-803884010.novalocal Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs-is-my-json-valid-2.12.4-2.el7.centos.src.rpm Child return code was: 0 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-is-my-json-valid.spec'], chrootPath='/var/lib/mock/697667-epel-7-x86_64-1515418424.789050/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'}shell=Falselogger=timeout=0uid=1001gid=135user='mockbuild'nspawn_args=[]printOutput=True) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-is-my-json-valid.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'en_US.UTF-8'} and shell False Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.IDOaLd + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf package + /usr/bin/gzip -dc /builddir/build/SOURCES/is-my-json-valid-2.12.4.tgz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd package + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -rf node_modules + /usr/lib/rpm/nodejs-fixdep end-of-stream '~1.x' + /usr/lib/rpm/nodejs-fixdep jsonpointer + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Mx02m7 + umask 022 + cd /builddir/build/BUILD + cd package + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.aQWlZ0 + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64 ++ dirname /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64 + cd package + mkdir -p /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/lib/node_modules/is-my-json-valid + cp -pr package.json formats.js index.js require.js /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/lib/node_modules/is-my-json-valid + /usr/lib/rpm/nodejs-symlink-deps /usr/lib/node_modules + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/package /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match. find: 'debug': No such file or directory + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-compress + /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-python-bytecompile /usr/bin/python 1 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.o3JBXU + umask 022 + cd /builddir/build/BUILD + cd package + /usr/lib/rpm/nodejs-symlink-deps /usr/lib/node_modules --check + tape test/json-schema.js test/misc.js TAP version 13 # json-schema-test-suite additionalItems as schema ok 1 additional items match schema ok 2 additional items do not match schema # json-schema-test-suite items is schema, no additionalItems ok 3 all items match schema # json-schema-test-suite array of items with no additionalItems ok 4 no additional items present ok 5 additional items are not permitted # json-schema-test-suite additionalItems as false without items ok 6 items defaults to empty schema so everything is valid ok 7 ignores non-arrays # json-schema-test-suite additionalItems are allowed by default ok 8 only the first item is validated # json-schema-test-suite additionalProperties being false does not allow other properties ok 9 no additional properties is valid ok 10 an additional property is invalid ok 11 ignores non-objects ok 12 patternProperties are not additional properties # json-schema-test-suite additionalProperties allows a schema which should validate ok 13 no additional properties is valid ok 14 an additional valid property is valid ok 15 an additional invalid property is invalid # json-schema-test-suite additionalProperties can exist by itself ok 16 an additional valid property is valid ok 17 an additional invalid property is invalid # json-schema-test-suite additionalProperties are allowed by default ok 18 additional properties are allowed # json-schema-test-suite allOf ok 19 allOf ok 20 mismatch second ok 21 mismatch first ok 22 wrong type # json-schema-test-suite allOf with base schema ok 23 valid ok 24 mismatch base schema ok 25 mismatch first allOf ok 26 mismatch second allOf ok 27 mismatch both # json-schema-test-suite allOf simple types ok 28 valid ok 29 mismatch one # json-schema-test-suite anyOf ok 30 first anyOf valid ok 31 second anyOf valid ok 32 both anyOf valid ok 33 neither anyOf valid # json-schema-test-suite anyOf with base schema ok 34 mismatch base schema ok 35 one anyOf valid ok 36 both anyOf invalid # json-schema-test-suite integer ok 37 a bignum is an integer # json-schema-test-suite number ok 38 a bignum is a number # json-schema-test-suite integer ok 39 a negative bignum is an integer # json-schema-test-suite number ok 40 a negative bignum is a number # json-schema-test-suite string ok 41 a bignum is not a string # json-schema-test-suite integer comparison ok 42 comparison works for high numbers # json-schema-test-suite float comparison with high precision ok 43 comparison works for high numbers # json-schema-test-suite integer comparison ok 44 comparison works for very negative numbers # json-schema-test-suite float comparison with high precision on negative numbers ok 45 comparison works for very negative numbers # json-schema-test-suite invalid type for default ok 46 valid when property is specified ok 47 still valid when the invalid default is used # json-schema-test-suite invalid string value for default ok 48 valid when property is specified ok 49 still valid when the invalid default is used # json-schema-test-suite dependencies ok 50 neither ok 51 nondependant ok 52 with dependency ok 53 missing dependency ok 54 ignores non-objects # json-schema-test-suite multiple dependencies ok 55 neither ok 56 nondependants ok 57 with dependencies ok 58 missing dependency ok 59 missing other dependency ok 60 missing both dependencies # json-schema-test-suite multiple dependencies subschema ok 61 valid ok 62 no dependency ok 63 wrong type ok 64 wrong type other ok 65 wrong type both # json-schema-test-suite simple enum validation ok 66 one of the enum is valid ok 67 something else is invalid # json-schema-test-suite heterogeneous enum validation ok 68 one of the enum is valid ok 69 something else is invalid ok 70 objects are deep compared # json-schema-test-suite enums in properties ok 71 both properties are valid ok 72 missing optional property is valid ok 73 missing required property is invalid ok 74 missing all properties is invalid # json-schema-test-suite validation of date-time strings ok 75 a valid date-time string ok 76 an invalid date-time string ok 77 only RFC3339 not all of ISO 8601 are valid # json-schema-test-suite validation of URIs ok 78 a valid URI ok 79 an invalid URI ok 80 an invalid URI though valid URI reference # json-schema-test-suite validation of e-mail addresses ok 81 a valid e-mail address ok 82 an invalid e-mail address # json-schema-test-suite validation of IP addresses ok 83 a valid IP address ok 84 an IP address with too many components ok 85 an IP address with out-of-range values ok 86 an IP address without 4 components ok 87 an IP address as an integer # json-schema-test-suite validation of IPv6 addresses ok 88 a valid IPv6 address ok 89 an IPv6 address with out-of-range values ok 90 an IPv6 address with too many components ok 91 an IPv6 address containing illegal characters # json-schema-test-suite validation of host names ok 92 a valid host name ok 93 a host name starting with an illegal character ok 94 a host name containing illegal characters ok 95 a host name with a component too long # json-schema-test-suite a schema given for items ok 96 valid items ok 97 wrong type of items ok 98 ignores non-arrays # json-schema-test-suite an array of schemas for items ok 99 correct types ok 100 wrong types # json-schema-test-suite maxItems validation ok 101 shorter is valid ok 102 exact length is valid ok 103 too long is invalid ok 104 ignores non-arrays # json-schema-test-suite maxLength validation ok 105 shorter is valid ok 106 exact length is valid ok 107 too long is invalid ok 108 ignores non-strings # json-schema-test-suite maxProperties validation ok 109 shorter is valid ok 110 exact length is valid ok 111 too long is invalid ok 112 ignores non-objects # json-schema-test-suite maximum validation ok 113 below the maximum is valid ok 114 above the maximum is invalid ok 115 ignores non-numbers # json-schema-test-suite exclusiveMaximum validation ok 116 below the maximum is still valid ok 117 boundary point is invalid # json-schema-test-suite minItems validation ok 118 longer is valid ok 119 exact length is valid ok 120 too short is invalid ok 121 ignores non-arrays # json-schema-test-suite minLength validation ok 122 longer is valid ok 123 exact length is valid ok 124 too short is invalid ok 125 ignores non-strings # json-schema-test-suite minProperties validation ok 126 longer is valid ok 127 exact length is valid ok 128 too short is invalid ok 129 ignores non-objects # json-schema-test-suite minimum validation ok 130 above the minimum is valid ok 131 below the minimum is invalid ok 132 ignores non-numbers # json-schema-test-suite exclusiveMinimum validation ok 133 above the minimum is still valid ok 134 boundary point is invalid # json-schema-test-suite by int ok 135 int by int ok 136 int by int fail ok 137 ignores non-numbers # json-schema-test-suite by number ok 138 zero is multiple of anything ok 139 4.5 is multiple of 1.5 ok 140 35 is not multiple of 1.5 # json-schema-test-suite by small number ok 141 0.0075 is multiple of 0.0001 ok 142 0.00751 is not multiple of 0.0001 # json-schema-test-suite not ok 143 allowed ok 144 disallowed # json-schema-test-suite not multiple types ok 145 valid ok 146 mismatch ok 147 other mismatch # json-schema-test-suite not more complex schema ok 148 match ok 149 other match ok 150 mismatch # json-schema-test-suite forbidden property ok 151 property present ok 152 property absent # json-schema-test-suite validation of null and format ok 153 a valid date-time string ok 154 allow null # json-schema-test-suite multiple types of null and object containing properties ok 155 null is valid # json-schema-test-suite oneOf ok 156 first oneOf valid ok 157 second oneOf valid ok 158 both oneOf valid ok 159 neither oneOf valid # json-schema-test-suite oneOf with base schema ok 160 mismatch base schema ok 161 one oneOf valid ok 162 both oneOf valid # json-schema-test-suite pattern validation ok 163 a matching pattern is valid ok 164 a non-matching pattern is invalid ok 165 ignores non-strings # json-schema-test-suite patternProperties validates properties matching a regex ok 166 a single valid match is valid ok 167 multiple valid matches is valid ok 168 a single invalid match is invalid ok 169 multiple invalid matches is invalid ok 170 ignores non-objects # json-schema-test-suite multiple simultaneous patternProperties are validated ok 171 a single valid match is valid ok 172 a simultaneous match is valid ok 173 multiple matches is valid ok 174 an invalid due to one is invalid ok 175 an invalid due to the other is invalid ok 176 an invalid due to both is invalid # json-schema-test-suite regexes are not anchored by default and are case sensitive ok 177 non recognized members are ignored ok 178 recognized members are accounted for ok 179 regexes are case sensitive ok 180 regexes are case sensitive, 2 # json-schema-test-suite object properties validation ok 181 both properties present and valid is valid ok 182 one property invalid is invalid ok 183 both properties invalid is invalid ok 184 doesn't invalidate other properties ok 185 ignores non-objects # json-schema-test-suite properties, patternProperties, additionalProperties interaction ok 186 property validates property ok 187 property invalidates property ok 188 patternProperty invalidates property ok 189 patternProperty validates nonproperty ok 190 patternProperty invalidates nonproperty ok 191 additionalProperty ignores property ok 192 additionalProperty validates others ok 193 additionalProperty invalidates others # json-schema-test-suite root pointer ref ok 194 match ok 195 recursive match ok 196 mismatch ok 197 recursive mismatch # json-schema-test-suite relative pointer ref to object ok 198 match ok 199 mismatch # json-schema-test-suite relative pointer ref to array ok 200 match array ok 201 mismatch array # json-schema-test-suite escaped pointer ref ok 202 slash ok 203 tilda ok 204 percent # json-schema-test-suite nested refs ok 205 nested ref valid ok 206 nested ref invalid # json-schema-test-suite required validation ok 207 present required property is valid ok 208 non-present required property is invalid # json-schema-test-suite required default validation ok 209 not required by default # json-schema-test-suite integer type matches integers ok 210 an integer is an integer ok 211 a float is not an integer ok 212 a string is not an integer ok 213 an object is not an integer ok 214 an array is not an integer ok 215 a boolean is not an integer ok 216 null is not an integer # json-schema-test-suite number type matches numbers ok 217 an integer is a number ok 218 a float is a number ok 219 a string is not a number ok 220 an object is not a number ok 221 an array is not a number ok 222 a boolean is not a number ok 223 null is not a number # json-schema-test-suite string type matches strings ok 224 1 is not a string ok 225 a float is not a string ok 226 a string is a string ok 227 an object is not a string ok 228 an array is not a string ok 229 a boolean is not a string ok 230 null is not a string # json-schema-test-suite object type matches objects ok 231 an integer is not an object ok 232 a float is not an object ok 233 a string is not an object ok 234 an object is an object ok 235 an array is not an object ok 236 a boolean is not an object ok 237 null is not an object # json-schema-test-suite array type matches arrays ok 238 an integer is not an array ok 239 a float is not an array ok 240 a string is not an array ok 241 an object is not an array ok 242 an array is not an array ok 243 a boolean is not an array ok 244 null is not an array # json-schema-test-suite boolean type matches booleans ok 245 an integer is not a boolean ok 246 a float is not a boolean ok 247 a string is not a boolean ok 248 an object is not a boolean ok 249 an array is not a boolean ok 250 a boolean is not a boolean ok 251 null is not a boolean # json-schema-test-suite null type matches only the null object ok 252 an integer is not null ok 253 a float is not null ok 254 a string is not null ok 255 an object is not null ok 256 an array is not null ok 257 a boolean is not null ok 258 null is null # json-schema-test-suite multiple types can be specified in an array ok 259 an integer is valid ok 260 a string is valid ok 261 a float is invalid ok 262 an object is invalid ok 263 an array is invalid ok 264 a boolean is invalid ok 265 null is invalid # json-schema-test-suite uniqueItems validation ok 266 unique array of integers is valid ok 267 non-unique array of integers is invalid ok 268 numbers are unique if mathematically unequal ok 269 unique array of objects is valid ok 270 non-unique array of objects is invalid ok 271 unique array of nested objects is valid ok 272 non-unique array of nested objects is invalid ok 273 unique array of arrays is valid ok 274 non-unique array of arrays is invalid ok 275 1 and true are unique ok 276 0 and false are unique ok 277 unique heterogeneous types are valid ok 278 non-unique heterogeneous types are invalid # simple ok 279 should be valid ok 280 should be invalid ok 281 should be invalid # advanced ok 282 should be valid ok 283 should be invalid # greedy/false ok 284 should be invalid ok 285 should be equal ok 286 should be equal ok 287 should be equal ok 288 should be equal ok 289 should be equal ok 290 should be invalid ok 291 should be equal ok 292 should be equal ok 293 should be equal ok 294 should be invalid ok 295 should be equal ok 296 should be equal ok 297 should be equal # greedy/true ok 298 should be invalid ok 299 should be equal ok 300 should be equal ok 301 should be equal ok 302 should be equal ok 303 should be equal ok 304 should be invalid ok 305 should be equal ok 306 should be equal ok 307 should be equal ok 308 should be equal ok 309 should be equal ok 310 should be invalid ok 311 should be equal ok 312 should be equal ok 313 should be equal ok 314 should be invalid # additional props ok 315 (unnamed assert) ok 316 (unnamed assert) ok 317 should output the property not allowed in verbose mode # array ok 318 wrong type ok 319 is required ok 320 (unnamed assert) # nested array ok 321 is required ok 322 (unnamed assert) ok 323 (unnamed assert) # enum ok 324 is required ok 325 (unnamed assert) ok 326 (unnamed assert) # minimum/maximum ok 327 (unnamed assert) ok 328 (unnamed assert) ok 329 (unnamed assert) # exclusiveMinimum/exclusiveMaximum ok 330 (unnamed assert) ok 331 (unnamed assert) ok 332 (unnamed assert) ok 333 (unnamed assert) # custom format ok 334 not as ok 335 not as ok 336 not as ok 337 as ok 338 as # custom format function ok 339 not as ok 340 not as ok 341 not as ok 342 as ok 343 as # do not mutate schema ok 344 did not mutate # #toJSON() ok 345 should return original schema # external schemas ok 346 is a string ok 347 not a string # top-level external schema ok 348 is an object ok 349 recognizes external schema ok 350 recognizes external schema # nested required array decl ok 351 should be valid ok 352 should not be valid ok 353 should output the missing field # verbose mode ok 354 should be valid ok 355 should not be valid ok 356 error object should contain the invalid value # additional props in verbose mode ok 357 should output the path to the additional prop in the error # Date.now() is an integer ok 358 is integer # field shows item index in arrays ok 359 should output the field with specific index of failing item in the error 1..359 # tests 359 # pass 359 # ok Processing files: nodejs-is-my-json-valid-2.12.4-2.el7.centos.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.KDn3YP + exit 0 + umask 022 + cd /builddir/build/BUILD + cd package + DOCDIR=/builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/doc/nodejs-is-my-json-valid-2.12.4 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/doc/nodejs-is-my-json-valid-2.12.4 + cp -pr README.md /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/doc/nodejs-is-my-json-valid-2.12.4 + cp -pr example.js /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/doc/nodejs-is-my-json-valid-2.12.4 + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.EVZT1K + umask 022 + cd /builddir/build/BUILD + cd package + LICENSEDIR=/builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/licenses/nodejs-is-my-json-valid-2.12.4 + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/licenses/nodejs-is-my-json-valid-2.12.4 + cp -pr LICENSE /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64/usr/share/licenses/nodejs-is-my-json-valid-2.12.4 + exit 0 Provides: nodejs-is-my-json-valid = 2.12.4-2.el7.centos npm(is-my-json-valid) = 2.12.4 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: nodejs(engine) npm(end-of-stream) >= 1 npm(end-of-stream) < 2 npm(generate-function) >= 2.0.0 npm(generate-function) < 3 npm(generate-object-property) >= 1.1.0 npm(generate-object-property) < 2 npm(jsonpointer) npm(xtend) >= 4.0.0 npm(xtend) < 5 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64 warning: Could not canonicalize hostname: copr-builder-803884010.novalocal Wrote: /builddir/build/RPMS/nodejs-is-my-json-valid-2.12.4-2.el7.centos.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.aeChOB + umask 022 + cd /builddir/build/BUILD + cd package + /usr/bin/rm -rf /builddir/build/BUILDROOT/nodejs-is-my-json-valid-2.12.4-2.el7.centos.x86_64 + exit 0 Child return code was: 0