Bazel remote cache is enabled, generating .bazelrcs ... CC:13.2.1,PY:3.12.2,RPM:4.19.1.1 create_bazel_cache_rcs.sh: Configuring '/root/.bazelrc' and '/etc/bazel.bazelrc' with # ------------------------------------------------------------------------------ startup --host_jvm_args=-Dbazel.DigestFunction=sha256 build --remote_local_fallback build --remote_cache=http://bazel-cache.kubevirt-prow:8080/kubevirt/containerized-data-importer,379e6e538d965addcb45dc681bc87528 # ------------------------------------------------------------------------------ Adding /etc/docker-mirror-proxy/ca.crt as a trusted root CA Enabling IPV6. net.ipv6.conf.all.disable_ipv6 = 0 net.ipv6.conf.all.forwarding = 1 Podman in Container enabled, initializing in podman compatible mode... Waiting for podman socket to be ready, sleeping for 1 seconds. Waiting for podman socket to be ready, sleeping for 2 seconds. Waiting for podman socket to be ready, sleeping for 3 seconds. Waiting for podman socket to be ready, sleeping for 4 seconds. ================================================================================ Done setting up podman in container. mkdir: cannot create directory '/root/.docker': File exists + /bin/sh -c 'make fossa' ./hack/build/bazel-docker.sh "FOSSA_TOKEN_FILE=/root/.docker/secrets/fossa/token PULL_BASE_REF=main CI=true ./hack/fossa.sh" CDI_CRI: docker, CDI_CONTAINER_BUILDCMD: docker kubevirt-cdi-volume Making sure output directory exists... Trying to pull quay.io/kubevirt/kubevirt-cdi-bazel-builder:2401240332-bbc3643a6... Getting image source signatures Copying blob sha256:8e253be5e39da4ddaa068875d9d8e7fd5a3d1decffc7dd862e2517a0b5905f7b Copying blob sha256:80e3f9e4367d320ff908433688f7cecff0283ff90e6378fd7d627c62eb87bb95 Copying config sha256:041cd29046f61dc6080690cee81db0ae6ea64b82a63389ef70b44dd9ba69d536 Writing manifest to image destination go version go1.21.5 linux/amd64 go version go1.21.5 linux/amd64 Starting rsyncd Rsyncing /home/prow/go/src/github.com/kubevirt/containerized-data-importer to container 923985c5558aa1d630d020ca157fc7c7654bde56300e78e2d91917b7001e9e7a Starting bazel server go version go1.21.5 linux/amd64 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 13334 100 13334 0 0 100k 0 --:--:-- --:--:-- --:--:-- 99k 100 13334 100 13334 0 0 98k 0 --:--:-- --:--:-- --:--:-- 97k fossas/fossa-cli info checking GitHub for latest tag fossas/fossa-cli info found fossa-cli 3.9.8 binary for linux/amd64 at https://github.com/fossas/fossa-cli/releases/download/v3.9.8/fossa_3.9.8_linux_amd64.tar.gz fossas/fossa-cli info fossas/fossa-cli info ------ fossas/fossa-cli info Notice fossas/fossa-cli info ------ fossas/fossa-cli info fossas/fossa-cli info FOSSA collects warnings, errors, and usage data to improve fossas/fossa-cli info the FOSSA CLI and your experience. fossas/fossa-cli info fossas/fossa-cli info Read more: https://github.com/fossas/fossa-cli/blob/master/docs/telemetry.md fossas/fossa-cli info fossas/fossa-cli info If you want to prevent any telemetry data from being sent to fossas/fossa-cli info the server, you can opt out of telemetry by setting fossas/fossa-cli info FOSSA_TELEMETRY_SCOPE environment variable to 'off' in your shell. fossas/fossa-cli info fossas/fossa-cli info For example: fossas/fossa-cli info FOSSA_TELEMETRY_SCOPE=off fossa analyze fossas/fossa-cli info fossas/fossa-cli info fossas/fossa-cli info installed /usr/local/bin/fossa Unable to infer project revision from VCS, using current timestamp as the revision. [ 5 Waiting / 2 Running / 0 Completed ] [ 32 Waiting / 4 Running / 1 Completed ] [ 30 Waiting / 4 Running / 3 Completed ] [ 29 Waiting / 4 Running / 4 Completed ] [ 27 Waiting / 4 Running / 6 Completed ] [ 25 Waiting / 4 Running / 8 Completed ] [ 24 Waiting / 4 Running / 9 Completed ] [ 23 Waiting / 4 Running / 10 Completed ] [ 21 Waiting / 4 Running / 12 Completed ] [ 20 Waiting / 4 Running / 13 Completed ] [ 19 Waiting / 4 Running / 14 Completed ] [ 18 Waiting / 4 Running / 15 Completed ] [ 17 Waiting / 4 Running / 16 Completed ] [ 16 Waiting / 4 Running / 17 Completed ] [ 15 Waiting / 4 Running / 18 Completed ] [ 13 Waiting / 4 Running / 20 Completed ] [ 12 Waiting / 4 Running / 21 Completed ] Skipping npm project at "/root/go/src/kubevirt.io/containerized-data-importer/vendor/github.com/blang/semver/": no filters matched [ 9 Waiting / 4 Running / 25 Completed ] Analyzing gomod project at /root/go/src/kubevirt.io/containerized-data-importer/ [ 9 Waiting / 4 Running / 26 Completed ] [ 8 Waiting / 4 Running / 27 Completed ] [ 7 Waiting / 4 Running / 28 Completed ] [ 6 Waiting / 4 Running / 29 Completed ] [ 6 Waiting / 3 Running / 30 Completed ] [ 5 Waiting / 4 Running / 30 Completed ] [ 4 Waiting / 4 Running / 31 Completed ] [ 3 Waiting / 4 Running / 32 Completed ] [ 2 Waiting / 4 Running / 33 Completed ] [ 1 Waiting / 4 Running / 34 Completed ] [ 0 Waiting / 4 Running / 35 Completed ] [ 0 Waiting / 3 Running / 36 Completed ] [ 0 Waiting / 2 Running / 37 Completed ] [ 0 Waiting / 1 Running / 38 Completed ] NOTE: /root/go/src/kubevirt.io/containerized-data-importer/ analyzed using V3 Go Resolver. As of v3.8.5 we have changed our dynamic Go strategy. If you've analyzed this project before, results may have changed. See https://github.com/fossas/fossa-cli/blob/master/docs/references/strategies/languages/golang/v3-go-resolver-transition-qa.md for more information. NOTE: path dependency detected in project: gomod at: /root/go/src/kubevirt.io/containerized-data-importer/! To enable path dependency analysis, use: --experimental-analyze-path-dependencies flag. See https://github.com/fossas/fossa-cli/blob/v3.9.8/docs/references/experimental/path-dependency.md for more information. FOSSA CLI does not support reachability analysis for: gomod@/root/go/src/kubevirt.io/containerized-data-importer/ yet. (skipping) Scan Summary ------------ fossa-cli version 3.9.8 (revision b5f97eb2cd7d compiled with ghc-9.4) fossa endpoint server version: 4.20.3 2 projects scanned; 1 skipped, 1 succeeded, 0 failed, 0 analysis warnings * gomod project in "/root/go/src/kubevirt.io/containerized-data-importer/": succeeded * npm project in "/root/go/src/kubevirt.io/containerized-data-importer/vendor/github.com/blang/semver/": skipped (exclusion filters) - Reachability analysis ** npm project in "/root/go/src/kubevirt.io/containerized-data-importer/vendor/github.com/blang/semver/": skipped (no dependency analysis) ** gomod project in "/root/go/src/kubevirt.io/containerized-data-importer/": skipped (not supported) You can pass `--debug` option to eagerly show all warning and failure messages. You can also view analysis summary with warning and error messages at: "/tmp/fossa-analyze-scan-summary.txt" ------------ Organization: (13072) does not support reachability. Skipping reachability analysis upload. For reachability, refer to: https://docs.fossa.com/docs/reachability Using project name: `git@github.com:kubevirt/containerized-data-importer.git` Using revision: `2024-03-10T10:08:59Z` Using branch: `main` ============================================================ View FOSSA Report: https://app.fossa.com/projects/custom%2b13072%2fgit%40github.com:kubevirt%2fcontainerized-data-importer.git/refs/branch/main/2024-03-10T10:08:59Z ============================================================ Unable to infer project revision from VCS, using current timestamp as the revision. Using project name: `git@github.com:kubevirt/containerized-data-importer.git` Using revision: `2024-03-10T10:08:59Z` [ Checking build completion for 2024-03-10T10:08:59Z... ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusCreated ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for build completion (revision 2024-03-10T10:08:59Z)... last status: StatusRunning ] [ Waiting for issue scan completion... ] [ERROR] ======================================================================== Tested Following Project: ======================================================================== Project Title: git@github.com:kubevirt/containerized-data-importer.git Project Revision: 2024-03-10T10:08:59Z Project Visibility: private Project Targets: - gomod: [go.mod] COMPLIANCE ISSUES (Total 1) ======================================================================== Flagged by Policy (Total 1) ======================================================================== ⚑ GPL-3.0-or-later license detected in github.com/gorhill/cronexpr@88b0669f7d75 More information: https://app.fossa.com/projects/custom%2B13072%2Fgit%40github.com%3Akubevirt%2Fcontainerized-data-importer.git/refs/branch/master/2024-03-10T10%3A08%3A59Z/issues/licensing/4930821 [ERROR] An issue occurred *** Relevant Errors *** Error: The scan has revealed issues. Number of issues found: 1 make: *** [Makefile:168: fossa] Error 1 + EXIT_VALUE=2 + set +o xtrace Cleaning up after podman in container. ================================================================================ Cleaning up after podman time="2024-03-10T10:12:38Z" level=warning msg="StopSignal SIGTERM failed to stop container kubevirt-cdi-volume-bazel-server in 10 seconds, resorting to SIGKILL" 923985c5558aa1d630d020ca157fc7c7654bde56300e78e2d91917b7001e9e7a /usr/local/bin/runner.sh: line 50: wait: pid 49 is not a child of this shell ================================================================================ Done cleaning up after podman in container.