Hi Jason. I just read TESTING.md, and while it gives at least an introduction into running the tests, it doesn't say anything I could see about adding new tests. Where can I find documentation for that?
Gabe On Mon, Jan 7, 2019 at 7:23 PM Gabe Black <gabebl...@google.com> wrote: > No problem, I understand how hard it can be to keep all the plates > spinning when things get really busy. I'll take a look at TESTING.md > (again? I think I may have read it once upon a time.) and let you know if I > get stuck. I was thinking of doing/helping do exactly what you're > describing, ie. get more tests like the systemc tests hooked up, porting > over old tests, and getting it all to run automatically. > > Gabe > > On Fri, Jan 4, 2019 at 8:57 AM Jason Lowe-Power <ja...@lowepower.com> > wrote: > >> Hey Gabe, >> >> Sorry for the slow response. I've been hoping to make more progress on >> the testing framework, but as always, it's been put on the back burner. >> >> The current state is that things should be all working. The best thing >> you could help with is adding new tests (e.g., for systemc) and porting old >> tests over to find the missing features, missing documentation, etc. I have >> some patches that are very close to being ready for memory tests (e.g., >> traffic gen) and CPU tests, but I'm working with some students to get them >> pushed and it's taking longer than I hoped. Hopefully, this will happen in >> the next couple of weeks. >> >> Related, I think the jenkins/kokoro integration is very close as well. I >> was working on it last month, and I remember everything mostly working. I >> think it just needed some more testing (preferably with more tests). I'll >> have some time the week of the 14th to look into this more. >> >> Let me know if you have any specific questions on how to add tests to the >> new testing framework. I tried to write good documentation in TESTING.md, >> but it may be missing things. I'll be more responsive next time :). >> >> Cheers, >> Jason >> >> >> >> On Thu, Jan 3, 2019 at 5:30 PM Gabe Black <gabebl...@google.com> wrote: >> >>> Hello...? >>> >>> On Tue, Dec 18, 2018 at 3:26 PM Gabe Black <gabebl...@google.com> wrote: >>> >>>> These changes have all been checked in. I still need some info about >>>> how to hook them systemc tests into Jason and co's framework. >>>> >>>> In general, how is getting that framework installed and ready to use >>>> coming along? Is there any blocking issue I can help with? >>>> >>>> Gabe >>>> >>>> On Wed, Dec 5, 2018 at 7:16 PM Gabe Black <gabebl...@google.com> wrote: >>>> >>>>> Hi folks, and specifically Jason. >>>>> >>>>> With these pending changes, the systemc tests (with the checked in >>>>> filter applied) should all pass, and should be well behaved and not leave >>>>> random files scattered around the source tree when run. Three of these >>>>> changes fix some small bugs I found while finishing this out, and two >>>>> update reference test output to match gem5's legal but slightly different >>>>> behavior compared to Accellera. >>>>> >>>>> https://gem5-review.googlesource.com/c/public/gem5/+/14915 >>>>> https://gem5-review.googlesource.com/c/public/gem5/+/14916 >>>>> https://gem5-review.googlesource.com/c/public/gem5/+/14917 >>>>> https://gem5-review.googlesource.com/c/public/gem5/+/14918 >>>>> https://gem5-review.googlesource.com/c/public/gem5/+/14919 >>>>> >>>>> The next step will be to integrate these tests into the overarching >>>>> test framework Jason and co. have been working on. I'm pretty sure there's >>>>> documentation out there which should tell me how to do this, but to save >>>>> me >>>>> some minor effort could someone point out what I should read to see how to >>>>> do this? Any other tips or suggestions to keep in mind? >>>>> >>>>> Gabe >>>>> >>>> _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
