Project

General

Profile

Bug #24939

mgr/dashboard: Frontend unit tests fail

Added by Volker Theile 5 months ago. Updated 2 months ago.

Status:
Can't reproduce
Priority:
Normal
Assignee:
Category:
dashboard/general
Target version:
Start date:
07/16/2018
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

When running 'npm run test' in the src/pybind/mgr/dashboard/frontend directory it fails with the error below. It seems that jest/git uses some repository (e.g. a GIT repo located at /home/vot/git/openmediavault-docs), but not the correct one, to detect the latest changed files. I assume jest --watch is not configured correct in this case.

Determining test suites to run...
<--- Last few GCs --->

[20677:0x25ba870] 19456 ms: Scavenge 1396.1 (1420.8) -> 1396.0 (1421.8) MB, 2.6 / 0.0 ms (average mu = 0.118, current mu = 0.020) allocation failure
[20677:0x25ba870] 20053 ms: Mark-sweep 1396.5 (1421.8) -> 1396.3 (1421.3) MB, 596.2 / 0.1 ms (average mu = 0.066, current mu = 0.008) allocation failure scavenge might not succeed
[20677:0x25ba870] 20058 ms: Scavenge 1396.9 (1421.3) -> 1396.7 (1422.3) MB, 2.8 / 0.0 ms (average mu = 0.066, current mu = 0.008) allocation failure

<--- JS stacktrace --->

==== JS stack trace =========================================

0: ExitFrame [pc: 0x201f063041bd]
1: StubFrame [pc: 0x201f06312c4a]
Security context: 0x149218e9e589 &lt;JSObject&gt;
2: normalizeString(aka normalizeString) [0x1b1cff817dd9] [path.js:~57] [pc=0x201f06586ced](this=0x15186c7022e1 &lt;undefined&gt;,path=0x3a06f4a5e529 &lt;String[100]: /home/vot/git/openmediavault-docs/venv/lib/python3.6/site-packages/pytz/zoneinfo/Australia/Adelaide/&gt;,allowAboveRoot=0x15186c7023f1 &lt;false&gt;,separator=0x124a521ca...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: node::Abort() [node]
2: 0x89375c [node]
3: v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
4: v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
5: 0xe616b2 [node]
6: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
7: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
8: v8::internal::Heap::AllocateRawWithRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [node]
9: v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [node]
10: v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [node]
11: 0x201f063041bd
Aborted (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! test: `jest --watch`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the test 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:

History

#1 Updated by Lenz Grimmer 4 months ago

Is this still an issue or has this been resolved in the meanwhile?

#2 Updated by Tiago Melo 2 months ago

  • Status changed from New to Can't reproduce

Also available in: Atom PDF