[Webkit-unassigned] [Bug 174502] [GTK][WPE] stress/dont-reserve-huge-capacity-lexer.js JSC test failing

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=174502

--- Comment #4 from Zan Dobersek <zan at falconsigh.net> ---
(In reply to Carlos Alberto Lopez Perez from comment #3)
> (In reply to Yusuke Suzuki from comment #2)
> > (In reply to Zan Dobersek from comment #1)
> > > One option is to run the tests on the GTK+ and WPE bots with
> > > --memory-limited by default.
> > 
> > Until we implement the functionality to execute some tests in a non-parallel
> > manner, passing --memory-limited in GTK/WPE bot is good workaround.
> 
> I prefer to skip the specific tests that use insane amounts of RAM ( see bug
> 171630 ) on WPE and GTK than just skip all tests that can use more RAM than
> the available on an embedded system (I understand that this is what memory
> limited means, correct me if I'm wrong).
> 

The test in 171630 is a layout test and is easily skippable. This is a file under JSTests/ and can't be as easily skipped.

In total there are 11 tests that are skipped on x86_64 in case the script is passed --memory-limited, so there's not a lot of test coverage that's lost if --memory-limited is used by default on the bots.

> Typical GTK/WPE bots have at least 16GB of RAM available and run 8 tests in
> parallel. If a test uses [2-4]GB of RAM is fine. If it uses more can be a
> problem.

Well obviously 16GB is not enough when a bunch of dont-reserve-huge-capacity-lexer.js variations are run together, so as it stands this might as well be considered a memory-limited configuration.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170728/d1e4a4d6/attachment-0001.html>