a phantomjs test fail suggests parsing from s3 might have a memory leak

Description

Don't have a lot of info on this yet, but was getting out of memory error during a s3 parse in phantomjs jenkins test

because it looked similar to the water meter problem with memory leak, prithvi thought there might be another memory leak here. Might be specific to s3 parse

here's the run.py that was running..it seemed to pass on master/ray branches, failed on cliffc branch. not sure why (mr-0xa1 jenkins)

../scripts/run.py --wipeall --test lib/h2o-flow/build/js/headless-test.js --baseport $BASE_PORT

so it used the default small heap (have to see what that was)

Assignee

New H2O Bugs

Reporter

Kevin Normoyle

Labels

None

CustomerVisible

No

testcase 1

None

testcase 2

None

testcase 3

None

h2ostream link

None

Affected Spark version

None

AffectedContact

None

AffectedCustomers

None

AffectedPilots

None

AffectedOpenSource

None

Support Assessment

None

Customer Request Type

None

Support ticket URL

None

End date

None

Baseline start date

None

Baseline end date

None

Task progress

None

Task mode

None

Priority

Major
Configure