Temporarily disable broken secret scenario tests

[spadgett]

Disable secret scenario which is failing almost every run.

[spadgett]

/assign @jhadvig

We should debug the secret test. I was hoping #1385 would fix it, but no luck.

I'm upgrading Chrome to try and avoid the OperatorHub crash in #1383

[spadgett]

/retest

[jhadvig]

@spadgett yeah, will take a closer look on what could be the possible cause of the issue. Lets skip these test.
Also I see that the performance tests are failing pretty often.

[jhadvig]

HmmHmm so when I was checking the failed test in #1381 I can see:

Interacting with the create secret forms.Key/Value secrets check for edited Key/Value secret values 0.30s

Error: Failed expectation
    at Object.<anonymous> (/go/src/github.com/openshift/console/frontend/integration-tests/views/secrets.view.ts:67:29)
    at step (/go/src/github.com/openshift/console/frontend/integration-tests/views/secrets.view.ts:32:23)
    at Object.next (/go/src/github.com/openshift/console/frontend/integration-tests/views/secrets.view.ts:13:53)
    at fulfilled (/go/src/github.com/openshift/console/frontend/integration-tests/views/secrets.view.ts:4:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)

So not sure that disabling the Registry credentials image secrets test will help. Probably there is something either wrong with the test itself or the create-secret form.
Taking a closer look

[spadgett]

/hold

We've updated Chrome to the latest version in CI. Previously we were using an older beta version (at the time it was required for --headless). Let's see if it fixes OperatorHub tests.

[jhadvig]

ok... if anything we can disable all the secret tests temporarily, already looking into it.

[spadgett]

/hold cancel

[jhadvig]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, spadgett

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [jhadvig,spadgett]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[spadgett]

/hold

e2e-aws-console passed in #1383. Just want to double-check that this is still needed after that merges.

[openshift-ci-robot]

@spadgett: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-console-olm	da97d31	link	/test e2e-aws-console-olm

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[spadgett]

/skip

[spadgett]

/hold cancel

Secret tests are still failing (just not every run)