goharbor / harbor

An open source trusted cloud native registry project that stores, signs, and scans content.

Home Page:https://goharbor.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

the UI_UT of CI failed

zyyw opened this issue · comments

During the process of releasing v2.11.0-rc1, the CI job failed as show below:
Screenshot 2024-05-17 at 2 00 11 PM

which is this one:

the error log display something like below:

05:02:05 An error was thrown in afterAll
05:02:05 Error: Expected null not to be null.
05:02:05 at <Jasmine>
05:02:05 at apply (http://localhost:9876/_karma_webpack_/webpack:/src/appproject/repository/artifact/sbom-scanning/sbom-scan.component.spec.ts:181:28)
05:02:05 at _ZoneDelegate.invoke (http://localhost:9876/_karma_webpack_/webpack:/node_modules/zone.js/fesm2015/zone.js:368:26)
05:02:05 at ProxyZoneSpec.onInvoke (http://localhost:9876/_karma_webpack_/webpack:/node_modules/zone.js/fesm2015/zone-testing.js:273:39)
05:02:05 Chrome Headless 125.0.6422.60 (Linux x86_64): Executed 419 of 460 ERROR (0 secs / 12.691 secs)
05:02:05 Chrome Headless 125.0.6422.60 (Linux x86_64) ERROR
05:02:05 An error was thrown in afterAll
05:02:05 Error: Expected null not to be null.

the log also displays something like this:

05:00:13 > harbor@2.10.0 lint
05:00:13 > ng lint
05:00:13
05:00:13
05:00:13 Linting "harbor-portal"...
05:00:35
05:00:35 All files pass linting.
05:00:35
05:00:35 + npm run lint:style
05:00:35
05:00:35 > harbor@2.10.0 lint:style
05:00:35 > npx stylelint "**/*.scss"

Is the harbor@2.10.0 correct?