Kinsey Moore created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5417
## Summary An issue has arisen recently with the addition of the psximfs03 test where a very large amount of memory is assumed to be present on the target system. This goes beyond the use-case of tstsmallmem.yml where tests are excluded from being built on targets that have very small amounts of memory available. In fact, only a handful of targets have the 1GB of RAM required to link psximfs03. The quick and dirty solution that mirrors our existing work is to create another level of test exclusions for systems that are not in the "very large" category with regards to RAM availability. I would argue against this since it is yet another level of vague matching based on notional categories of systems and it becomes harder to maintain than it already is. A better solution would be for the build system to know approximately how much RAM a test needs (either through build-time inspection or the writer of the test pre-setting the expected amount) and refuse to build that test (or silently abort the build when a mismatch is detected) for BSP configurations that have too little configured RAM. ## Steps to reproduce <!-- Pre-set options - milestone --> -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5417 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
