On 5/18/20 2:16 PM, Jacob Bachmeyer wrote:
> My work on DejaGnu is one of my hobbies. However, DejaGnu is a
> relatively stable project, so I do not expect it to require much time.
To adequately test DejaGnu, you need to be able to build and test the
GNU toolchain, both native and cross. That's necessary to test patches,
or reproduce bugs. Once all that is setup, then yes testing patches
isn't too time consuming. Building several toolchains and setting up
cross testing is what sucks up most of the time. You don't need to be a
toolchain developer, but you do need to be able to work in that environment.
Luckily you can use my ABE tool (also GPLv3), which I built for
Linaro, and it fully automates the process of building and testing
native or cross toolchains. I agree you've been deeper into the DejaGnu
code than anybody else these days, but unless you run the toolchain
testsuites in a cross build from git, you can never really be sure if
something doesn't break in obscure ways. Maybe others disagree with me
on this, but testing the toolchain is the primary purpose of DejaGnu.
I'm open to an additional co-maintainer if you can survive getting
fully setup. ABE makes it easy, you just need a ton of disk space. While
it is possible to add bug fixes or features without much toolchain
testing, it's impossible to do a stable release without it. With
DejaGnu, all releases are long-term support... and we will need to do a
release after the patch backlog is caught up.
- rob -
---
https://www.senecass.com
