Actions
Bug #52682
openmgr/dashboard: mgr-dashboard-frontend-unittests fails in RbdTrashMoveModalComponent
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Description of problem¶
# ctest -R mgr-dashboard-frontend-unittests --output-on-failure
Test project /working/ceph/build
Start 162: mgr-dashboard-frontend-unittests
1/1 Test #162: mgr-dashboard-frontend-unittests ...***Failed 383.70 sec
...
> ceph-dashboard@0.0.0 test:ci /working/ceph/src/pybind/mgr/dashboard/frontend
> jest --clearCache && JEST_SILENT_REPORTER_DOTS=true jest --coverage --reporters jest-silent-reporter
Cleared /tmp/jest_0
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
.Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
....................................................................................................
● RbdTrashMoveModalComponent › should call moveImage › with delay < 0
expect(received).toBeGreaterThan(expected)
Expected: > 76390
Received: 50399.618
89 | const req = httpTesting.expectOne('api/block/image/foo%2Fbar/move_trash');
90 | req.flush(null);
> 91 | expect(req.request.body.delay).toBeGreaterThan(76390);
| ^
92 | });
93 | });
94 | });
at src/app/ceph/block/rbd-trash-move-modal/rbd-trash-move-modal.component.spec.ts:91:38
at ZoneDelegate.Object.<anonymous>.ZoneDelegate.invoke (node_modules/zone.js/dist/zone.js:386:30)
at ProxyZoneSpec.Object.<anonymous>.ProxyZoneSpec.onInvoke (node_modules/zone.js/dist/proxy.js:117:43)
at ZoneDelegate.Object.<anonymous>.ZoneDelegate.invoke (node_modules/zone.js/dist/zone.js:385:36)
at Zone.Object.<anonymous>.Zone.run (node_modules/zone.js/dist/zone.js:143:47)
.....................................................................................................................................................................................
npm ERR! code ELIFECYCLE
npm ERR! errno 1
...
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 383.73 sec
The following tests FAILED:
162 - mgr-dashboard-frontend-unittests (Failed)
Errors while running CTest
Environment¶
ceph versionstring: ecd57a59dfcbe256c1eb5291f5702c446c20b3b9- Platform (OS/distro/release): VERSION="20.04.3 LTS (Focal Fossa)" container
- Cluster details (nodes, monitors, OSDs): n/a
- Did it happen on a stable environment or after a migration/upgrade?: n/a
- Browser used (e.g.:
Version 86.0.4240.198 (Official Build) (64-bit)): n/a
How reproducible¶
Steps:
Start container.
- apt-get update
- cd /ceph
- ./install-deps.sh
- ./do_cmake.sh
- ninja -j8 all tests
- ctest -R mgr-dashboard-frontend-unittests --output-on-failure
Updated by Ernesto Puerta over 2 years ago
- Status changed from New to Triaged
- Assignee set to Alfonso Martínez
- Source set to Development
Updated by Brad Hubbard over 2 years ago
Saw this again on commit 5dda7997733e0ccc66d1437ac9b5754be667c2fd (HEAD -> wip-yuriw-master-11.19.21, ceph-ci/wip-yuriw-master-11.19.21)
Same process to reproduce.
$ podman pull ubuntu:focal $ podman run -it --rm --privileged -v./src/ceph:/working:z ubuntu:focal # cd /working # ./install-deps.sh # ./do_cmake.sh # ninja -j8 all tests # ctest -R mgr-dashboard-frontend-unittests --output-on-failure
Updated by Ernesto Puerta over 2 years ago
This might be a timezone conversion issue (the received value is 14 hours while the original should be closer to 24 or 22 hours).
Updated by Brad Hubbard over 2 years ago
Interesting. When running install-deps.sh on Ubuntu containers you are prompted to select a timezone when it installs the tzdata package (we should make it so it doesn't prompt, but that's another story and not high on my priority list) and I usually select my location (Brisbane, Australia).
Actions