starting build "b6e51429-107b-4b06-aba9-ad1815626f7c" using release legacy FETCHSOURCE BUILD Starting Step #0 Step #0: Already have image (with digest): gcr.io/cloud-builders/git Step #0: Cloning into 'oss-fuzz'... Finished Step #0 Starting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b" Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Already have image (with digest): gcr.io/cloud-builders/docker Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Sending build context to Docker daemon 8.704kB Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 1/7 : FROM gcr.io/oss-fuzz-base/base-builder-python@sha256:d223a882810372830fd7968eb3e64533f3a2318c90be43ac753a46a15946faec Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": gcr.io/oss-fuzz-base/base-builder-python@sha256:d223a882810372830fd7968eb3e64533f3a2318c90be43ac753a46a15946faec: Pulling from oss-fuzz-base/base-builder-python Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b549f31133a9: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0d2ee9fe350e: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 12c665fd3958: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 162cc87abac5: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d7857b5d3684: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 399018d66d74: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 360521496ff2: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d860b450e986: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 828901005181: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d39c85c0cf62: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c7dafdd3d4db: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d439c8e1f49a: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c855200b29cb: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a7c9dd33db5c: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 1c16c800f4dc: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 85559ded5d6f: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 25fbf44515c4: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": e648ed1bcb12: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d71bd8f510e: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": bda36c7bd1d2: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a592917f5efa: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3cc0fee3ff32: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d3f946420e0: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0cc51d3a3e91: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b0bac1d7f242: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c66c2605a9ad: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4aa54710815b: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a5d28742c0d6: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d3d53aee0dc7: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c2fdacbea096: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a7c9dd33db5c: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 25fbf44515c4: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4bf41eed3bf4: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 19834c65599d: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 1c16c800f4dc: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 46f99dd5f5a6: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 85559ded5d6f: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ef050abf851b: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": e648ed1bcb12: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c7dafdd3d4db: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 86b0be69710e: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 8c00eb4253a7: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d71bd8f510e: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d439c8e1f49a: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": bda36c7bd1d2: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 56a21495d4c1: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c855200b29cb: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 27bbfb50a7d0: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d804adb4165e: Pulling fs layer Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a592917f5efa: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3cc0fee3ff32: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d3f946420e0: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0cc51d3a3e91: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b0bac1d7f242: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 19834c65599d: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c66c2605a9ad: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4aa54710815b: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 46f99dd5f5a6: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a5d28742c0d6: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4bf41eed3bf4: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ef050abf851b: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 86b0be69710e: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d3d53aee0dc7: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 8c00eb4253a7: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c2fdacbea096: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 27bbfb50a7d0: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d804adb4165e: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d860b450e986: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 360521496ff2: Waiting Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 399018d66d74: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 399018d66d74: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 12c665fd3958: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d7857b5d3684: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d7857b5d3684: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d860b450e986: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d860b450e986: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b549f31133a9: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b549f31133a9: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 828901005181: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 828901005181: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 162cc87abac5: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 162cc87abac5: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d439c8e1f49a: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d439c8e1f49a: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c855200b29cb: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c855200b29cb: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a7c9dd33db5c: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a7c9dd33db5c: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 1c16c800f4dc: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 1c16c800f4dc: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0d2ee9fe350e: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0d2ee9fe350e: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c7dafdd3d4db: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c7dafdd3d4db: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 85559ded5d6f: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": e648ed1bcb12: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": e648ed1bcb12: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b549f31133a9: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 25fbf44515c4: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 25fbf44515c4: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d71bd8f510e: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d71bd8f510e: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": bda36c7bd1d2: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a592917f5efa: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a592917f5efa: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3cc0fee3ff32: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3cc0fee3ff32: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b0bac1d7f242: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0cc51d3a3e91: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0cc51d3a3e91: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d39c85c0cf62: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d39c85c0cf62: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d3f946420e0: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d3f946420e0: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c66c2605a9ad: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d3d53aee0dc7: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d3d53aee0dc7: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4aa54710815b: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4aa54710815b: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a5d28742c0d6: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a5d28742c0d6: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4bf41eed3bf4: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c2fdacbea096: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c2fdacbea096: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ef050abf851b: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ef050abf851b: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 86b0be69710e: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 86b0be69710e: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 46f99dd5f5a6: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 8c00eb4253a7: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 360521496ff2: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 360521496ff2: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 56a21495d4c1: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 56a21495d4c1: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 27bbfb50a7d0: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 27bbfb50a7d0: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0d2ee9fe350e: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 12c665fd3958: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d804adb4165e: Verifying Checksum Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d804adb4165e: Download complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 162cc87abac5: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d7857b5d3684: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 399018d66d74: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 360521496ff2: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d860b450e986: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 828901005181: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d39c85c0cf62: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c7dafdd3d4db: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d439c8e1f49a: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c855200b29cb: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a7c9dd33db5c: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 1c16c800f4dc: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 85559ded5d6f: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 25fbf44515c4: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": e648ed1bcb12: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d71bd8f510e: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": bda36c7bd1d2: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a592917f5efa: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3cc0fee3ff32: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 3d3f946420e0: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 0cc51d3a3e91: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": b0bac1d7f242: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c66c2605a9ad: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4aa54710815b: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": a5d28742c0d6: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d3d53aee0dc7: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": c2fdacbea096: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 4bf41eed3bf4: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 19834c65599d: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 46f99dd5f5a6: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ef050abf851b: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 86b0be69710e: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 8c00eb4253a7: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 56a21495d4c1: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": 27bbfb50a7d0: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": d804adb4165e: Pull complete Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Digest: sha256:d223a882810372830fd7968eb3e64533f3a2318c90be43ac753a46a15946faec Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Status: Downloaded newer image for gcr.io/oss-fuzz-base/base-builder-python@sha256:d223a882810372830fd7968eb3e64533f3a2318c90be43ac753a46a15946faec Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> 238b52b82fa0 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 2/7 : RUN git clone --depth 1 --single-branch https://github.com/pypa/setuptools setuptools Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> Running in 27649c6fc51d Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Cloning into 'setuptools'... Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Removing intermediate container 27649c6fc51d Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> 677bb1e21106 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 3/7 : RUN git clone --depth 1 --single-branch https://github.com/pypa/distutils distutils Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> Running in 508f8de45643 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Cloning into 'distutils'... Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Removing intermediate container 508f8de45643 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> 40f58d215a66 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 4/7 : RUN python3 -m pip install --upgrade pip && python3 -m pip install 'pyinstaller==6.10.0' tomli tomli-w railroad-diagrams pyparsing jinja2 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> Running in 047b968e6a7f Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Requirement already satisfied: pip in /usr/local/lib/python3.10/site-packages (25.1.1) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting pip Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading pip-26.3-py3-none-any.whl.metadata (4.6 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading pip-26.3-py3-none-any.whl (2.0 MB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.0/2.0 MB 40.3 MB/s eta 0:00:00 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Installing collected packages: pip Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Attempting uninstall: pip Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Found existing installation: pip 25.1.1 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Uninstalling pip-25.1.1: Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Successfully uninstalled pip-25.1.1 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Successfully installed pip-26.3 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Requirement already satisfied: pyinstaller==6.10.0 in /usr/local/lib/python3.10/site-packages (6.10.0) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting tomli Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading tomli-2.5.0-py3-none-any.whl.metadata (10 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting tomli-w Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading tomli_w-1.2.0-py3-none-any.whl.metadata (5.7 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting railroad-diagrams Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading railroad_diagrams-3.0.1-py3-none-any.whl.metadata (11 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting pyparsing Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading pyparsing-3.3.3-py3-none-any.whl.metadata (5.9 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting jinja2 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading jinja2-3.1.6-py3-none-any.whl.metadata (2.9 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Requirement already satisfied: setuptools>=42.0.0 in /usr/local/lib/python3.10/site-packages (from pyinstaller==6.10.0) (72.1.0) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Requirement already satisfied: altgraph in /usr/local/lib/python3.10/site-packages (from pyinstaller==6.10.0) (0.17.4) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Requirement already satisfied: pyinstaller-hooks-contrib>=2024.8 in /usr/local/lib/python3.10/site-packages (from pyinstaller==6.10.0) (2025.4) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Requirement already satisfied: packaging>=22.0 in /usr/local/lib/python3.10/site-packages (from pyinstaller==6.10.0) (25.0) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Collecting MarkupSafe>=2.0 (from jinja2) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading markupsafe-3.0.4-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (2.7 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading tomli-2.5.0-py3-none-any.whl (14 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading tomli_w-1.2.0-py3-none-any.whl (6.7 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading railroad_diagrams-3.0.1-py3-none-any.whl (15 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading pyparsing-3.3.3-py3-none-any.whl (126 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading jinja2-3.1.6-py3-none-any.whl (134 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Downloading markupsafe-3.0.4-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl (20 kB) Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Installing collected packages: tomli-w, tomli, railroad-diagrams, pyparsing, MarkupSafe, jinja2 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Successfully installed MarkupSafe-3.0.4 jinja2-3.1.6 pyparsing-3.3.3 railroad-diagrams-3.0.1 tomli-2.5.0 tomli-w-1.2.0 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Removing intermediate container 047b968e6a7f Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> 68d2c93b30fe Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 5/7 : RUN urls="https://raw.githubusercontent.com/google/fuzzing/master/dictionaries/utf8.dict https://raw.githubusercontent.com/google/fuzzing/master/dictionaries/toml.dict" && target_file="$SRC/__base.dict" && echo $urls | xargs -n 1 wget -qO- >> $target_file Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> Running in 6da368ce6ce9 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Removing intermediate container 6da368ce6ce9 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> df3cde90945a Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 6/7 : COPY *.sh *py $SRC/ Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> da15dd503f7d Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Step 7/7 : WORKDIR $SRC/setuptools Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> Running in fcddbaaa3eca Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Removing intermediate container fcddbaaa3eca Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": ---> b96de9323330 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Successfully built b96de9323330 Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Successfully tagged gcr.io/oss-fuzz/setuptools:latest Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b": Successfully tagged us-central1-docker.pkg.dev/oss-fuzz/unsafe/setuptools:latest Finished Step #1 - "build-85c46ead-f61c-4ae6-b7a4-a4b29b05ad0b" Starting Step #2 - "srcmap" Step #2 - "srcmap": Already have image: gcr.io/oss-fuzz/setuptools Step #2 - "srcmap": ++ tempfile Step #2 - "srcmap": + SRCMAP=/tmp/fileqKgBWN Step #2 - "srcmap": + echo '{}' Step #2 - "srcmap": + PATHS_TO_SCAN=/src Step #2 - "srcmap": + [[ python == \g\o ]] Step #2 - "srcmap": ++ find /src -name .git -type d Step #2 - "srcmap": + for DOT_GIT_DIR in $(find $PATHS_TO_SCAN -name ".git" -type d) Step #2 - "srcmap": ++ dirname /src/distutils/.git Step #2 - "srcmap": + GIT_DIR=/src/distutils Step #2 - "srcmap": + cd /src/distutils Step #2 - "srcmap": ++ git config --get remote.origin.url Step #2 - "srcmap": + GIT_URL=https://github.com/pypa/distutils Step #2 - "srcmap": ++ git rev-parse HEAD Step #2 - "srcmap": + GIT_REV=493fff0da6bef0626ddcfeada59d4dc2b5d52616 Step #2 - "srcmap": + jq_inplace /tmp/fileqKgBWN '."/src/distutils" = { type: "git", url: "https://github.com/pypa/distutils", rev: "493fff0da6bef0626ddcfeada59d4dc2b5d52616" }' Step #2 - "srcmap": ++ tempfile Step #2 - "srcmap": + F=/tmp/fileTCHAkd Step #2 - "srcmap": + cat /tmp/fileqKgBWN Step #2 - "srcmap": + jq '."/src/distutils" = { type: "git", url: "https://github.com/pypa/distutils", rev: "493fff0da6bef0626ddcfeada59d4dc2b5d52616" }' Step #2 - "srcmap": + mv /tmp/fileTCHAkd /tmp/fileqKgBWN Step #2 - "srcmap": + for DOT_GIT_DIR in $(find $PATHS_TO_SCAN -name ".git" -type d) Step #2 - "srcmap": ++ dirname /src/setuptools/.git Step #2 - "srcmap": + GIT_DIR=/src/setuptools Step #2 - "srcmap": + cd /src/setuptools Step #2 - "srcmap": ++ git config --get remote.origin.url Step #2 - "srcmap": + GIT_URL=https://github.com/pypa/setuptools Step #2 - "srcmap": ++ git rev-parse HEAD Step #2 - "srcmap": + GIT_REV=049ae8e3083514378aedb352a2017fbc306bd126 Step #2 - "srcmap": + jq_inplace /tmp/fileqKgBWN '."/src/setuptools" = { type: "git", url: "https://github.com/pypa/setuptools", rev: "049ae8e3083514378aedb352a2017fbc306bd126" }' Step #2 - "srcmap": ++ tempfile Step #2 - "srcmap": + F=/tmp/filebauYsG Step #2 - "srcmap": + cat /tmp/fileqKgBWN Step #2 - "srcmap": + jq '."/src/setuptools" = { type: "git", url: "https://github.com/pypa/setuptools", rev: "049ae8e3083514378aedb352a2017fbc306bd126" }' Step #2 - "srcmap": + mv /tmp/filebauYsG /tmp/fileqKgBWN Step #2 - "srcmap": ++ find /src -name .svn -type d Step #2 - "srcmap": ++ find /src -name .hg -type d Step #2 - "srcmap": + '[' '' '!=' '' ']' Step #2 - "srcmap": + cat /tmp/fileqKgBWN Step #2 - "srcmap": + rm /tmp/fileqKgBWN Step #2 - "srcmap": { Step #2 - "srcmap": "/src/distutils": { Step #2 - "srcmap": "type": "git", Step #2 - "srcmap": "url": "https://github.com/pypa/distutils", Step #2 - "srcmap": "rev": "493fff0da6bef0626ddcfeada59d4dc2b5d52616" Step #2 - "srcmap": }, Step #2 - "srcmap": "/src/setuptools": { Step #2 - "srcmap": "type": "git", Step #2 - "srcmap": "url": "https://github.com/pypa/setuptools", Step #2 - "srcmap": "rev": "049ae8e3083514378aedb352a2017fbc306bd126" Step #2 - "srcmap": } Step #2 - "srcmap": } Finished Step #2 - "srcmap" Starting Step #3 - "compile-libfuzzer-coverage-x86_64" Step #3 - "compile-libfuzzer-coverage-x86_64": Already have image (with digest): gcr.io/cloud-builders/docker Step #3 - "compile-libfuzzer-coverage-x86_64": --------------------------------------------------------------- Step #3 - "compile-libfuzzer-coverage-x86_64": vm.mmap_rnd_bits = 28 Step #3 - "compile-libfuzzer-coverage-x86_64": Compiling libFuzzer to /usr/lib/libFuzzingEngine.a... done. Step #3 - "compile-libfuzzer-coverage-x86_64": --------------------------------------------------------------- Step #3 - "compile-libfuzzer-coverage-x86_64": CC=clang Step #3 - "compile-libfuzzer-coverage-x86_64": CXX=clang++ Step #3 - "compile-libfuzzer-coverage-x86_64": CFLAGS=-O1 -fno-omit-frame-pointer -gline-tables-only -Wno-error=enum-constexpr-conversion -Wno-error=incompatible-function-pointer-types -Wno-error=int-conversion -Wno-error=deprecated-declarations -Wno-error=implicit-function-declaration -Wno-error=implicit-int -Wno-error=vla-cxx-extension -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION -fprofile-instr-generate -fcoverage-mapping -pthread -Wl,--no-as-needed -Wl,-ldl -Wl,-lm -Wno-unused-command-line-argument -fno-sanitize=function,leak,vptr, Step #3 - "compile-libfuzzer-coverage-x86_64": CXXFLAGS=-O1 -fno-omit-frame-pointer -gline-tables-only -Wno-error=enum-constexpr-conversion -Wno-error=incompatible-function-pointer-types -Wno-error=int-conversion -Wno-error=deprecated-declarations -Wno-error=implicit-function-declaration -Wno-error=implicit-int -Wno-error=vla-cxx-extension -DFUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION -fprofile-instr-generate -fcoverage-mapping -pthread -Wl,--no-as-needed -Wl,-ldl -Wl,-lm -Wno-unused-command-line-argument -stdlib=libc++ -fno-sanitize=function,leak,vptr Step #3 - "compile-libfuzzer-coverage-x86_64": RUSTFLAGS=--cfg fuzzing -Cdebuginfo=1 -Cforce-frame-pointers -Cinstrument-coverage -C link-arg=-lc++ Step #3 - "compile-libfuzzer-coverage-x86_64": --------------------------------------------------------------- Step #3 - "compile-libfuzzer-coverage-x86_64": + sed -i 's/def do_override():/def do_override():\n return True\n\ndef do_override2():/g' _distutils_hack/__init__.py Step #3 - "compile-libfuzzer-coverage-x86_64": + pushd /src/distutils Step #3 - "compile-libfuzzer-coverage-x86_64": /src/distutils /src/setuptools Step #3 - "compile-libfuzzer-coverage-x86_64": + pip3 install . Step #3 - "compile-libfuzzer-coverage-x86_64": Processing ./. Step #3 - "compile-libfuzzer-coverage-x86_64": Installing build dependencies ... [?25l- \ | / - \ | done Step #3 - "compile-libfuzzer-coverage-x86_64": [?25h Getting requirements to build wheel ... [?25l- done Step #3 - "compile-libfuzzer-coverage-x86_64": /tmp/pip-build-env-6537vuce/overlay/lib/python3.10/site-packages/vcs_versioning/_backends/_git.py:709: BuildBackendWarning: "/src/distutils" is shallow and may cause errors Step #3 - "compile-libfuzzer-coverage-x86_64": pre_parse(wd) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25h Preparing metadata (pyproject.toml) ... [?25l- done Step #3 - "compile-libfuzzer-coverage-x86_64": /tmp/pip-build-env-6537vuce/overlay/lib/python3.10/site-packages/vcs_versioning/_backends/_git.py:709: BuildBackendWarning: "/src/distutils" is shallow and may cause errors Step #3 - "compile-libfuzzer-coverage-x86_64": pre_parse(wd) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25hRequirement already satisfied: packaging in /usr/local/lib/python3.10/site-packages (from distutils==0.1.dev1+g493fff0da) (25.0) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting jaraco.functools>=4 (from distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading jaraco_functools-4.6.0-py3-none-any.whl.metadata (2.9 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting more_itertools (from distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading more_itertools-11.1.0-py3-none-any.whl.metadata (41 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting jaraco.text (from distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading jaraco_text-4.3.0-py3-none-any.whl.metadata (3.8 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting jaraco.context>=4.1 (from jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading jaraco_context-6.1.2-py3-none-any.whl.metadata (4.2 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting typer-slim (from jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading typer_slim-0.24.0-py3-none-any.whl.metadata (4.2 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting backports.tarfile (from jaraco.context>=4.1->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading backports.tarfile-1.2.0-py3-none-any.whl.metadata (2.0 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting typer>=0.24.0 (from typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading typer-0.29.1-py3-none-any.whl.metadata (16 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting pydantic>=2.5.3 (from typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading pydantic-2.14.4-py3-none-any.whl.metadata (143 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting shellingham>=1.3.0 (from typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading shellingham-1.5.4-py2.py3-none-any.whl.metadata (3.5 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting rich>=13.8.0 (from typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading rich-15.0.0-py3-none-any.whl.metadata (18 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting annotated-doc>=0.0.2 (from typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading annotated_doc-0.0.6-py3-none-any.whl.metadata (6.5 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting annotated-types>=0.6.0 (from pydantic>=2.5.3->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading annotated_types-0.8.0-py3-none-any.whl.metadata (15 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting pydantic-core==2.50.5 (from pydantic>=2.5.3->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading pydantic_core-2.50.5-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl.metadata (6.6 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting typing-extensions>=4.16.0 (from pydantic>=2.5.3->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Using cached typing_extensions-4.16.0-py3-none-any.whl.metadata (3.3 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting typing-inspection>=0.4.4 (from pydantic>=2.5.3->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading typing_inspection-0.4.5-py3-none-any.whl.metadata (2.6 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting markdown-it-py>=2.2.0 (from rich>=13.8.0->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading markdown_it_py-4.3.0-py3-none-any.whl.metadata (7.9 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting pygments<3.0.0,>=2.13.0 (from rich>=13.8.0->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading pygments-2.21.0-py3-none-any.whl.metadata (2.5 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Collecting mdurl~=0.1 (from markdown-it-py>=2.2.0->rich>=13.8.0->typer>=0.24.0->typer-slim->jaraco.text->distutils==0.1.dev1+g493fff0da) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading mdurl-0.1.2-py3-none-any.whl.metadata (1.6 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading jaraco_functools-4.6.0-py3-none-any.whl (11 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading jaraco_text-4.3.0-py3-none-any.whl (14 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading jaraco_context-6.1.2-py3-none-any.whl (7.9 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading backports.tarfile-1.2.0-py3-none-any.whl (30 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading more_itertools-11.1.0-py3-none-any.whl (72 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading typer_slim-0.24.0-py3-none-any.whl (3.4 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading typer-0.29.1-py3-none-any.whl (121 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading annotated_doc-0.0.6-py3-none-any.whl (5.3 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading pydantic-2.14.4-py3-none-any.whl (494 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading pydantic_core-2.50.5-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl (2.3 MB) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25l ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0.0/2.3 MB ? eta -:--:--  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 75.5 MB/s 0:00:00 Step #3 - "compile-libfuzzer-coverage-x86_64": [?25hDownloading annotated_types-0.8.0-py3-none-any.whl (13 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading rich-15.0.0-py3-none-any.whl (310 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading pygments-2.21.0-py3-none-any.whl (1.3 MB) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25l ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0.0/1.3 MB ? eta -:--:--  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.3/1.3 MB 68.9 MB/s 0:00:00 Step #3 - "compile-libfuzzer-coverage-x86_64": [?25hDownloading markdown_it_py-4.3.0-py3-none-any.whl (96 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading mdurl-0.1.2-py3-none-any.whl (10.0 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading shellingham-1.5.4-py2.py3-none-any.whl (9.8 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Using cached typing_extensions-4.16.0-py3-none-any.whl (45 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Downloading typing_inspection-0.4.5-py3-none-any.whl (14 kB) Step #3 - "compile-libfuzzer-coverage-x86_64": Building wheels for collected packages: distutils Step #3 - "compile-libfuzzer-coverage-x86_64": Building wheel for distutils (pyproject.toml) ... [?25l- \ done Step #3 - "compile-libfuzzer-coverage-x86_64": /tmp/pip-build-env-6537vuce/overlay/lib/python3.10/site-packages/vcs_versioning/_backends/_git.py:709: BuildBackendWarning: "/src/distutils" is shallow and may cause errors Step #3 - "compile-libfuzzer-coverage-x86_64": pre_parse(wd) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25h Created wheel for distutils: filename=distutils-0.1.dev1+g493fff0da-py3-none-any.whl size=259913 sha256=7d5bc235be3b8437a8dd86077b79f66fd7dd7f131bbb8a0c8e3c8610bff6d3fb Step #3 - "compile-libfuzzer-coverage-x86_64": Stored in directory: /tmp/pip-ephem-wheel-cache-8okl9g0n/wheels/89/8c/25/e009dafa81410d4048f169b638413bbfb3efd099f80f477671 Step #3 - "compile-libfuzzer-coverage-x86_64": Successfully built distutils Step #3 - "compile-libfuzzer-coverage-x86_64": Installing collected packages: typing-extensions, shellingham, pygments, more_itertools, mdurl, backports.tarfile, annotated-types, annotated-doc, typing-inspection, pydantic-core, markdown-it-py, jaraco.functools, jaraco.context, rich, pydantic, typer, typer-slim, jaraco.text, distutils Step #3 - "compile-libfuzzer-coverage-x86_64": [?25l  ━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  2/19 [pygments]  ━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  2/19 [pygments]  ━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  2/19 [pygments]  ━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  2/19 [pygments]  ━━━━╺━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━  2/19 [pygments]  ━━━━━━━━━━━━━━━━╸━━━━━━━━━━━━━━━━━━━━━━━  8/19 [typing-inspection]  ━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━━━━━━━ 11/19 [jaraco.functools]  ━━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━━━ 13/19 [rich]  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━ 14/19 [pydantic]  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━ 14/19 [pydantic]  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╸━━━━━━━━ 15/19 [typer]  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╸━━ 18/19 [distutils]  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 19/19 [distutils] Step #3 - "compile-libfuzzer-coverage-x86_64": [?25h Successfully installed annotated-doc-0.0.6 annotated-types-0.8.0 backports.tarfile-1.2.0 distutils-0.1.dev1+g493fff0da jaraco.context-6.1.2 jaraco.functools-4.6.0 jaraco.text-4.3.0 markdown-it-py-4.3.0 mdurl-0.1.2 more_itertools-11.1.0 pydantic-2.14.4 pydantic-core-2.50.5 pygments-2.21.0 rich-15.0.0 shellingham-1.5.4 typer-0.29.1 typer-slim-0.24.0 typing-extensions-4.16.0 typing-inspection-0.4.5 Step #3 - "compile-libfuzzer-coverage-x86_64": WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. Step #3 - "compile-libfuzzer-coverage-x86_64": + popd Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools Step #3 - "compile-libfuzzer-coverage-x86_64": + pip3 install . Step #3 - "compile-libfuzzer-coverage-x86_64": Processing ./. Step #3 - "compile-libfuzzer-coverage-x86_64": Getting requirements to build wheel ... [?25l- \ done Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/config/pyprojecttoml.py:72: BuildBackendWarning: `[tool.distutils]` in `pyproject.toml` is still *experimental* and likely to change in future releases. Step #3 - "compile-libfuzzer-coverage-x86_64": config = read_configuration(filepath, True, ignore_option_errors, dist) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25h Preparing metadata (pyproject.toml) ... [?25l- \ done Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/config/pyprojecttoml.py:72: BuildBackendWarning: `[tool.distutils]` in `pyproject.toml` is still *experimental* and likely to change in future releases. Step #3 - "compile-libfuzzer-coverage-x86_64": config = read_configuration(filepath, True, ignore_option_errors, dist) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25hBuilding wheels for collected packages: setuptools Step #3 - "compile-libfuzzer-coverage-x86_64": Building wheel for setuptools (pyproject.toml) ... [?25l- \ | / done Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/config/pyprojecttoml.py:72: BuildBackendWarning: `[tool.distutils]` in `pyproject.toml` is still *experimental* and likely to change in future releases. Step #3 - "compile-libfuzzer-coverage-x86_64": config = read_configuration(filepath, True, ignore_option_errors, dist) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools._distutils.compilers.C.tests' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools._distutils.compilers.C.tests' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools._distutils.compilers.C.tests' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools._distutils.compilers.C.tests' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools._distutils.compilers.C.tests' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools._distutils.tests' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools._distutils.tests' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools._distutils.tests' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools._distutils.tests' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools._distutils.tests' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools._distutils.tests.compat' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools._distutils.tests.compat' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools._distutils.tests.compat' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools._distutils.tests.compat' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools._distutils.tests.compat' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests.compat' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests.compat' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests.compat' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests.compat' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests.compat' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests.config' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests.config' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests.config' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests.config' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests.config' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests.config.downloads' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests.config.downloads' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests.config.downloads' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests.config.downloads' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests.config.downloads' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests.indexes.test_links_priority' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests.indexes.test_links_priority' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests.indexes.test_links_priority' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests.indexes.test_links_priority' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests.indexes.test_links_priority' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests.indexes.test_links_priority.simple.foobar' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests.indexes.test_links_priority.simple.foobar' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests.indexes.test_links_priority.simple.foobar' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests.indexes.test_links_priority.simple.foobar' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests.indexes.test_links_priority.simple.foobar' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": /src/setuptools/setuptools/command/build_py.py:215: BuildBackendWarning: Package 'setuptools.tests.integration' is absent from the `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": # Package would be ignored # Step #3 - "compile-libfuzzer-coverage-x86_64": ############################ Step #3 - "compile-libfuzzer-coverage-x86_64": Python recognizes 'setuptools.tests.integration' as an importable package[^1], Step #3 - "compile-libfuzzer-coverage-x86_64": but it is absent from setuptools' `packages` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": This leads to an ambiguous overall configuration. If you want to distribute this Step #3 - "compile-libfuzzer-coverage-x86_64": package, please make sure that 'setuptools.tests.integration' is explicitly added Step #3 - "compile-libfuzzer-coverage-x86_64": to the `packages` configuration field. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Alternatively, you can also rely on setuptools' discovery methods Step #3 - "compile-libfuzzer-coverage-x86_64": (for example by using `find_namespace_packages(...)`/`find_namespace:` Step #3 - "compile-libfuzzer-coverage-x86_64": instead of `find_packages(...)`/`find:`). Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package discovery" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": If you don't want 'setuptools.tests.integration' to be distributed and are Step #3 - "compile-libfuzzer-coverage-x86_64": already explicitly excluding 'setuptools.tests.integration' via Step #3 - "compile-libfuzzer-coverage-x86_64": `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, Step #3 - "compile-libfuzzer-coverage-x86_64": you can try to use `exclude_package_data`, or `include-package-data=False` in Step #3 - "compile-libfuzzer-coverage-x86_64": combination with a more fine grained `package-data` configuration. Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": You can read more about "package data files" on setuptools documentation page: Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": - https://setuptools.pypa.io/en/latest/userguide/datafiles.html Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": [^1]: For Python, any directory (with suitable naming) can be imported, Step #3 - "compile-libfuzzer-coverage-x86_64": even if it does not contain any `.py` files. Step #3 - "compile-libfuzzer-coverage-x86_64": On the other hand, currently there is no concept of package data Step #3 - "compile-libfuzzer-coverage-x86_64": directory, all directories are treated like packages. Step #3 - "compile-libfuzzer-coverage-x86_64": ******************************************************************************** Step #3 - "compile-libfuzzer-coverage-x86_64": Step #3 - "compile-libfuzzer-coverage-x86_64": !! Step #3 - "compile-libfuzzer-coverage-x86_64": check.warn(importable) Step #3 - "compile-libfuzzer-coverage-x86_64": [?25h Created wheel for setuptools: filename=setuptools-84.2.1-py3-none-any.whl size=876615 sha256=ebe4366c00bbdf7c97c37bb251c119d794aea4a593b92150814b9482d45996bb Step #3 - "compile-libfuzzer-coverage-x86_64": Stored in directory: /tmp/pip-ephem-wheel-cache-pnglc26w/wheels/c5/57/53/fa466557849754618af19b4a81a0e8e20e63f66f097685f632 Step #3 - "compile-libfuzzer-coverage-x86_64": Successfully built setuptools Step #3 - "compile-libfuzzer-coverage-x86_64": Installing collected packages: setuptools Step #3 - "compile-libfuzzer-coverage-x86_64": Attempting uninstall: setuptools Step #3 - "compile-libfuzzer-coverage-x86_64": Found existing installation: setuptools 72.1.0 Step #3 - "compile-libfuzzer-coverage-x86_64": Uninstalling setuptools-72.1.0: Step #3 - "compile-libfuzzer-coverage-x86_64": Successfully uninstalled setuptools-72.1.0 Step #3 - "compile-libfuzzer-coverage-x86_64": Successfully installed setuptools-84.2.1 Step #3 - "compile-libfuzzer-coverage-x86_64": WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning. Step #3 - "compile-libfuzzer-coverage-x86_64": + cd ../ Step #3 - "compile-libfuzzer-coverage-x86_64": + mkdir forbuilding Step #3 - "compile-libfuzzer-coverage-x86_64": + cd forbuilding Step #3 - "compile-libfuzzer-coverage-x86_64": ++ find /src -name 'fuzz_*.py' Step #3 - "compile-libfuzzer-coverage-x86_64": + for fuzzer in $(find "$SRC" -name 'fuzz_*.py') Step #3 - "compile-libfuzzer-coverage-x86_64": + compile_python_fuzzer /src/fuzz_config_pyprojecttoml.py Step #3 - "compile-libfuzzer-coverage-x86_64": + fuzzer_path=/src/fuzz_config_pyprojecttoml.py Step #3 - "compile-libfuzzer-coverage-x86_64": + shift 1 Step #3 - "compile-libfuzzer-coverage-x86_64": ++ basename -s .py /src/fuzz_config_pyprojecttoml.py Step #3 - "compile-libfuzzer-coverage-x86_64": + fuzzer_basename=fuzz_config_pyprojecttoml Step #3 - "compile-libfuzzer-coverage-x86_64": + fuzzer_package=fuzz_config_pyprojecttoml.pkg Step #3 - "compile-libfuzzer-coverage-x86_64": + PYFUZZ_WORKPATH=/src/pyfuzzworkdir/ Step #3 - "compile-libfuzzer-coverage-x86_64": + FUZZ_WORKPATH=/src/pyfuzzworkdir//fuzz_config_pyprojecttoml Step #3 - "compile-libfuzzer-coverage-x86_64": + [[ coverage = *introspector* ]] Step #3 - "compile-libfuzzer-coverage-x86_64": + [[ coverage = *coverage* ]] Step #3 - "compile-libfuzzer-coverage-x86_64": + cat Step #3 - "compile-libfuzzer-coverage-x86_64": + cat coverage_wrapper.py /src/fuzz_config_pyprojecttoml.py Step #3 - "compile-libfuzzer-coverage-x86_64": + mv tmp_fuzzer_coverage.py /src/fuzz_config_pyprojecttoml.py Step #3 - "compile-libfuzzer-coverage-x86_64": + [[ 0 != \0 ]] Step #3 - "compile-libfuzzer-coverage-x86_64": + rm -rf /src/pyfuzzworkdir/ Step #3 - "compile-libfuzzer-coverage-x86_64": + mkdir /src/pyfuzzworkdir/ /src/pyfuzzworkdir//fuzz_config_pyprojecttoml Step #3 - "compile-libfuzzer-coverage-x86_64": + pyinstaller --distpath /workspace/out/libfuzzer-coverage-x86_64 --workpath=/src/pyfuzzworkdir//fuzz_config_pyprojecttoml --onefile --name fuzz_config_pyprojecttoml.pkg /src/fuzz_config_pyprojecttoml.py Step #3 - "compile-libfuzzer-coverage-x86_64": Traceback (most recent call last): Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/bin/pyinstaller", line 8, in Step #3 - "compile-libfuzzer-coverage-x86_64": sys.exit(_console_script_run()) Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/__main__.py", line 231, in _console_script_run Step #3 - "compile-libfuzzer-coverage-x86_64": run() Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/__main__.py", line 172, in run Step #3 - "compile-libfuzzer-coverage-x86_64": parser = generate_parser() Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/__main__.py", line 137, in generate_parser Step #3 - "compile-libfuzzer-coverage-x86_64": import PyInstaller.building.build_main Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/building/build_main.py", line 28, in Step #3 - "compile-libfuzzer-coverage-x86_64": from PyInstaller.building.api import COLLECT, EXE, MERGE, PYZ Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/building/api.py", line 33, in Step #3 - "compile-libfuzzer-coverage-x86_64": from PyInstaller.building.splash import Splash # argument type validation in EXE Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/building/splash.py", line 23, in Step #3 - "compile-libfuzzer-coverage-x86_64": from PyInstaller.depend import bindepend Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/depend/bindepend.py", line 25, in Step #3 - "compile-libfuzzer-coverage-x86_64": from PyInstaller.depend import dylib, utils Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/depend/utils.py", line 31, in Step #3 - "compile-libfuzzer-coverage-x86_64": from PyInstaller.lib.modulegraph import modulegraph Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/PyInstaller/lib/modulegraph/modulegraph.py", line 34, in Step #3 - "compile-libfuzzer-coverage-x86_64": from altgraph.ObjectGraph import ObjectGraph Step #3 - "compile-libfuzzer-coverage-x86_64": File "/usr/local/lib/python3.10/site-packages/altgraph/__init__.py", line 142, in Step #3 - "compile-libfuzzer-coverage-x86_64": import pkg_resources Step #3 - "compile-libfuzzer-coverage-x86_64": ModuleNotFoundError: No module named 'pkg_resources' Step #3 - "compile-libfuzzer-coverage-x86_64": ********************************************************************************\nFailed to build.\nTo reproduce, run:\npython infra/helper.py build_image setuptools\npython infra/helper.py build_fuzzers --sanitizer coverage --engine libfuzzer --architecture x86_64 setuptools\n******************************************************************************** Finished Step #3 - "compile-libfuzzer-coverage-x86_64" ERROR ERROR: build step 3 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1