k8s bot did not open test for flaking test

[saad-ali]

The test [k8s.io] [Feature:Example] [k8s.io] Spark should start spark master, driver and workers has been consistently failing in the kubernetes-e2e-gce-examples test suite for a long time. However I don't see any issue opened for it.

Why did the k8s-merge-robot not open an issue for it. I see other tests in that suite have triggered automated issue creation in the past: e.g. kubernetes/kubernetes#33106

I manually opened up an issue in the meantime: kubernetes/kubernetes#36102

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close