Test project with no external dependencies, except for junit 3.8.2.

I've managed to create another test project, with no external dependencies but junit 3.8.2.

The problem is reproducible when exception thrown by JUnit (or any of the objects it references) implements custom serialization with writeObject/readObject methods. If there is such an object in the serialized objects graph, then Gradle test task hangs.

Another thing I've tested is use of readResolve() and writeReplace() methods.
Replacing class E from the test project with the following:

public class E extends Exception {
    
    private static final long serialVersionUID = 1000L;
    
    private static final E SINGLETON = new E("message of a singleton");

    public E(String m) {
        super(m);
    }
    
    protected Object writeReplace() throws ObjectStreamException {
        return SINGLETON;
    }

    protected Object readResolve() throws ObjectStreamException {
        return SINGLETON;
    }
}

does not have any effect. Test fails as expected (does not hang), but nowhere in the output there is a "singleton" message. This is fine, but looks strange, as I would expect SINGLETON exception instance to be used in report output, not the original one.

it seems we also run into this issue.....