[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1064362: golang-k8s-kube-openapi: FTBFS on riscv64 due to test timeout



Source: golang-k8s-kube-openapi
Version: 0.0~git20231214.ab13479-1
Severity: important
Tags: patch ftbfs upstream fixed-upstream
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@lists.debian.org

Dear maintainer,

golang-k8s-kube-openapi fails to build from source on riscv64 with a
timeout in on test:

| Running Suite: Integration Test Suite - /<<PKGBUILDDIR>>/_build/src/k8s.io/kube-openapi/test/integration
| ================================================================================================================================================================
| Random Seed: 1707440586
| 
| Will run 4 of 4 specs
| ------------------------------
| [BeforeSuite] [FAILED] [39.046 seconds]
| [BeforeSuite] 
| /<<PKGBUILDDIR>>/_build/src/k8s.io/kube-openapi/test/integration/integration_suite_test.go:70
| 
|   Timeline >>
|   STEP: building openapi-gen @ 02/09/24 01:03:06.541
|   STEP: processing go idl with openapi-gen @ 02/09/24 01:03:35.566
|   [FAILED] in [BeforeSuite] - /<<PKGBUILDDIR>>/_build/src/k8s.io/kube-openapi/test/integration/integration_suite_test.go:101 @ 02/09/24 01:03:45.586
|   << Timeline
| 
|   [FAILED] Timed out after 10.004s.
|   Expected process to exit.  It did not.
|   In [BeforeSuite] at: /<<PKGBUILDDIR>>/_build/src/k8s.io/kube-openapi/test/integration/integration_suite_test.go:101 @ 02/09/24 01:03:45.586
| ------------------------------
| 
| Summarizing 1 Failure:
|   [FAIL] [BeforeSuite] 
|   /<<PKGBUILDDIR>>/_build/src/k8s.io/kube-openapi/test/integration/integration_suite_test.go:101
| 
| Ran 0 of 4 Specs in 39.056 seconds
| FAIL! -- A BeforeSuite node failed so all tests were skipped.
| --- FAIL: TestGenerators (39.06s)
| FAIL
| FAIL    k8s.io/kube-openapi/test/integration    39.125s
| === RUN   TestConvertGolden
| --- PASS: TestConvertGolden (0.15s)
| PASS
| ok      k8s.io/kube-openapi/test/integration/openapiconv        0.245s
| FAIL
| dh_auto_test: error: cd _build && go test -vet=off -v -p 4 k8s.io/kube-openapi/cmd/openapi-gen k8s.io/kube-openapi/cmd/openapi-gen/args k8s.io/kube-openapi/cmd/openapi2smd k8s.io/kube-openapi/pkg/aggregator k8s.io/kube-openapi/pkg/builder k8s.io/kube-openapi/pkg/builder3 k8s.io/kube-openapi/pkg/builder3/util k8s.io/kube-openapi/pkg/cached k8s.io/kube-openapi/pkg/common k8s.io/kube-openapi/pkg/common/restfuladapter k8s.io/kube-openapi/pkg/generators k8s.io/kube-openapi/pkg/generators/rules k8s.io/kube-openapi/pkg/handler k8s.io/kube-openapi/pkg/handler3 k8s.io/kube-openapi/pkg/idl k8s.io/kube-openapi/pkg/internal k8s.io/kube-openapi/pkg/internal/third_party/go-json-experiment/json k8s.io/kube-openapi/pkg/openapiconv k8s.io/kube-openapi/pkg/schemaconv k8s.io/kube-openapi/pkg/schemamutation k8s.io/kube-openapi/pkg/spec3 k8s.io/kube-openapi/pkg/util k8s.io/kube-openapi/pkg/util/jsontesting k8s.io/kube-openapi/pkg/util/proto k8s.io/kube-openapi/pkg/util/proto/testing k8s.io/kube-openapi/pkg/util/proto/validation k8s.io/kube-openapi/pkg/util/sets k8s.io/kube-openapi/pkg/validation/errors k8s.io/kube-openapi/pkg/validation/spec k8s.io/kube-openapi/pkg/validation/strfmt k8s.io/kube-openapi/pkg/validation/strfmt/bson k8s.io/kube-openapi/pkg/validation/validate k8s.io/kube-openapi/test/integration k8s.io/kube-openapi/test/integration/builder k8s.io/kube-openapi/test/integration/builder3 k8s.io/kube-openapi/test/integration/openapiconv k8s.io/kube-openapi/test/integration/pkg/generated k8s.io/kube-openapi/test/integration/testutil returned exit code 1
| make: *** [debian/rules:4: binary-arch] Error 25
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2

The full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=golang-k8s-kube-openapi&arch=riscv64&ver=0.0%7Egit20231214.ab13479-1&stamp=1707440925&raw=0

I submitted a patch upstream which has now been merged:
https://github.com/kubernetes/kube-openapi/commit/b4a5507e9c90356cbf47fb4ad34862ded7919b1e

Would it be possible to include that fix in the next upload?

Thanks
Aurelien


Reply to: