Dashboard 5.4 or 5.4.0.1 and child 5.4
Attempting to updated child from 5.4 to 5.4.0.1 never completes and spikes CPU usage to 100 %
The issue appears to be related to the regression testing plugin. When I disable it I can run updates and CPU usage is normal.
1 Like
I have the same problem, and globally, since the last update mainwp crash almost every time
I’ve been seeing similar behaviour, where the update looks to not have completed in the dashboard but if I actually check the site the update has completed successfully, but I guess the regression testing add-on is not doing its thing and therefore holds up showing the update as complete.
On a side not, in the regression testing add-on page which lists all of the sites, by default it shows 10 sites and everything seems to work okay on those sites (e.g. I can kick off a scan or view the latest one) but if I go to page 2 none of the site options work. Even if I set it to show all sites, the options to scan/view results don’t work.
There appear to be a number of issues around this new add-on that don’t seem to be working properly.
1 Like
Instead of disabling the Regression Testing add-on, you can deactivate the post-update automatic scans in the add-on settings page so you can continue to scan your sites manually.:
I’ve managed to reproduce this issue and forwarded it to our dev team.
It will be fixed in an upcoming release.
I’ve done this but I was looking at the prospects of using this instead of the VRTs plugin (paid for service) which handles scheduled regression tests and regression tests when updates are made as this is an important point to check the site again to ensure the update hasn’t caused a problem. So, having to disable this means it can’t replace VRTs yet.
You don’t necessarily have to disable that option.
Instead you could reduce the Maximum simultaneous install and update requests in Advanced Settings.
This may reduce the load on the Dashboard site since it will run less updates and regression scans in parallel.
However, it will increase the time needed to perform them.
all is at minimum for me and it still make crashes the server each time
Thanks for the update.
Would you mind opening a private Help Desk ticket so we can collect some additional information & investigate further?
Please refer to this Community thread by its URL in the ticket.
Hi everyone,
Got the same issue after installing and activating Regression testing. It crashed our server a few minutes ago… Plugin is now deactivated and we are back to normal/ This plugin is using too much resources, we will keep our 3rd party testing tool for now (appscreen).
If anyone is experiencing high CPU usage or server crashes related to regression scans, please open a a private Help Desk ticket and we will gladly look into it further.