On Dec 11, 2014, at 5:07 AM, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: > David Malcolm <dmalc...@redhat.com> writes: >>> * I don't consider this a critical issue that cannot work without >>> current releases. We're already working around several upstream >>> DejaGnu issues in our codebase, and I don't consider this particular >>> one important enough to require everyone to upgrade to a not-a-release >>> version. > > ... a DejaGnu 1.6 release would only address one part of my concern: I > still don't believe this minor issues warrants us demanding all gcc > testers upgrading to a newer DejaGnu release. I'd like my fellow > testsuite maintainers to weigh in, though.
I’m fine with how this is being done. If the jit people want to fixincludes it, fine. If they submit fixes to dejagnu and want to recommend a newer dejgnu for jit testing, that’s fine. A tester should be free to use the current dejagnu they use and it should result in no regressions in the test suite for the non-jit parts. They should also be free to update to the latest dejagnu and use it and see non-regressions across the non-jit suite. If the jit people want to simplify their lives and do a return if the dejagnu version is too old from their top-level, essentially enforcing a tester to use a newer dejegnu if they want to see jit test suite results, even that is fine with me. We can even update the recommended version of dejagnu while still keeping the current recommended version as working, I’m not opposed to that.
