| Title | amcssth fails with "unable to obtain resources" |
| Status | closed |
| Priority | essential |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | Platform: lii6gc Variety: COOL Test case: amcssth Seed: 1676356240 Assertion: MPS_RESERVE_BLOCK: RESOURCE: "unable to obtain resources" This happens once in every 20-30 times the test case is run with this seed. I've also seen: Assertion: MPS_RESERVE_BLOCK: COMMIT_LIMIT: "arena commit limit exceeded" |
| Analysis | I suspect that both these failures are due to this line setting the commit limit: mps_arena_commit_limit_set(arena, 2 * testArenaSIZE) This test case says that it has been "tuned in the hope of getting one dynamic collection". But this is hopeless for the following reasons: (i) no guarantee of getting collection messages in a timely fashion; (ii) depends in a complicated way on the MPS's internals, such as overheads, allocation policy and so on. |
| How found | automated_test |
| Evidence | See description. |
| Test procedure | amcssth |
| Created by | Gareth Rees |
| Created on | 2014-03-18 16:01:19 |
| Last modified by | Gareth Rees |
| Last modified on | 2014-10-20 17:44:41 |
| History | 2014-03-18 GDR Created. 2014-04-08 GDR Closed as duplicate of job003561. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 185430 | closed | 2014-04-10 15:06:58 | Gareth Rees | Fix amcssth -- don't try to test two incompatible features at the same time (see job003561). Set the commit limit in amcss and amcsshe so that we test that the MPS can live in a tight memory limit. Don't try to detect when the MPS has made a "dynamic" collection. This is not reliable or maintainable. |