René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Operator E2E test sporadically failing due to the timing issue","articleBody":"Operator E2E test sporadically failing due to the timing issue based on the availability of the pods status. We have to expect reliable execution on every PR to avoid the inconsistency. \n\nFor Example:\n\nhttps://github.com/feast-dev/feast/actions/runs/12896520988/job/35959688148?pr=4930\n\nHere is the error we are seeing.\n\n\n```\nSTEP: deploying the Simple Feast Custom Resource to Kubernetes @ 01/21/25 21:59:21.019\n  running: kubectl apply -f test/testdata/feast_integration_test_crs/v1alpha1_default_featurestore.yaml -n default\n  [FAILED] in [It] - /home/runner/work/feast/feast/infra/feast-operator/test/e2e/e2e_test.go:161 @ 01/21/25 21:59:21.129\n  STEP: Uninstalling the feast CRD @ 01/21/25 21:59:21.129\n  running: kubectl delete deployment feast-operator-controller-manager -n feast-operator-system\n• [FAILED] [466.659 seconds]\ncontroller Operator E2E Tests [It] Should be able to deploy and run a default feature store CR successfully\n/home/runner/work/feast/feast/infra/feast-operator/test/e2e/e2e_test.go:100\n\n  [FAILED] Error occurred while checking FeatureStore simple-feast-setup is having remote registry or not. \n  Error: kubectl get featurestore command returned empty output\n\n  Unexpected error:\n      \u003c*errors.errorString | 0xc0002a65b0\u003e: \n      kubectl get featurestore command returned empty output\n      {\n          s: \"kubectl get featurestore command returned empty output\",\n      }\n  occurred\n  In [It] at: /home/runner/work/feast/feast/infra/feast-operator/test/e2e/e2e_test.go:161 @ 01/21/25 21:59:21.129\n------------------------------\nS [SKIPPED] [0.000 seconds]\ncontroller Operator E2E Tests [It] Should be able to deploy and run a feature store with remote registry CR successfully\n/home/runner/work/feast/feast/infra/feast-operator/test/e2e/e2e_test.go:118\n\n  [SKIPPED] Spec skipped because an earlier spec in an ordered container failed\n  In [It] at: /home/runner/work/feast/feast/infra/feast-operator/test/e2e/e2e_test.go:118 @ 01/21/25 21:59:21.18\n------------------------------\n\nSummarizing 1 Failure:\n  [FAIL] controller Operator E2E Tests [It] Should be able to deploy and run a default feature store CR successfully\n  /home/runner/work/feast/feast/infra/feast-operator/test/e2e/e2e_test.go:161\n\nRan 1 of 2 Specs in [46](https://github.com/feast-dev/feast/actions/runs/12896520988/job/35959688148?pr=4930#step:7:47)6.659 seconds\nFAIL! -- 0 Passed | 1 Failed | 0 Pending | 1 Skipped\n--- FAIL: TestE2E (466.66s)\nFAIL\nFAIL\tgithub.com/feast-dev/feast/infra/feast-operator/test/e2e\t466.665s\nFAIL\nmake: *** [Makefile:121: test-e2e] Error 1\nError: Process completed with exit code 2.\n```","author":{"url":"https://github.com/lokeshrangineni","@type":"Person","name":"lokeshrangineni"},"datePublished":"2025-01-22T04:17:32.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/4953/feast/issues/4953"}