Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-62371

Add debugging to help track down performance issues

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide

      Master

      The tool has not been updated with these changes so testing on master differs slightly.

      Setup
      1. Login as admin
      2. Open Site administration -> Users -> Define roles
      3. Create a new role:
        1. Upload the attached dpo.xml preset
        2. Create the role a the system context
      4. Open Site administration -> Users -> Assign system roles
      5. Assign your admin user to the role
      6. Open Site administration -> Users -> Privacy and policies
        1. Tick Contact Data Protection Officer
        2. Select your new role from the Data Protection Officer role mapping
      User requests
      1. Place the attached runadhoc.php script in your Moodle directory
      2. On the Command line, run:

        php runadhoc.php
        

      3. Open Site administration -> Users -> Data requests
      4. Create a new export request for any user
        1. It should be shown as "Pending"
      5. Run runadhoc.php again
        1. Confirm that the output included detail of each component which was fetched
      6. In the UI, refresh the page
      7. Choose Actions => Approve request
      8. Run runadhoc.php again
        1. Confirm that the output included detail of each component which was fetched
      9. In the UI
      10. Create a new delete request for any user (preferable one you don't care about)
      11. Run runadhoc.php again
        1. Confirm that the output included detail of each component which was fetched

      All branches

      1. Place the attached testcontextdelete.php script in your Moodle directory
      2. Run it:

        php testcontextdelete.php
        

      3. Choose a context from the list of suggestions
        1. Confirm that the output included detail of each component which was deleted

      3.3 , and 3.4 only

      Test user export
      1. Place the attached testfinal.php script in your Moodle directory
      2. Run it:

        php testfinal.php
        

      3. Enter a username
        1. Confirm that the output included detail of each component which was fetched
        2. Confirm that the output included detail of each component which was exported
      Test user removal
      1. Place the attached testdelete.php script in your Moodle directory
      2. Run it:

        php testdelete.php
        

      3. Enter a username
        1. Confirm that the output included detail of each component which was fetched for removal
        2. Confirm that the output included detail of each component which was actually deleted
      Show
      Master The tool has not been updated with these changes so testing on master differs slightly. Setup Login as admin Open Site administration -> Users -> Define roles Create a new role: Upload the attached dpo.xml preset Create the role a the system context Open Site administration -> Users -> Assign system roles Assign your admin user to the role Open Site administration -> Users -> Privacy and policies Tick Contact Data Protection Officer Select your new role from the Data Protection Officer role mapping User requests Place the attached runadhoc.php script in your Moodle directory On the Command line, run: php runadhoc.php Open Site administration -> Users -> Data requests Create a new export request for any user It should be shown as "Pending" Run runadhoc.php again Confirm that the output included detail of each component which was fetched In the UI, refresh the page Choose Actions => Approve request Run runadhoc.php again Confirm that the output included detail of each component which was fetched In the UI Create a new delete request for any user (preferable one you don't care about) Run runadhoc.php again Confirm that the output included detail of each component which was fetched All branches Place the attached testcontextdelete.php script in your Moodle directory Run it: php testcontextdelete.php Choose a context from the list of suggestions Confirm that the output included detail of each component which was deleted 3.3 , and 3.4 only Test user export Place the attached testfinal.php script in your Moodle directory Run it: php testfinal.php Enter a username Confirm that the output included detail of each component which was fetched Confirm that the output included detail of each component which was exported Test user removal Place the attached testdelete.php script in your Moodle directory Run it: php testdelete.php Enter a username Confirm that the output included detail of each component which was fetched for removal Confirm that the output included detail of each component which was actually deleted
    • Affected Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
    • Fixed Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE
    • Pull Master Branch:
      MDL-62371-master

      Description

      We need to modify the manager to:

      • add an mtrace to say which component is being processed
      • add a time taken for each component

      See https://moodle.org/mod/forum/discuss.php?d=370387#p1492945 for some rationale.

        Attachments

        1. dpo.xml
          26 kB
        2. example.png
          example.png
          1.22 MB
        3. runadhoc.php
          3 kB
        4. testcontextdelete.php
          1 kB
        5. testdelete.php
          2 kB
        6. testfinal.php
          2 kB

          Issue Links

            Activity

              People

              Assignee:
              dobedobedoh Andrew Nicols
              Reporter:
              dobedobedoh Andrew Nicols
              Peer reviewer:
              Adrian Greeve
              Integrator:
              Eloy Lafuente (stronk7)
              Tester:
              Marina Glancy
              Participants:
              Component watchers:
              Andrew Nicols, Jun Pataleta, Michael Hawkins, Shamim Rezaie, Simey Lameze
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                17/May/18