Personally I've never really liked the directory structure under `tests`. Scripts are often far from the tests that run them. There's also `tests/configs` and `tests/gem5/configs` which could almost certainly be merged. Almost all tests are stored under `tests/gem5` for no other reason than this is where we've put them. At the very least it's not a very descriptive name for the directory. While your solution would be beneficial, I also think we (well, probably just me unless anyone wants to volunteer) should think about how to clean-up this directory in general.
-- Dr. Bobby R. Bruce Room 3050, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Sep 22, 2021 at 10:32 PM Gabe Black via gem5-dev <gem5-dev@gem5.org> wrote: > Hey folks, just FYI, when running tests from the tests directory (as the > instructions say to do), if a script imports a gem5 module, there is some > ambiguity whether that should be the built in gem5 module added for the > components stuff, or if it should be the gem5 directory in the tests > directory used by the test infrastructure. > > I think as is today we get away with that for some timing reason I haven't > fully nailed down, and I'm attempting to reorder things in my SCons > refactor so that the internal version takes precedence over anything in the > file system. I'm hopeful this will fix things, but it's still running. > > This isn't necessarily a call to arms or anything, but this seems like a > situation likely enough to cause errors that I wanted to point it out. > > Gabe > _______________________________________________ > gem5-dev mailing list -- gem5-dev@gem5.org > To unsubscribe send an email to gem5-dev-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
