Skip to content

managedusers reset bug fix

c02a5e0
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

postgres controllers metrics #1811

managedusers reset bug fix
c02a5e0
Select commit
Loading
Failed to load commit list.
GitHub Actions / Integration Test Results - appframeworksS1 failed Apr 10, 2026 in 0s

98 tests run, 4 passed, 92 skipped, 2 failed.

Annotations

Check failure on line 1 in Running s1appfw-lxf

See this annotation in the file changed.

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

Running s1appfw-lxf.[It] s1appfw test Standalone deployment (S1) with App Framework s1, integration, appframeworksS1, appframework: can deploy a Standalone instance with App Framework enabled, install apps, scale up, upgrade apps

A suite timeout occurred
Raw output
[TIMEDOUT] A suite timeout occurred
In [It] at: /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:618 @ 04/10/26 13:01:10.38

This is the Progress Report generated when the suite timeout occurred:
  s1appfw test Standalone deployment (S1) with App Framework s1, integration, appframeworksS1, appframework: can deploy a Standalone instance with App Framework enabled, install apps, scale up, upgrade apps (Spec Runtime: 3h43m11.277s)
    /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:618
    In [It] (Node Runtime: 3h43m9.975s)
      /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:618

    Spec Goroutine
    goroutine 276 [select]
      github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000262850, {0x297aa08, 0xc00044c860}, 0x1, {0x0, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558
      github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000262850, {0x297aa08, 0xc00044c860}, {0x0, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145
      github.com/splunk/splunk-operator/test/testenv.StandaloneReady({0x298be28, 0x3d40ce0}, 0xc000757c00, {0xc00044c850?, 0x1?}, 0xc000714008, 0xc0003c9680)
        /home/runner/work/splunk-operator/splunk-operator/test/testenv/verificationutils.go:110
    > github.com/splunk/splunk-operator/test/appframework_aws/s1.init.func3.6.1()
        /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:686
          | 
          | // Wait for Standalone to be in READY status
          > testenv.StandaloneReady(ctx, deployment, deployment.GetName(), standalone, testcaseEnvInst)
          | 
          | // Get Pod age to check for pod resets later
      github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xc000060930?, 0xc0009ceed0?})
        /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 45
        /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

Check failure on line 1 in Running s1appfw-lxf

See this annotation in the file changed.

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

Running s1appfw-lxf.[It] s1appfw test Standalone deployment (S1) with App Framework s1, integration, appframeworksS1, appframework: can deploy a Standalone and have ES app installed

A suite timeout occurred
Raw output
[TIMEDOUT] A suite timeout occurred
In [It] at: /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:753 @ 04/10/26 13:01:10.373

This is the Progress Report generated when the suite timeout occurred:
  s1appfw test Standalone deployment (S1) with App Framework s1, integration, appframeworksS1, appframework: can deploy a Standalone and have ES app installed (Spec Runtime: 3h43m11.181s)
    /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:753
    In [It] (Node Runtime: 3h43m9.933s)
      /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:753

    Spec Goroutine
    goroutine 251 [select]
      github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000474cb0, {0x297aa08, 0xc0003df410}, 0x1, {0x0, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:558
      github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000474cb0, {0x297aa08, 0xc0003df410}, {0x0, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/onsi/gomega@v1.39.1/internal/async_assertion.go:145
      github.com/splunk/splunk-operator/test/testenv.StandaloneReady({0x298be28, 0x3d40ce0}, 0xc000a65e00, {0xc0003df400?, 0x1?}, 0xc000259508, 0xc0004d6000)
        /home/runner/work/splunk-operator/splunk-operator/test/testenv/verificationutils.go:110
    > github.com/splunk/splunk-operator/test/appframework_aws/s1.init.func3.7.1()
        /home/runner/work/splunk-operator/splunk-operator/test/appframework_aws/s1/appframework_aws_test.go:805
          | 
          | // Ensure Standalone goes to Ready phase
          > testenv.StandaloneReady(ctx, deployment, deployment.GetName(), standalone, testcaseEnvInst)
          | 
          | // Get Pod age to check for pod resets later
      github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xc000386000?, 0xc000386120?})
        /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 57
        /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