Ability to do introspection on failures seems to have vanished

[MylesBorins]

in the past we would get an aggregate list of failures in CI... this no longer seems available, and I have to do a bunch of spelunking. Anyone else seeing this, or am I missing an obvious button?

[gibfahn]

Are you talking about the Aggregated Test Result? If so then yeah, those results disappear if one of the options is disabled on one of the subjobs.

Output is:

Fingerprinting not enabled on this build. Test aggregation requires fingerprinting.

[gibfahn]

I'd suggest we need to be enabling fingerprinting like so:

[gibfahn]

On a related note, is there a reason we're using the Jenkins Text Finder plugin? The TAP plugin parses the results and marks the build as UNSTABLE if tests fail anyway.

[rvagg]

no objection from me if you want to give that a go @gibfahn, are you in jenkins-admins? re Jenkins Text Finder, I don't know who or why it's in there unfortunately.

[gibfahn]

are you in jenkins-admins

Yes. I'll have a look.

[mhdawson]

The aggregate list sounds really useful :) I'll look forward to trying it out.

[gibfahn]

I'll test it out in readable-stream-continuous-integration #782 first.

[MylesBorins]

any traction on this? Having to dig into raw tap is a pretty bad ux

[gibfahn]

Enabling fingerprinting doesn't seem to actually work, at least not reliably. This irritates a lot of people, it's just waiting for someone to work out what the magic Jenkins formula is.

Alternatively we could just use tap2junit

[MylesBorins]

Do we have any insight into improving this? I noticed it was randomly working on a machine today