file in code/backup/controller/tests/fixtures/
Inspecting it by viewing the contents via command line appears to be a valid backup. It's contents does have a backup log:
-rw-r--r-- 0/0 1471 2017-07-25 21:23 moodle_backup.log
There's same in an updated 3.3 to highest.
Can anyone explain the purpose of the 'deadlock.mbz' file?
Thanks, in advance, Ken
fixtures are the assets used in the automated tests.
yep: you could argue that maybe it's time to split the Moodle distribution package into two different packages, one strictly for the production i.e. w/o any kind of test ("base code"), the other including the tests for kind of staging env, to provide feedback about your ecosystem when running those tests (given that the staging env should be almost equal to production).
Makes sense to me but it means that you're supposed to select the right package depending on your deployment policies.