On 10/31/18 9:15 PM, Jacob Bachmeyer wrote:
> The best answer would probably be to add support for DejaGnu's own XML
> format (which seems to have a far more sensible data model) to Jenkins,
> but that is outside the scope of the DejaGnu project and I am not
> currently using Jenkins, so I will leave that to someone else.
This is why this script is in 'contrib', and not core DejaGnu. :-) I
thought others might use this as a basis for this integration and
enhance it. I found the Junit test results in Jenkins far from
sufficient for GCC testing, so later wrote scripts for comparing diffs
instead that worked much better. I also wrote the XML support in
DejaGnu, and agree it would be better than Junit, but I don't feel like
learning to write a Java plugin for Jenkins. I'm also not currently
working on CI for the toolchain anymore. Personally, I'd just ignore
this script, but thanks for digging into it for possible issues.
- rob -
_______________________________________________
Bug-dejagnu mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-dejagnu
