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

Failures with Firefox on H5P essay report scenario (take #3)

    XMLWordPrintable

Details

    • MOODLE_39_STABLE
    • MOODLE_39_STABLE
    • Hide

      Ensure 39_STABLE behat runs are back to pass @ CI

      Show
      Ensure 39_STABLE behat runs are back to pass @ CI

    Description

      This is a backport of MDL-71876 that was a backport of MDL-71337.

      Basically, a recent FF upgrade made that test to start failing in all branches, but we didn't detect 39_STABLE was affected because that branch is in security-only support now and we had not run any job there over the last weeks.

      Today, for another (travis fixes, see MDL-71804) issue, we got 39_STABLE tests executed and the very same problem was detected there. And we cannot keep that branch (LTS) failing.

      Link to failure: https://ci.moodle.org/view/Testing/job/DEV.01%20-%20Developer-requested%20Behat/14118/

      So this is, simply, about to backport the fix from MDL-71876 and ensure it makes 39_STABLE behat runs green again.

      Attachments

        Issue Links

          Activity

            People

              stronk7 Eloy Lafuente (stronk7)
              stronk7 Eloy Lafuente (stronk7)
              Andrew Lyons Andrew Lyons
              Andrew Lyons Andrew Lyons
              CiBoT CiBoT
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 45 minutes
                  45m

                  Clockify

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