coveralls commented on issue #405:
URL: https://github.com/apache/struts/pull/405#issuecomment-617625161
[](https://coveralls.io/builds/30251043)
Coverage increased (+0.02%) to 47.086% when pulling
**c2765e5236dd99765
The build for struts-core/master completed successfully and is back to normal.
Build: https://builds.apache.org/job/struts-core/job/master/245/
Logs: https://builds.apache.org/job/struts-core/job/master/245/console
Changes: https://builds.apache.org/job/struts-core/job/master/245/changes
--
Mr. J
atkaiser commented on issue #405:
URL: https://github.com/apache/struts/pull/405#issuecomment-618022537
LGTM 👍
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
coveralls edited a comment on issue #405:
URL: https://github.com/apache/struts/pull/405#issuecomment-617625161
[](https://coveralls.io/builds/30277905)
Coverage increased (+0.02%) to 47.086% when pulling
**30b43044a3
Hi,
I found this old task [1] and it looks interesting to me, we can use
benchmarking to test if we did improve performance or not. I'm working
on an example application now and how to test it, just wonder if we
should add to this to a repo - create a new struts-benchmarking repo?
[1] https://iss
Here are some comparisons, does anybody now how to read this?
Struts 2.5.22
Starting standalone test @ Thu Apr 23 08:36:14 CEST 2020 (1587623774966)
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message
on port 4445
summary + 2695 in 00:00:15 = 181.9/s Avg: 537 Min:99 Max
