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

Failures with Firefox on H5P essay report scenario

XMLWordPrintable

      Since some hours ago we are getting consistent failures with the feature / scenario: View attempt essay content

      Only with Firefox, but consistently (I've been able to reproduce it locally).

      Link: https://ci.moodle.org/job/W311.04.01%20-%20Behat%20-%20Firefox%20+%20Postgres/113/

       

      --- Failed steps:
      001 Scenario: View attempt essay content # /var/www/html/mod/h5pactivity/tests/behat/result_longfillin.feature:31
       When I follow "View my attempts" # /var/www/html/mod/h5pactivity/tests/behat/result_longfillin.feature:43
       Link matching locator "View my attempts" not found. (Behat\Mink\Exception\ElementNotFoundException)
      

       

      Git bisect has pointed to MDL-71161:

       

      16a9e8ada7cae1a2bbfd597ae8eb934e303d4088 is the first bad commit
      commit 16a9e8ada7cae1a2bbfd597ae8eb934e303d4088
      Author: Jun Pataleta <jun@moodle.com>
      Date: Thu Mar 25 16:35:46 2021 +0800
      MDL-71161 mod_h5pactivity: Display activity information output component
      mod/h5pactivity/view.php | 5 +++++
       1 file changed, 5 insertions(+)
      

       

            jpataleta Jun Pataleta
            sarjona Sara Arjona (@sarjona)
            Michael Hawkins Michael Hawkins
            Sara Arjona (@sarjona) Sara Arjona (@sarjona)
            CiBoT CiBoT
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 55 minutes
                1h 55m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.