Re: dejagnu version update?

On 5/13/20 10:51 AM, Mike Stump wrote: > So, now that ubuntu 20.04 is out and RHEL 8 is out, and they both > contain 6, and SLES has 6 and since we've been sitting at 1.4.4 for > so long, anyone want to not update dejagnu to require 1.6? We do still find and fix bugs occasionally. :-) And 1.4.4

Re: dejagnu version update?

On 5/14/20 8:08 AM, Rainer Orth wrote: >> stops responding for whatever reason. I have come up with a solution >> (that I'd be happy to upstream, except that DejaGNU maintenance seems to >> have been dead for like a year now), which I have also confirmed to be >> required with current DejaGNU

Re: dejagnu version update?

On 5/14/20 10:08 AM, David Edelsohn wrote: > Have you approached the Linux Foundation Core Infrastructure > Initiative for funding for both DejaGNU maintenance (patch backlog) > and refactoring DejaGNU in Python efforts? Not that team, the folks I talked to thought I was crazy for wanting to re

Re: dejagnu version update?

On 5/14/20 5:34 PM, Maciej W. Rozycki wrote: > And then current development appears ongoing, ferociously indeed, with the > last check in literally today (barring my time zone), as indicated here: > . It's obvious I haven't been paying attention, so muc

Re: dejagnu version update?

On 5/15/20 6:22 PM, Mike Stump wrote: > Anyway, love to have software that can move code wholesale. Love to move the > testsuite into a new language. All it needs is funding. :-) What GDB needs is expect, not Tcl. Most of the GDB testsuite is just expect pattern matching from the shell. That'

Re: dejagnu version update?

On 5/16/20 5:45 PM, Maciej W. Rozycki wrote: > Overall perhaps a patch management system might be good having to make > chasing patches easier, such as patchwork, and we already use Git, so we As an old GNU project, we're required to use what the FSF prefers, which is on savannah. https://sav

Re: dejagnu version update?

On 5/17/20 1:43 PM, Maciej W. Rozycki wrote: > patch service before. It doesn't appear linked to our mailing list either > and instead you need to go through the hoops of a web interface (and open > an account first) to submit a change. From what I remember, it was decided the GNU toolchain

Re: dejagnu version update?

I processed the patch backlog for DejaGnu, and have gone through the bug list. It'd be nice if somebody could try master with a more complex environment, etc... if I'm going to push out a release. For cross testing all I have is a PI and QEMU. - rob -

Re: dejagnu version update?

On 5/26/20 7:20 PM, Maciej W. Rozycki wrote: > I'll run some RISC-V remote GCC/GDB testing and compare results for > DejaGnu 1.6/1.6.1 vs trunk. It will take several days though, as it takes > many hours to go through these testsuite runs. That'd be great. I'd rather push out a stable relea

Re: connecting a QEMU VM to dejagnu...

On 10/16/19 5:40 PM, Alan Lehotsky via DejaGnu wrote: > The one example I found via a web search seems to want to do > everything in the virtual machine - but I have to believe that’s > going to be insanely slow… Well, qemu is a virtual machine... Here's the ones I used for GNU toolchain cross

Re: DejaGnu and toolchain testing

On 07/25/2013 06:21 PM, Joseph S. Myers wrote: > I was interested to watch the video of the DejaGnu BOF at the Cauldron. A > few issues with DejaGnu for toolchain testing that I've noted but I don't > think were covered there include: Thanks for the thoughtful comments, they're useful as I sta

Re: DejaGnu and toolchain testing

On 07/26/2013 10:37 AM, Joseph S. Myers wrote: > Anything in the core needs to avoid obstructing toolchain changes. People > typically test with the installed DejaGnu from their OS, and the OS itself > may well be a few years old (e.g. Ubuntu 10.04), so it's undesirable for > an enhancement to