Closed RRMoelker closed 8 years ago
do you still have the database file (visualreview.db.mv.db
) that triggered the error? I could use that to find the problem.
Alas, no. I removed the last runs through the UI forgetting to make a DB backup first.
I suggest closing the issue for now as it probably is very hard to reproduce. When it reoccurs I'll extract the db.
I'm guessing one the last runs triggered something weird in the internal storage, causing the 404's. If you encounter this error again, you could re-open this issue.
After many runs ( > 3500 runs) the status resource suddenly returned a 404. Deleting the last few runs in that suite fixed the problem. I could not find a VR log with any errors. But it is quite clear that the end point is not working as expected.
I'm not expecting the issue to be fixed given the limited bug report. But it is a indication that more logging is desired.