You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Steve Lawrence (Jira)" <ji...@apache.org> on 2024/06/03 14:14:00 UTC

[jira] [Assigned] (DAFFODIL-2901) Unable to run many tests in single tdml suite without large amounts of memory

     [ https://issues.apache.org/jira/browse/DAFFODIL-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence reassigned DAFFODIL-2901:
----------------------------------------

    Assignee: Steve Lawrence

> Unable to run many tests in single tdml suite without large amounts of memory
> -----------------------------------------------------------------------------
>
>                 Key: DAFFODIL-2901
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2901
>             Project: Daffodil
>          Issue Type: Bug
>          Components: TDML Runner
>    Affects Versions: 3.7.0
>            Reporter: Olabusayo Kilo
>            Assignee: Steve Lawrence
>            Priority: Major
>
> The test suite I'm working with contains 600+ tests, and run just fine in IntelliJ (which has a heap size of 4G), but fails to run with `sbt test` failing with an out of memory error. This error doesn't go away until we increase the sbt heap size to 8G. Then the tests run successfully.
> Obvious workaround is just to do `sbt -mem 8192 test`, but it would be ideal if this wasn't necessary, especially since the tests are run sequentially and not in parallel. A memory leak in the runner seems like a likely suspect.
> We would obviously need to profile an `sbt test` run using either JProfiler or Intellij's built in profiler. Example schemas with lots of tests are the JREAP schema and the P8 schema. 
> According to [~jadams_tresys] , this issue doesn't occur if the tests are split out into multiple test suites



--
This message was sent by Atlassian Jira
(v8.20.10#820010)