Community devfile registry integration testing is failing due to missing ginkgo

[michael-valdron]

/kind bug

Which area is this bug related to?

/area ci
/area registry

What versions of software are you using?

Go project

Operating System and version: N/A

Go Pkg Version: 1.23

Bug Summary

Describe the bug:

The integration testing check under devfile/registry PRs is currently failing due to the test script being unable to find the ginkgo binary. The recent update to use 1.23 environment might of had a breaking change with the availability of ginkgo and therefore a new approach might be needed.

To Reproduce:

Open any PRs right now and allow the OpenShift CI testing run.

Expected behavior

OpenShift CI testing environment should supply ginkgo to the test suite as its a required dependency.

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

ack: ollama' --slow-spec-threshold 120s --timeout 3h tests/odov3 -- -stacksPath /go/src/github.com/devfile/registry/stacks -stackDirs 'dotnet50 dotnet60 dotnet80 dotnetcore31 go/1.0.2 go/1.1.0 go/1.2.0 go/1.2.1 go/1.3.0 go/1.3.1 go/2.0.0 go/2.1.0 go/2.2.0 go/2.3.0 go/2.4.0 go/2.5.0 java-maven/1.2.0 java-maven/1.3.0 java-maven/1.3.1 java-openliberty java-openliberty-gradle java-quarkus/1.3.0 java-quarkus/1.3.1 java-quarkus/1.4.0 java-quarkus/1.4.1 java-quarkus/1.5.0 java-springboot/1.2.0 java-springboot/1.3.0 java-springboot/1.4.0 java-springboot/2.0.0 java-springboot/2.1.0 java-springboot/2.2.0 java-vertx/1.2.0 java-vertx/1.3.0 java-vertx/1.4.0 java-websphereliberty java-websphereliberty-gradle java-wildfly/1.1.0 java-wildfly/2.0.0 java-wildfly/2.0.1 java-wildfly/2.0.2 java-wildfly-bootable-jar/1.1.0 java-wildfly-bootable-jar/1.2.0 java-wildfly-bootable-jar/1.3.0 jhipster-online/2.33.0 jhipster-online/2.33.1 nodejs/2.1.1 nodejs/2.2.0 nodejs/2.2.1 nodejs-angular/2.0.2 nodejs-angular/2.1.0 nodejs-angular/2.2.0 nodejs-angular/2.2.1 nodejs-mongodb nodejs-nextjs/1.0.3 nodejs-nextjs/1.1.0 nodejs-nextjs/1.2.0 nodejs-nextjs/1.2.1 nodejs-nuxtjs/1.0.3 nodejs-nuxtjs/1.1.0 nodejs-nuxtjs/1.2.0 nodejs-nuxtjs/1.2.1 nodejs-react/2.0.2 nodejs-react/2.1.0 nodejs-react/2.2.1 nodejs-svelte/1.0.3 nodejs-svelte/1.1.0 nodejs-svelte/1.2.0 nodejs-svelte/1.2.1 nodejs-vue/1.0.2 nodejs-vue/1.1.0 nodejs-vue/1.2.0 nodejs-vue/1.2.1 ollama php-laravel/1.0.1 php-laravel/2.0.0 php-laravel/2.0.1 python/2.1.0 python/2.2.0 python/3.0.0 python/3.1.0 python-django udi' -odoPath /go/src/github.com/devfile/registry/odo
/go/src/github.com/devfile/registry/tests/check_odov3.sh: line 12: ginkgo: command not found
{"component":"entrypoint","error":"wrapped process failed: exit status 127","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2025-07-09T20:46:58Z"}
error: failed to execute wrapped command: exit status 127

Additional context

Any workaround?

No workarounds.

Suggestion on how to fix the bug

Implement a solution to making ginkgo available in the testing environment during the PR testing.