Skip to content

CSPL-3775 extract common code in tests #1788

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.

Sign up for GitHub

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

Open
kasiakoziol wants to merge 37 commits into
base: feature/test-refactoring
Choose a base branch
from

CSPL-3775 Adjust timeouts

23957e0
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Open

CSPL-3775 extract common code in tests #1788

CSPL-3775 Adjust timeouts
23957e0
Select commit
Loading
Failed to load commit list.
GitHub Actions / Integration Test Results - managerappframeworkm4 failed Apr 10, 2026 in 0s

81 tests run, 17 passed, 63 skipped, 1 failed.

Annotations

Check failure on line 1 in Running m4appfw-j2u

See this annotation in the file changed.

@github-actions github-actions / Integration Test Results - managerappframeworkm4

Running m4appfw-j2u.[It] m4appfw test Multisite Indexer Cluster with Search Head Cluster (M4) with App Framework integration, m4, managerappframeworkm4, appframework: can deploy a M4 SVA with App Framework enabled and reset operator pod while app download is in progress 

A suite timeout occurred
Raw output 
[TIMEDOUT] A suite timeout occurred
In [It] at: /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/m4/manager_appframework_test.go:1813 @ 04/10/26 17:00:55.681

This is the Progress Report generated when the suite timeout occurred:
  m4appfw test Multisite Indexer Cluster with Search Head Cluster (M4) with App Framework integration, m4, managerappframeworkm4, appframework: can deploy a M4 SVA with App Framework enabled and reset operator pod while app download is in progress (Spec Runtime: 1h57m58.088s)
    /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/m4/manager_appframework_test.go:1813
    In [It] (Node Runtime: 1h57m57.982s)
      /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/m4/manager_appframework_test.go:1813

    Spec Goroutine
    goroutine 18684 [select]
      k8s.io/apimachinery/pkg/util/wait.loopConditionUntilContext({0x29f3420, 0xc0003e8620}, {0x29e5910, 0xc00011fc00}, 0x1, 0x0, 0xc0000757b0)
        /home/runner/go/pkg/mod/k8s.io/apimachinery@v0.33.0/pkg/util/wait/loop.go:66
      k8s.io/apimachinery/pkg/util/wait.PollUntilContextTimeout({0x29f3308?, 0x3dc8e60?}, 0x12a05f200, 0x41c01f?, 0x1, 0xc000aa77b0)
        /home/runner/go/pkg/mod/k8s.io/apimachinery@v0.33.0/pkg/util/wait/poll.go:48
      github.com/splunk/splunk-operator/test/testenv.(*TestCaseEnv).VerifyAppState(0xc001238280, {0x29f3308, 0x3dc8e60}, 0xc00119b7c0, {0xc000951aa0, 0x13}, {0x2044f8e, 0xe}, {0xc0013bb880, 0x1c}, ...)
        /home/runner/work/splunk-operator/splunk-operator/test/testenv/verificationutils.go:1106
    > github.com/splunk/splunk-operator/test/appframework_aws/m4.init.func4.13.1()
        /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/m4/manager_appframework_test.go:1865
          | 
          | // Verify App Download is in progress on Cluster Manager
          > testcaseEnvInst.VerifyAppState(ctx, deployment, deployment.GetName(), cm.Kind, appSourceNameIdxc, appFileList, enterpriseApi.AppPkgDownloadComplete, enterpriseApi.AppPkgDownloadPending)
          | 
          | // Delete Operator pod while Install in progress
      github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xc000b78f08?, 0x4a2904?})
        /home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.1/internal/node.go:585
      github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3()
        /home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.1/internal/suite.go:946
      github.com/onsi/ginkgo/v2/internal.(*Suite).runNode in goroutine 71
        /home/runner/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.28.1/internal/suite.go:911

There were additional failures detected after the initial failure. These are visible in the timeline
View more details on GitHub Actions