On Thu, 21 Feb 2013, Mike Stump wrote: > > BTW, do you happen to know a way to reliable force all our testsuites NOT > > to delete executables after run? Personally I think it's missing the > > point to have them deleted -- how can one debug any regressions then? > > So, I go into the source and comment out the cleanup lines… Would be > nice to have them conditional on a variable so that one can set that > variable in their .dejagnurc file.
Hmm, good idea, I'll see if the hack I use could be adapted easily. > The limitations of this are, multiple test cases can use the same > intermediate files and they would not give you a nice 1 to 1 mapping > back. However, this I usually side step by only running a subset of the > test suite that contains the part I'm interested in. Yeah, I think final executables that don't have unique names are even worse. It would be good to avoid at least making such new cases. > > What do other people do? > > We usually can cut and paste the one line and run the one case by hand. > Test cases that don't fall into this category, well, suck, I mean, are > more annoying. For this to work you need to have at least all the auxiliary stuff needed for linking, etc. that's built once per test suite run still available. Somehow I found it troublesome to rebuild it manually. Thanks for all the hints -- it looks to me like there's no easy answer. In which case I'll see if I can do anything about the hack I have in case someone else finds it useful. Maciej
