Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Automated testing is not enabled for the 2.0.x dev branch. No passing tests are shown on the module page.
Proposed resolution
Enable automated testing for the 2.0.x dev branch.
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 2022-11-09 10_40_46-Window.png | 6.57 KB | grevil |
Comments
Comment #2
anybodyThanks @Grevil, I agree the Automated Test settings for this project should please be aligned. It's strange if failing tests (only) show up in issues and it looks like the issue broke it, but it's broken in head already.
@justin2pin could you perhaps have a look at this?
Comment #3
grevil commentedMy apologies, tests will only fail locally. Tests run by Jenkins in the module are all passing!
As the Drupal Gitlab API was pretty much broken the last couple of days, added changes to an issue fork wouldn't get tested, so we thought the current state of the dev branch is broken, but this is NOT the case!
Nevertheless, it would be really nice to enable automated testing on dev branch commits.
Comment #4
grevil commentedInteresting... it is not even possible to enable automated testing only for issues but not for dev branch commits...
So I am really unsure why the tests won't show up on the module page, but in issue forks they do?!
Comment #5
justin2pin commentedI don't think this actually has anything to do with tests, which have been running for both commits (dev branch) and issues (issues forks). You can see the recent test history for the 2.x dev branch working correctly here: https://www.drupal.org/node/3134537/qa
However: I did notice that I had not checked the option for the 2.x dev release to show on the main module page, and had not tagged 2.x as the recommended version. I changed both of those options, which you can see on the main module page: https://www.drupal.org/project/layout_paragraphs
I'm closing as "works as designed," feel free to reopen if there are additional issues. Thanks!
Comment #6
anybodyThanks @justin2pin for your super quick and helpful reply! :)
Looks good now, I think we can see this as "Fixed" with the update from @Grevil! Thanks!
Comment #7
grevil commented@justin2pin, tests are now shown on the module page, great!