-
Bug
-
Resolution: Fixed
-
Major
-
4.1
-
MOODLE_401_STABLE
-
MOODLE_401_STABLE
-
MDL-75820-master -
-
1
-
Team Omega 4.1 Sprint 0.5
This has started to happen the 21 Sept 2022, only in master (4.1dev). The first is:
https://ci.moodle.org/job/S.03.01%20-%20Behat%20-%20Chrome%20+%20Postgres%20(HEADED)/779/
001 Scenario: Configure the block on a non-graded activity to show 3 high scores # /var/www/html/blocks/activity_results/tests/behat/addblockinactivity.feature:47
|
And I press "Save changes" # /var/www/html/blocks/activity_results/tests/behat/addblockinactivity.feature:44
|
element click intercepted: Element <input type="submit" id="gradersubmit" class="btn btn-primary" value="Save changes"> is not clickable at point (131, 635). Other element would receive the click: <div id="page" data-region="mainpage" data-usertour="scroller" class="drawers show-drawer-right drag-container">...</div>
|
(Session info: chrome=96.0.4664.45) (Facebook\WebDriver\Exception\ElementClickInterceptedException)
|
|
|
002 Scenario: Block should select current activity by default # /var/www/html/blocks/activity_results/tests/behat/addblockinactivity.feature:65
|
And I press "Save changes" # /var/www/html/blocks/activity_results/tests/behat/addblockinactivity.feature:44
|
element click intercepted: Element <input type="submit" id="gradersubmit" class="btn btn-primary" value="Save changes"> is not clickable at point (131, 635). Other element would receive the click: <div id="page" data-region="mainpage" data-usertour="scroller" class="drawers show-drawer-right drag-container">...</div>
|
(Session info: chrome=96.0.4664.45) (Facebook\WebDriver\Exception\ElementClickInterceptedException)
|
It affects HEADED Chrome runs only. And only in CIs (not reproducible with HEADED Chrome - Mac, locally).
- 10 repetitions were launched @ CI and all them failed (link).
- 5 repetitions were launched locally and all them passed.
To reproduce it, just run chrome (HEADED) and:
--name 'The activity results block displays student scores'
In the mean time, the @skip_interim tag has been added to those 2 scenarios to allow CI to pass (so they only will be executed when the @skip_interim tag is specified). That has been done in a commit associated with MDL-75153, not because of any reason, but because we needed an ongoing issue to add the tag to the scenarios.
IMPORTANT: Once it has been detected why those 2 scenarios have started to fail and this issue has been fixed, as part of the fix, the {@skip_interim}} tag needs to be removed from the failing feature.
Ciao 
- has a non-specific relationship to
-
MDL-75153 Update tertiary dropdown into a future generic component
-
- Closed
-
