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

Random "Export settings with an existing name" behat failure

XMLWordPrintable

      Started on the 22nd of September 2022, 4.1dev (Oracle + Chrome)

      Failed test/scenario

      I can add a new preset with current settings.Export settings with an existing name

      Failed builds

      https://ci.moodle.org/job/W401.03.05%20-%20Behat%20-%20Chrome%20+%20Oracle/37/

      Console output

      001 Scenario: Export settings with an existing name                                                 # /var/www/html/admin/tool/admin_presets/tests/behat/export_settings.feature:8
      		 
            Then I should see "Moodle with all of the most popular features" in the "Starter" "table_row" # /var/www/html/admin/tool/admin_presets/tests/behat/export_settings.feature:14
      		 
              "Moodle with all of the most popular features" text was not found in the "Starter" element (Behat\Mink\Exception\ExpectationException)

        1. MDL-77079 editor.png
          MDL-77079 editor.png
          54 kB
        2. MDL-77079 presets table.png
          MDL-77079 presets table.png
          96 kB
        3. MDL-77079 presets table local.png
          MDL-77079 presets table local.png
          106 kB

            lameze Simey Lameze
            lameze Simey Lameze
            Angelia Dela Cruz Angelia Dela Cruz
            Ilya Tregubov Ilya Tregubov
            CiBoT CiBoT
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 2 hours, 52 minutes
                1d 2h 52m

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