[UI] Update the Kubeflow Commit for Katib UI

[andreyvelich]

I updated commit that might help to fix Katib UI CI/CD.

/assign @kubeflow/wg-automl-leads @kimwnasptd @elenzio9 @apo-ger

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreyvelich

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

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/ui/v1beta1/OWNERS [andreyvelich]

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

[tenzen-y]

Also, we need to change there: https://github.com/tenzen-y/katib/blob/714929384bfb6a3a2c3d5b9769f3b1bb6e8ba9bf/pkg/ui/v1beta1/frontend/src/styles.scss#L2

[andreyvelich]

@kimwnasptd @kubeflow/wg-notebooks-leads I might need your help to debug CI/CD for Katib UI since it is related to CRUD WebApps

[andreyvelich]

@orfeas-k @kimwnasptd Any thoughts on this error ? If we can't debug it before the release, we can temporarily disable unit tests for Katib UI

  1) Index page
       renders properly Status icon for all  experiments:
     AssertionError: Timed out retrying after 4000ms: Expected to find element: `lib-status>mat-icon`, but never found it. Queried from element: <td.mat-cell.cdk-cell.cdk-column-status.mat-column-status.ng-star-inserted>
      at Context.eval (webpack:///./cypress/e2e/index-page.cy.ts:56:11)

[orfeas-k]

Could you try the following change from here? This should do the fix if the previous Kubeflow commit was a very old one.

[andreyvelich]

Could you try the following change from here? This should do the fix if the previous Kubeflow commit was a very old one.

@orfeas-k I still can see the following error:

There was an error reconnecting to the Chrome DevTools protocol. Please restart the browser.

Error: connect ECONNREFUSED 127.0.0.1:40069
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! frontend@0.0.0 ui-test-ci-all: `cypress run . --e2e --browser=chrome && cypress run . --e2e --browser=firefox`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the frontend@0.0.0 ui-test-ci-all script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2024-04-24T15_23_36_465Z-debug.log
Error: Process completed with exit code 1.

Do we need to make any other changes ?

[orfeas-k]

@andreyvelich Unfortunately, it's the first time I see this error. Cypress has the following issue cypress-io/cypress#26900 for which they released a fix in 12.17. However, I 'm afraid that just bumping cypress two major versions will need some work.

[andreyvelich]

@andreyvelich Unfortunately, it's the first time I see this error. Cypress has the following issue cypress-io/cypress#26900 for which they released a fix in 12.17. However, I 'm afraid that just bumping cypress two major versions will need some work.

Does Cypress have some breaking changes that we need to make if we update the version ?

[orfeas-k]

@andreyvelich I haven't done that migration in the past myself but reading the docs, there are quite a few breaking changes going from 10->11 and 11->12, so I expect we 'd hit at least some of them.

[andreyvelich]

@orfeas-k @kubeflow/wg-notebooks-leads Any updates here ?
Did you migrate to the new version of Cypress for Central Dashboard or Notebooks UI tests ?