Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test broken on report/test-report-fatal-error #153

Closed
gengjiawen opened this issue Apr 7, 2020 · 3 comments
Closed

test broken on report/test-report-fatal-error #153

gengjiawen opened this issue Apr 7, 2020 · 3 comments

Comments

@gengjiawen
Copy link
Member

gengjiawen commented Apr 7, 2020

From latest github CI pipeline.

2020-04-05T07:50:54.2822967Z not ok 2611 report/test-report-fatal-error
2020-04-05T07:50:54.2823937Z   ---
2020-04-05T07:50:54.2824333Z   duration_ms: 3.131
2020-04-05T07:50:54.2824673Z   severity: fail
2020-04-05T07:50:54.2825274Z   exitcode: 1
2020-04-05T07:50:54.2825918Z   stack: |-
2020-04-05T07:50:54.2826312Z     undefined:1
2020-04-05T07:50:54.2826853Z     <--- Last few GCs --->
2020-04-05T07:50:54.2827244Z     ^
2020-04-05T07:50:54.2827544Z     
2020-04-05T07:50:54.2827871Z     SyntaxError: Unexpected token < in JSON at position 0
2020-04-05T07:50:54.2828198Z         at JSON.parse (<anonymous>)
2020-04-05T07:50:54.2830295Z         at Object.<anonymous> (/home/runner/work/node-v8/node-v8/test/report/test-report-fatal-error.js:118:21)
2020-04-05T07:50:54.2830791Z         at Module._compile (internal/modules/cjs/loader.js:1178:30)
2020-04-05T07:50:54.2831173Z         at Object.Module._extensions..js (internal/modules/cjs/loader.js:1198:10)
2020-04-05T07:50:54.2831515Z         at Module.load (internal/modules/cjs/loader.js:1027:32)
2020-04-05T07:50:54.2831834Z         at Function.Module._load (internal/modules/cjs/loader.js:923:14)
2020-04-05T07:50:54.2832175Z         at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
2020-04-05T07:50:54.2832514Z         at internal/main/run_main_module.js:17:47
@mmarchini
Copy link

Looks like a formatting change on the error.

@gengjiawen
Copy link
Member Author

gengjiawen commented Apr 7, 2020

Looks like there gc log mixed in.

<--- Last few GCs --->

[74857:0x108000000]      283 ms: Mark-sweep 22.7 (55.9) -> 22.6 (55.9) MB, 16.9 / 0.0 ms  (average mu = 0.040, current mu = 0.001) allocation failure scavenge might not succeed
[74857:0x108000000]      301 ms: Mark-sweep (reduce) 22.6 (55.9) -> 22.6 (24.9) MB, 17.9 / 0.0 ms  (average mu = 0.025, current mu = 0.002) last resort GC in old space requested


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

{"header":{"reportVersion":2,"event":"Allocation failed - JavaScript heap out of memory","trigger":"FatalError ...

@gengjiawen
Copy link
Member Author

Looks like this is a way to fix:

  const report = lines.find(i => i.startsWith("{"));

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants