Just git updated a 3.2 to highest 3.2.5 and noticed a deadlock.mbz

Just git updated a 3.2 to highest 3.2.5 and noticed a deadlock.mbz

by Ken Task -
Number of replies: 3
Picture of Particularly helpful Moodlers

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



Average of ratings: -
In reply to Ken Task

Re: Just git updated a 3.2 to highest 3.2.5 and noticed a deadlock.mbz

by Matteo Scaramuccia -

Hi Ken,
fixtures are the assets used in the automated tests.

Find the answer in MDL-57698 (and https://github.com/moodle/moodle/commit/b1fc170b21b577a10a14414b43a92a942c5850d6#diff-52dcc3703ec871618cbd55c77be8c5fe).

HTH,
Matteo

Average of ratings: -
In reply to Matteo Scaramuccia

Re: Just git updated a 3.2 to highest 3.2.5 and noticed a deadlock.mbz

by Ken Task -
Picture of Particularly helpful Moodlers

Thanks, Matteo.   So it's a test and meant for servers that run mssql or other DB's that have issues with backups.  Hmmmm ...

'spirit of sharing', Ken

Average of ratings: -
In reply to Ken Task

Re: Just git updated a 3.2 to highest 3.2.5 and noticed a deadlock.mbz

by Matteo Scaramuccia -

Hi Ken,
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.

HTH,
Matteo

Average of ratings: -