Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
ckeditor5.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Aug 2026 at 13:29 UTC
Updated:
4 Sep 2026 at 02:02 UTC
Jump to comment: Most recent
Comments
Comment #3
longwaveComment #5
smustgrave commentedThere a neat gitlab trick to run x number of times?
Comment #6
longwaveI tried to do 300 runs in https://git.drupalcode.org/project/drupal/-/jobs/11482920 but 1. it timed out and 2. it is running into #3616075: [random test failure] CKEditor5Test::testExistingContent in the same file. I think we should combine them.
To do the multiple runs you can start the "repeat class test" job but you have to know the variable names to configure it. So, I also opened #3616180: [ci] Improve repeat test class job configuration to make this easier. Not sure if the GitLab permissions issue affects some people trying to run this job, too.
Comment #7
longwaveComment #8
longwaveBumping this to critical as it's affected a number of pipelines that I've seen this week alone.
Comment #9
longwaveRunning this 100x in https://git.drupalcode.org/issue/drupal-3616094/-/jobs/11485819
Comment #10
longwaveBetter, but not good enough.
Comment #11
longwaveCan't reproduce locally so far, let's just see if increasing the timeout helps at all.
100x more: https://git.drupalcode.org/issue/drupal-3616094/-/jobs/11486151
Comment #12
charlliequadros commentedI'm testing the change by adding this assertion:
$this->assertNotEmpty($assert_session->waitForText('page My test content has been created.'));I'm trying to run the tests locally before submitting the change, using this command in the terminal:
Comment #13
charlliequadros commentedHi @longwave
The tests with these assertions work because they wait for the message confirming that the content was created or updated successfully. Do you think it would be worth changing the tests to use this type of check?
Comment #14
longwaveSure, feel free to push to the MR if that has worked for you, and we can try it on CI with the "repeat class test" job.
Comment #15
charlliequadros commentedHi @longwave.
I’ve added my changes, but I’m not sure where I should run the tests. I don’t think I have permission to run them, right?
Comment #16
charlliequadros commentedComment #17
longwaveThe job is the "Repeat Class Test" job in CI, not sure who has permission to run it. You have to set the REPEAT_TEST_CLASS variable to the class that you want to test.
I am running it 100x for the class here: https://git.drupalcode.org/issue/drupal-3616094/-/jobs/11511432
Comment #18
longwave@charlliequadros nice work, the 100x run passed every time, which I hadn't managed with the earlier changes.
Comment #21
catchThis looks good. Eventually the selenium/chromium bug might get fixed, but even if it does the assertions won't do any harm.
Committed/pushed to main and 11.x, thanks!
Comment #24
joelpittetSpotted this https://git.drupalcode.org/issue/drupal-3613882/-/jobs/11964276
Should I open a new one sonsidering it's a different test method?
testEmphasisArbitraryHtmlComment #25
joelpittetSeems reasonable cloned this here #3620770: [random test failure] EmphasisTest::testEmphasis