Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed task build cri-o #30

Open
bumiga opened this issue Jun 7, 2020 · 0 comments
Open

Failed task build cri-o #30

bumiga opened this issue Jun 7, 2020 · 0 comments

Comments

@bumiga
Copy link

bumiga commented Jun 7, 2020

fatal: [<all_ip_cluster>]: FAILED! => {"changed": true, "cmd": "cd /root/src/github.com/kubernetes-incubator/cri-o && make && make install && make install.systemd && make install.config\n", "delta": "0:01:04.153020", "end": "2020-06-07 16:33:29.004316", "msg": "non-zero return code", "rc": 2, "start": "2020-06-07 16:32:24.851296", "stderr": "flag provided but not defined: -mod\nusage: build [-o output] [-i] [build flags] [packages]\n\nBuild compiles the packages named by the import paths,\nalong with their dependencies, but it does not install the results.\n\nIf the arguments to build are a list of .go files, build treats\nthem as a list of source files specifying a single package.\n\nWhen compiling a single main package, build writes\nthe resulting executable to an output file named after\nthe first source file ('go build ed.go rx.go' writes 'ed' or 'ed.exe')\nor the source code directory ('go build unix/sam' writes 'sam' or 'sam.exe').\nThe '.exe' suffix is added when writing a Windows executable.\n\nWhen compiling multiple packages or a single non-main package,\nbuild compiles the packages but discards the resulting object,\nserving only as a check that the packages can be built.\n\nWhen compiling packages, build ignores files that end in '_test.go'.\n\nThe -o flag, only allowed when compiling a single package,\nforces build to write the resulting executable or object\nto the named output file, instead of the default behavior described\nin the last two paragraphs.\n\nThe -i flag installs the packages that are dependencies of the target.\n\nThe build flags are shared by the build, clean, get, install, list, run,\nand test commands:\n\n\t-a\n\t\tforce rebuilding of packages that are already up-to-date.\n\t-n\n\t\tprint the commands but do not run them.\n\t-p n\n\t\tthe number of programs, such as build commands or\n\t\ttest binaries, that can be run in parallel.\n\t\tThe default is the number of CPUs available.\n\t-race\n\t\tenable data race detection.\n\t\tSupported only on linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64.\n\t-msan\n\t\tenable interoperation with memory sanitizer.\n\t\tSupported only on linux/amd64,\n\t\tand only with Clang/LLVM as the host C compiler.\n\t-v\n\t\tprint the names of packages as they are compiled.\n\t-work\n\t\tprint the name of the temporary work directory and\n\t\tdo not delete it when exiting.\n\t-x\n\t\tprint the commands.\n\n\t-asmflags 'flag list'\n\t\targuments to pass on each go tool asm invocation.\n\t-buildmode mode\n\t\tbuild mode to use. See 'go help buildmode' for more.\n\t-compiler name\n\t\tname of compiler to use, as in runtime.Compiler (gccgo or gc).\n\t-gccgoflags 'arg list'\n\t\targuments to pass on each gccgo compiler/linker invocation.\n\t-gcflags 'arg list'\n\t\targuments to pass on each go tool compile invocation.\n\t-installsuffix suffix\n\t\ta suffix to use in the name of the package installation directory,\n\t\tin order to keep output separate from default builds.\n\t\tIf using the -race flag, the install suffix is automatically set to race\n\t\tor, if set explicitly, has _race appended to it. Likewise for the -msan\n\t\tflag. Using a -buildmode option that requires non-default compile flags\n\t\thas a similar effect.\n\t-ldflags 'flag list'\n\t\targuments to pass on each go tool link invocation.\n\t-linkshared\n\t\tlink against shared libraries previously created with\n\t\t-buildmode=shared.\n\t-pkgdir dir\n\t\tinstall and load all packages from dir instead of the usual locations.\n\t\tFor example, when building with a non-standard configuration,\n\t\tuse -pkgdir to keep generated packages in a separate location.\n\t-tags 'tag list'\n\t\ta list of build tags to consider satisfied during the build.\n\t\tFor more information about build tags, see the description of\n\t\tbuild constraints in the documentation for the go/build package.\n\t-toolexec 'cmd args'\n\t\ta program to use to invoke toolchain programs like vet and asm.\n\t\tFor example, instead of running asm, the go command will run\n\t\t'cmd args /path/to/asm '.\n\nThe list flags accept a space-separated list of strings. To embed spaces\nin an element in the list, surround it with either single or double quotes.\n\nFor more about specifying packages, see 'go help packages'.\nFor more about where packages and binaries are installed,\nrun 'go help gopath'.\nFor more about calling between Go and C/C++, run 'go help c'.\n\nNote: Build adheres to certain conventions such as those described\nby 'go help gopath'. Not all projects can follow these conventions,\nhowever. Installations that have their own conventions or that use\na separate software build system may choose to use lower-level\ninvocations such as 'go tool compile' and 'go tool link' to avoid\nsome of the overheads and design decisions of the build tool.\n\nSee also: go install, go get, go clean.\nmake: *** [bin/crio] Error 2", "stderr_lines": ["flag provided but not defined: -mod", "usage: build [-o output] [-i] [build flags] [packages]", "", "Build compiles the packages named by the import paths,", "along with their dependencies, but it does not install the results.", "", "If the arguments to build are a list of .go files, build treats", "them as a list of source files specifying a single package.", "", "When compiling a single main package, build writes", "the resulting executable to an output file named after", "the first source file ('go build ed.go rx.go' writes 'ed' or 'ed.exe')", "or the source code directory ('go build unix/sam' writes 'sam' or 'sam.exe').", "The '.exe' suffix is added when writing a Windows executable.", "", "When compiling multiple packages or a single non-main package,", "build compiles the packages but discards the resulting object,", "serving only as a check that the packages can be built.", "", "When compiling packages, build ignores files that end in '_test.go'.", "", "The -o flag, only allowed when compiling a single package,", "forces build to write the resulting executable or object", "to the named output file, instead of the default behavior described", "in the last two paragraphs.", "", "The -i flag installs the packages that are dependencies of the target.", "", "The build flags are shared by the build, clean, get, install, list, run,", "and test commands:", "", "\t-a", "\t\tforce rebuilding of packages that are already up-to-date.", "\t-n", "\t\tprint the commands but do not run them.", "\t-p n", "\t\tthe number of programs, such as build commands or", "\t\ttest binaries, that can be run in parallel.", "\t\tThe default is the number of CPUs available.", "\t-race", "\t\tenable data race detection.", "\t\tSupported only on linux/amd64, freebsd/amd64, darwin/amd64 and windows/amd64.", "\t-msan", "\t\tenable interoperation with memory sanitizer.", "\t\tSupported only on linux/amd64,", "\t\tand only with Clang/LLVM as the host C compiler.", "\t-v", "\t\tprint the names of packages as they are compiled.", "\t-work", "\t\tprint the name of the temporary work directory and", "\t\tdo not delete it when exiting.", "\t-x", "\t\tprint the commands.", "", "\t-asmflags 'flag list'", "\t\targuments to pass on each go tool asm invocation.", "\t-buildmode mode", "\t\tbuild mode to use. See 'go help buildmode' for more.", "\t-compiler name", "\t\tname of compiler to use, as in runtime.Compiler (gccgo or gc).", "\t-gccgoflags 'arg list'", "\t\targuments to pass on each gccgo compiler/linker invocation.", "\t-gcflags 'arg list'", "\t\targuments to pass on each go tool compile invocation.", "\t-installsuffix suffix", "\t\ta suffix to use in the name of the package installation directory,", "\t\tin order to keep output separate from default builds.", "\t\tIf using the -race flag, the install suffix is automatically set to race", "\t\tor, if set explicitly, has _race appended to it. Likewise for the -msan", "\t\tflag. Using a -buildmode option that requires non-default compile flags", "\t\thas a similar effect.", "\t-ldflags 'flag list'", "\t\targuments to pass on each go tool link invocation.", "\t-linkshared", "\t\tlink against shared libraries previously created with", "\t\t-buildmode=shared.", "\t-pkgdir dir", "\t\tinstall and load all packages from dir instead of the usual locations.", "\t\tFor example, when building with a non-standard configuration,", "\t\tuse -pkgdir to keep generated packages in a separate location.", "\t-tags 'tag list'", "\t\ta list of build tags to consider satisfied during the build.", "\t\tFor more information about build tags, see the description of", "\t\tbuild constraints in the documentation for the go/build package.", "\t-toolexec 'cmd args'", "\t\ta program to use to invoke toolchain programs like vet and asm.", "\t\tFor example, instead of running asm, the go command will run", "\t\t'cmd args /path/to/asm '.", "", "The list flags accept a space-separated list of strings. To embed spaces", "in an element in the list, surround it with either single or double quotes.", "", "For more about specifying packages, see 'go help packages'.", "For more about where packages and binaries are installed,", "run 'go help gopath'.", "For more about calling between Go and C/C++, run 'go help c'.", "", "Note: Build adheres to certain conventions such as those described", "by 'go help gopath'. Not all projects can follow these conventions,", "however. Installations that have their own conventions or that use", "a separate software build system may choose to use lower-level", "invocations such as 'go tool compile' and 'go tool link' to avoid", "some of the overheads and design decisions of the build tool.", "", "See also: go install, go get, go clean.", "make: *** [bin/crio] Error 2"], "stdout": "mkdir -p "/root/src/github.com/kubernetes-incubator/cri-o/_output/src/github.com/cri-o"\nln -s "/root/src/github.com/kubernetes-incubator/cri-o" "/root/src/github.com/kubernetes-incubator/cri-o/_output/src/github.com/cri-o/cri-o"\ntouch "/root/src/github.com/kubernetes-incubator/cri-o/_output/.gopathok"\nGO111MODULE=on go build --mod=vendor -ldflags '-s -w -X github.com/cri-o/cri-o/internal/pkg/criocli.DefaultsPath="" -X github.com/cri-o/cri-o/internal/version.buildDate=2020-06-07T21:33:27Z -X github.com/cri-o/cri-o/internal/version.gitCommit=5cbf694c34f8d1af19eb873e39057663a4830635 -X github.com/cri-o/cri-o/internal/version.gitTreeState=clean ' -tags "containers_image_ostree_stub seccomp selinux" -o bin/crio github.com/cri-o/cri-o/cmd/crio", "stdout_lines": ["mkdir -p "/root/src/github.com/kubernetes-incubator/cri-o/_output/src/github.com/cri-o"", "ln -s "/root/src/github.com/kubernetes-incubator/cri-o" "/root/src/github.com/kubernetes-incubator/cri-o/_output/src/github.com/cri-o/cri-o"", "touch "/root/src/github.com/kubernetes-incubator/cri-o/_output/.gopathok"", "GO111MODULE=on go build --mod=vendor -ldflags '-s -w -X github.com/cri-o/cri-o/internal/pkg/criocli.DefaultsPath="" -X github.com/cri-o/cri-o/internal/version.buildDate=2020-06-07T21:33:27Z -X github.com/cri-o/cri-o/internal/version.gitCommit=5cbf694c34f8d1af19eb873e39057663a4830635 -X github.com/cri-o/cri-o/internal/version.gitTreeState=clean ' -tags "containers_image_ostree_stub seccomp selinux" -o bin/crio github.com/cri-o/cri-o/cmd/crio"]}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant