Track frame export status and error out if QFile::copy() fails for any frames

Raidon Chromerequested to merge
raidon/krita:frame_export_status into master

KisAsyncAnimationFramesSavingRenderer is not guarding against any of the frames failing to export. This can happen due to many reasons - like a faulty drive or insufficient space or the disk being removed mid-export or whatever else.

This saves the QFile::copy() status on every frame export and makes export fail if one of them fails.

Test Plan

Built in docker on my ArchLinux machine and tested exporting the animation (built as AppImage)

Formalities Checklist

  • I confirmed this builds.
  • I confirmed Krita ran and the relevant functions work.
  • I tested the relevant unit tests and can confirm they are not broken. (If not possible, don't hesitate to ask for help!)
  • I made sure my commits build individually and have good descriptions as per KDE guidelines.
  • I made sure my code conforms to the standards set in the HACKING file.
  • I can confirm the code is licensed and attributed appropriately, and that unattributed code is mine, as per KDE Licensing Policy.
  • Does the patch add a user-visible feature? If yes, is there a documentation MR ready for it at Krita Documentation Repository?

Reminder: the reviewer is responsible for merging the patch, this is to ensure at the least two people can build the patch. In case a patch breaks the build, both the author and the reviewer should be contacted to fix the build. If this is not possible, the commits shall be reverted, and a notification with the reasoning and any relevant logs shall be sent to the mailing list, kimageshop@kde.org.

Merge request reports