I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException.
In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures.
In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts.
I would suggest to ignore AssertionErrors from server activities if there is a catched client exception.