-
Notifications
You must be signed in to change notification settings - Fork 75
Closed
Labels
area/apiEnhancement or issue related to the api/devfile specificationEnhancement or issue related to the api/devfile specificationarea/test-automationTest automation for devfile specification and libraryTest automation for devfile specification and librarykind/bugSomething isn't workingSomething isn't workingseverity/blockerIssues that prevent developers from workingIssues that prevent developers from working
Description
Which area this feature is related to?
/kind bug
Which area this bug is related to?
/area api
/area test-automation
Bug Summary
Describe the bug:
I've noticed that two workflows are failing for the API repo:
- The first one is the code coverage report. The error trace for this check is:
Run go test ./... -coverprofile cover.out
# k8s.io/apimachinery/third_party/forked/golang/reflect
Error: vendor/k8s.io/apimachinery/third_party/forked/golang/reflect/deep_equal.go:37[6](https://github.com/devfile/api/actions/runs/5425938477/job/14695275008#step:4:7):[7](https://github.com/devfile/api/actions/runs/5425938477/job/14695275008#step:4:8): undefined: reflect.Pointer
note: module requires Go 1.19
- The second one is the release typescript models. I've found 1 related issue error in /api/build/typescript-model/generate.sh #989
The error trace is:
Error: /typescript-model/generate.sh: line 63: [ERROR] Generated typescript model failed to build. Check it at /home/runner/work/api/api/api/build/typescript-model/workdir/typescript-models.: No such file or directory
Error: Process completed with exit code 127.
To Reproduce:
Check the actions tab here:
- Code coverage: https://github.com/devfile/api/actions/workflows/codecov.yaml
- Typescript Models: https://github.com/devfile/api/actions/workflows/release-typescript-models.yaml
Expected behavior
Both actions should be completed successful.
Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
The traces have been shared earlier above.
Any workaround?
Suggestion on how to fix the bug
svor
Metadata
Metadata
Assignees
Labels
area/apiEnhancement or issue related to the api/devfile specificationEnhancement or issue related to the api/devfile specificationarea/test-automationTest automation for devfile specification and libraryTest automation for devfile specification and librarykind/bugSomething isn't workingSomething isn't workingseverity/blockerIssues that prevent developers from workingIssues that prevent developers from working
Type
Projects
Status
Done ✅