Feature - Rejected Less verbose output for failing tests on GitHub

[fronobulax]

See https://github.com/kolmafia/kolmafia/actions/runs/13764021050/job/38486242663?pr=2813

The stack traces that begin with "org.gradle.internal" tell me nothing about the test failure. The sheer number of them make it hard to figure out what the actual problem was.

My recollection is that it wasn't always this way. Logging was added because information related to the failure was not being displayed. But I think some test infrastructure was changed to make that less likely.

Any chance we can go back to the way it was? Or am I the only person who deals with test failures on GitHub?

@Ryo_Sangnoir ?

Thanks.

 

[Ryo_Sangnoir]

I added it because without it, you can't tell what the failure actually is. I deal with test failures on GitHub, and it is useful. If we don't have this, we don't actually have any information beyond "test X failed" -- we don't have the failure message nor the stack trace for the line.

It was changed in https://github.com/kolmafia/kolmafia/pull/2536.

You need to ignore the stack traces at the bottom and scroll up until you reach the actual tests.

 

[fronobulax]

I added it because without it, you can't tell what the failure actually is. I deal with test failures on GitHub, and it is useful. If we don't have this, we don't actually have any information beyond "test X failed" -- we don't have the failure message nor the stack trace for the line.

It was changed in https://github.com/kolmafia/kolmafia/pull/2536.

You need to ignore the stack traces at the bottom and scroll up until you reach the actual tests.

View attachment 11360

Are you telling me that once I hit the org.gradle.internal section I can safely ignore what follows and stop scrolling? I confess I had not figured that out but if true, it addresses my problems. Thanks.