javascript-modules-engine-SN-custom-context - 125/129 FAILED tests during test execution

[jahia-ci]

An error occurred during the execution of a CI/CD workflow.

Failure Details

Total Tests: 129 - Failure: 125 (skipped: 2, pending: 0) - Executed in 3000s
FAILURES:
| Suite: report.json - Total tests: 129 - Failure: 125 - Executed in 3000s
|   | - Validate the concepts of the tutorial: 2 - Making a Hero Section
|   |    | - FAIL: buildNodeUrl should build a valid URL
|   |    | - FAIL: the page properties should be correctly retrieved
|   |    | - FAIL: the CSS class should be correctly set
|   |    | - FAIL: Discover Hydrogen: the CTA buttons should be correctly rendered
|   | - Validate the concepts of the tutorial: 3 - The "About Us" Page
|   |    | - FAIL: a node type can be rendered using different views
|   |    | - FAIL: about-us.html: the footer should exist (shared template)
|   |    | - FAIL: about-us/our-team.html: the footer should exist (shared template)
|   |    | - FAIL: about-us/our-values.html: the footer should exist (shared template)
|   |    | - FAIL: other-page-single-column.html: the footer should exist (shared template)
|   |    | - FAIL: the footer should not exist on the home page (different template)
|   | - Validate the concepts of the tutorial: 4 - Making a Blog
|   |    | - FAIL: the blog home page should only list published posts in the right order
|   |    | - FAIL: each article should be clickable and lead to a valid page
|   | - Validate the concepts of the tutorial: 5 - View Content in Full Page
|   |    | - FAIL: a-second-article.html: the hero section should be present on the blog post
|   |    | - FAIL: a-second-article.html: the main article should be displayed
|   |    | - FAIL: a-second-article.html: the page should have a 'back to blog home' link
|   |    | - FAIL: welcome-to-hydrogen-blog.html: the hero section should be present on the blog post
|   |    | - FAIL: welcome-to-hydrogen-blog.html: the main article should be displayed
|   |    | - FAIL: welcome-to-hydrogen-blog.html: the page should have a 'back to blog home' link
|   | - Check that components of a module are correctly registered
|   |    | - FAIL: Create a page with .hbs template
|   |    | - FAIL: Verify nodeTypes and icons are registered
|   | - Check that Javascript module settings (UI extensions, rules, configs) are correctly deployed
|   |    | - FAIL: Ensure Content editor UI extension is correctly registered
|   |    | - FAIL: Ensure Jahia rule is correctly registered and working
|   |    | - FAIL: Ensure Jahia URLRewrite rule is correctly registered and working
|   | - Check that the Javascript module has been transformed properly and has the proper header values
|   |    | - FAIL: Check the transformed module headers
|   | - Absolute Area test
|   |    | - FAIL: testAbsoluteArea: Basic Area test
|   |    | - FAIL: testAbsoluteArea: Allowed types area
|   |    | - FAIL: testAbsoluteArea: Number of items area
|   |    | - FAIL: testAbsoluteArea: areaView Area
|   |    | - FAIL: testAbsoluteArea: absolute Area home page
|   |    | - FAIL: testAbsoluteArea: absolute Area site root
|   |    | - FAIL: testAbsoluteArea: absolute Area custom page (sub-level)
|   |    | - FAIL: testAbsoluteArea: non editable Area
|   |    | - FAIL: testAbsoluteArea: Area type
|   |    | - FAIL: testAbsoluteArea: Limited absolute area editing
|   |    | - FAIL: testAbsoluteArea: Limited absolute area editing (home parent) is read-only on other pages
|   |    | - FAIL: home: Limited absolute area editing (home parent) is editable on the home page
|   |    | - FAIL: testAbsoluteArea: should render absolute area with parameters
|   | - Test on add resources component/helper
|   |    | - FAIL: testAddResources: should not contain a div in the head tag in the page source code
|   |    | - FAIL: testAddResources : should contain a link tag in the head tag to load the CSS styles
|   |    | - FAIL: testAddResources : should contain a script tag under the body tag
|   |    | - FAIL: testAddResources : should contain the test body element created by the body script
|   |    | - FAIL: testAddResources : should contain a script tag under the head tag
|   |    | - FAIL: testAddResources : should contain the test head element created by the head script
|   |    | - FAIL: testAddResources : should contain the test inline script element created by the inline script
|   | - Area test
|   |    | - FAIL: testJArea: Basic Area test
|   |    | - FAIL: testJArea: Allowed types area
|   |    | - FAIL: testJArea: Number of items area
|   |    | - FAIL: testJArea: areaView Area
|   |    | - FAIL: testJArea: path Area
|   |    | - FAIL: testJArea: non editable Area
|   |    | - FAIL: testJArea: Area type
|   |    | - FAIL: testJArea: should render area with parameters
|   | - Check on bound components
|   |    | - FAIL: Verify calendar (.jsp content in the template) is correctly bound to the events list
|   |    | - FAIL: Verify that the calendar is correctly refreshed once a new event is added
|   |    | - FAIL: Verify that the facets is working correctly
|   |    | - FAIL: Test boundComponent behavior with area/list creation by edit mode
|   | - Test OSGi configuration in views
|   |    | - FAIL: testConfig: test config in preview
|   |    | - FAIL: testConfig: test config in edit
|   |    | - FAIL: testConfig: test config in live guest
|   |    | - FAIL: testConfig: test config in live logged
|   |    | - FAIL: testConfig: test config in ajax rendered content
|   | - Content templates resolution testsuite
|   |    | - FAIL: Verify content template for jnt:event is correctly displayed
|   |    | - FAIL: Verify findDisplayableNode is correctly resolving jnt:event that is using a JS content template
|   |    | - FAIL: Test default content template is working properly when content doesn't have specific view
|   |    | - FAIL: Test default content template is working properly when content have specific view
|   | - Test on currentContent injected data
|   |    | - FAIL: testCurrentContent: Check currentContent injected JSON node in current view
|   | - getChildNodes function test
|   |    | - FAIL: Verify all children returned
|   |    | - FAIL: Verify filtered children returned
|   |    | - FAIL: Verify filtered + offset children returned
|   |    | - FAIL: Verify filtered + limit children returned
|   |    | - FAIL: Verify filtered + limit + offset children returned
|   |    | - FAIL: Verify limited children returned
|   |    | - FAIL: Verify limited + offset children returned
|   |    | - FAIL: Verify limit is mandatory
|   |    | - FAIL: Verify offset
|   |    | - FAIL: Verify RenderChildren
|   |    | - FAIL: Verify RenderChild
|   | - getNodeProps function test
|   |    | - FAIL: Verify property values from getNodeProps
|   | - getNodesByJCRQuery function test
|   |    | - FAIL: Test getNodesByJCRQuery, case: all
|   |    | - FAIL: Test getNodesByJCRQuery, case: limit
|   |    | - FAIL: Test getNodesByJCRQuery, case: limitMandatory
|   |    | - FAIL: Test getNodesByJCRQuery, case: offset
|   |    | - FAIL: Test getNodesByJCRQuery, case: limitOffset
|   | - Test GQL
|   |    | - FAIL: Check GQL execution in current view
|   |    | - FAIL: Check GQL execution when the view is rendered inside a GraphQL POST request
|   | - Test OSGi configuration in views
|   |    | - FAIL: is polite, says hello and sorts numbers
|   | - Test priority parameter on templates
|   |    | - FAIL: testPriorityTemplateExample1: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (9) is used
|   |    | - FAIL: testPriorityTemplateExample2: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (-5) is used
|   |    | - FAIL: testPriorityTemplateExample3: GIVEN multiple templates with different priorities WHEN resolving the template THEN the template with the highest priority (50) is used
|   | - Test priority parameter on views
|   |    | - FAIL: javascriptExample:testPriorityView1: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (6) is used
|   |    | - FAIL: javascriptExample:testPriorityView2: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (-3) is used
|   |    | - FAIL: javascriptExample:testPriorityView3: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (0) is used
|   |    | - FAIL: javascriptExample:testPriorityView4: GIVEN multiple views with different priorities WHEN resolving the view THEN the view with the highest priority (13) is used
|   | - proxyProps function test
|   |    | - FAIL: Verify property values from getNodeProps
|   | - Verify client side component are rehydrated as expected
|   |    | - FAIL: default: Check that components is hydrated correctly
|   |    | - FAIL: live: Check that components is hydrated correctly
|   | - Verify that registerJahiaComponents behaves as expected
|   |    | - FAIL: Check that components are properly registered
|   | - Render should be editable
|   |    | - FAIL: Without parameter, text should be editable
|   |    | - FAIL: With parameter set to false, text should not be editable
|   |    | - FAIL: With parameter set to true, text should be editable
|   | - Test on render and createContentButtons helpers
|   |    | - FAIL: testRender: should display page composer create button correctly using createContentButtons helper
|   |    | - FAIL: testRender: should render jnt:text JSON node
|   |    | - FAIL: testRender: should render jnt:text JSON node in config: OPTION
|   |    | - FAIL: testRender: should render javascriptExample:test JSON node in config: OPTION with view: sub
|   |    | - FAIL: testRender: should render JSON node with INCLUDE config
|   |    | - FAIL: testRender: should render JSON node with mixin
|   |    | - FAIL: testRender: should render JSON node with parameters passed to render
|   |    | - FAIL: testRender: should render node with parameters passed to render
|   |    | - FAIL: testRender: should render existing child node using relative path
|   | - Template Picker Correct Order Test
|   |    | - FAIL: should display the correct order of templates
|   | - Template testsuite
|   |    | - FAIL: testTemplate: Verify 3 sections presence
|   |    | - FAIL: testTemplate: Check grouping components
|   |    | - FAIL: testTemplate: Check 3 sections presence in LIVE workspace
|   | - Test current user
|   |    | - FAIL: should display the current user as root
|   | - Test has permission
|   |    | - FAIL: should display the permission
|   | - Test i18n
|   |    | - FAIL: Test I18n values in various workspace/locales and various type of usage SSR/hydrate/rendered client side
|   |    | - FAIL: Support i18n with components from multiple JS modules on the same page
|   | - test isNodeType
|   |    | - FAIL: should display the node type
|   | - Test locale
|   |    | - FAIL: should display the locale
|   | - Test url parameters
|   |    | - FAIL: should display the url parameters
|   |    | - FAIL: should display the url parameters with special chars
|   | - Test on url helper
|   |    | - FAIL: Generated URLs should be correct
|   |    | - FAIL: Generated URLs should be correct with vanity
|   | - Test virtual nodes
|   |    | - FAIL: testVirtualNode: Check virtual nodes are correctly rendered in preview mode
|   |    | - FAIL: testVirtualNode: Check virtual nodes are correctly rendered in customized preview mode
SKIPPED:
| Suite: report.json - Total tests: 129 - Skipped: 2 - Executed in 3000s
|   | - getNodeProps function test
|   |    | - SKIPPED: Verify property values from getNodeProps

Service: javascript-modules-engine-SN-custom-context
Date: 2026-08-25T01:13:30.966Z
Source URL: https://github.com/Jahia/javascript-modules/actions/runs/32792807958
Dedup Key: 42bc73dc-b3dd-5172-addc-f57d68c44000

Details about the process or how to disable notifications is available on this confluence page .

Expand to learn more about these issues

About

This issue was created by jahia-reporter by an automated CI/CD workflow (see link above).
Using a "Dedup key", the tool will identify similar failure for a particular service.

The following logic is present:

• A successful run for a service will close ALL open issues for that service for ALL dedup keys

• Updates are not posted if the status did not change (i.e. two subsequent failures only results in one single issue or single comment).

• A previously closed issues will be re-opened if it starts failing again.

The Dedup key is generated from the list of failed test cases sorted alphabetically.

[jahia-ai]

Automated triage

Classification: build/dependency mismatch
Analyzed run: https://github.com/Jahia/javascript-modules/actions/runs/32792807958
Logs source: github artifacts
Cross-repository signal: likely related to #776 — same run ID (32792807958), identical 125/129 failure pattern; both configurations (SN and SN-custom-context) share the same root cause (template-set module not starting)

What happened

125 of 129 tests failed because the template-set module did not start properly, causing 192 out of 204 provisioning operations to fail. Site creation scripts returned .failed, leaving all test sites absent from the JCR. Every Cypress test that visits a page or creates content then failed with 400 Bad Request or 404 Not Found. The root cause is a dependency or configuration problem in the javascript-modules test provisioning manifest that prevents the template-set module from starting against the current 8-SNAPSHOT Jahia image.

Evidence

"templateSet" is null  (152 occurrences)
createSite.groovy result: .failed  (37 occurrences)
javax.jcr.PathNotFoundException: /sites/javascriptTestSite  (96 occurrences)

Recommendation

Investigate why the template-set module fails to start in the javascript-modules provisioning manifest. The 152 "templateSet is null" errors indicate the module either did not install or its OSGi bundle did not activate. Check the provisioning manifest for missing or misconfigured dependencies. This is a deterministic build/dependency issue — a rerun will not help.

---

_{Automated analysis by Claude Code 2.1.231 (Claude Code) · model: mimo-v2.5-pro — analysis run log}

[jahia-ai]

Automated triage

Classification: build/dependency mismatch
Analyzed run: https://github.com/Jahia/javascript-modules/actions/runs/32792807958
Logs source: github artifacts
Cross-repository signal: likely related to #776 — same run ID (32792807958), identical 125/129 failure pattern; both configurations (SN and SN-custom-context) share the same root cause (template-set module not starting)

What happened

125 of 129 tests failed because the template-set module did not start properly, causing 192 out of 204 provisioning operations to fail. Site creation scripts returned .failed, leaving all test sites absent from the JCR. Every Cypress test that visits a page or creates content then failed with 400 Bad Request or 404 Not Found. The root cause is a dependency or configuration problem in the javascript-modules test provisioning manifest that prevents the template-set module from starting against the current 8-SNAPSHOT Jahia image.

Evidence

"templateSet" is null  (152 occurrences)
createSite.groovy result: .failed  (37 occurrences)
javax.jcr.PathNotFoundException: /sites/javascriptTestSite  (96 occurrences)

Recommendation

Investigate why the template-set module fails to start in the javascript-modules provisioning manifest. The 152 "templateSet is null" errors indicate the module either did not install or its OSGi bundle did not activate. Check the provisioning manifest for missing or misconfigured dependencies. This is a deterministic build/dependency issue — a rerun will not help.

---

_{Automated analysis by Claude Code 2.1.231 (Claude Code) · model: mimo-v2.5-pro — analysis run log}

[jahia-ai]

Automated triage

Classification: build/dependency mismatch
Analyzed run: https://github.com/Jahia/javascript-modules/actions/runs/32792807958
Logs source: github artifacts
Cross-repository signal: likely related to #776 — same run ID (32792807958), identical 125/129 failure pattern; both configurations (SN and SN-custom-context) share the same root cause (template-set module not starting)

What happened

125 of 129 tests failed because the template-set module did not start properly, causing 192 out of 204 provisioning operations to fail. Site creation scripts returned .failed, leaving all test sites absent from the JCR. Every Cypress test that visits a page or creates content then failed with 400 Bad Request or 404 Not Found. The root cause is a dependency or configuration problem in the javascript-modules test provisioning manifest that prevents the template-set module from starting against the current 8-SNAPSHOT Jahia image.

Evidence

"templateSet" is null  (152 occurrences)
createSite.groovy result: .failed  (37 occurrences)
javax.jcr.PathNotFoundException: /sites/javascriptTestSite  (96 occurrences)

Recommendation

Investigate why the template-set module fails to start in the javascript-modules provisioning manifest. The 152 "templateSet is null" errors indicate the module either did not install or its OSGi bundle did not activate. Check the provisioning manifest for missing or misconfigured dependencies. This is a deterministic build/dependency issue — a rerun will not help.

---

_{Automated analysis by Claude Code 2.1.231 (Claude Code) · model: mimo-v2.5-pro — analysis run log}

[jahia-ai]

Automated triage

Classification: build/dependency mismatch
Analyzed run: https://github.com/Jahia/javascript-modules/actions/runs/32792807958
Logs source: github artifacts
Cross-repository signal: likely related to #776 — same run ID (32792807958), identical 125/129 failure pattern; both configurations (SN and SN-custom-context) share the same root cause (template-set module not starting)

What happened

125 of 129 tests failed because the template-set module did not start properly, causing 192 out of 204 provisioning operations to fail. Site creation scripts returned .failed, leaving all test sites absent from the JCR. Every Cypress test that visits a page or creates content then failed with 400 Bad Request or 404 Not Found. The root cause is a dependency or configuration problem in the javascript-modules test provisioning manifest that prevents the template-set module from starting against the current 8-SNAPSHOT Jahia image.

Evidence

"templateSet" is null  (152 occurrences)
createSite.groovy result: .failed  (37 occurrences)
javax.jcr.PathNotFoundException: /sites/javascriptTestSite  (96 occurrences)

Recommendation

Investigate why the template-set module fails to start in the javascript-modules provisioning manifest. The 152 "templateSet is null" errors indicate the module either did not install or its OSGi bundle did not activate. Check the provisioning manifest for missing or misconfigured dependencies. This is a deterministic build/dependency issue — a rerun will not help.

---

_{Automated analysis by Claude Code 2.1.231 (Claude Code) · model: mimo-v2.5-pro — analysis run log}

[baptistegrimaud]

Root cause is the product image, not this repository — nothing to change here.

The module sha did not move across the transition. Only the ghcr.io/jahia/jahia-ee-dev:8-SNAPSHOT tag did:

	2026-08-24 (green)	2026-08-25 (red)
module sha	741904b5	741904b5
product build	5a1f970	759ba2c

That newer image narrowed the set of URL schemes the provisioning API accepts from a submitted manifest, and js: is not currently among them. Both JS entries in tests/provisioning-manifest-snapshot.yml are therefore refused:

ERROR [o.j.b.p.i.o.InstallModule] - Cannot install js:mvn:org.jahia.test/javascript-modules-engine-test-module/LATEST/tgz
    = java.io.IOException: Scheme js cannot be resolved, js:mvn:...

Worth noting the message mentions maven reachability, which is misleading here: nothing is fetched at all — the URL is rejected on its scheme, in about a millisecond.

From there it cascades: the test module and the hydrogen sample never install, createSite.groovy gets a null template set, no test site is created, and every spec that needs one fails. installed-jahia-modules.json confirms neither module is present.

This is deterministic, not flaky — both nightly jobs (SN and SN-custom-context) fail identically on the same image, and re-running will not help. It will stay red until a product image accepting js: again is published. A fix is in progress on the product side.

[jahia-ci]

✅ A CI/CD workflow has completed successfully, closing the issue.

Details:

Total Tests: 129 - Failure: 0 (skipped: 0, pending: 0) - Executed in 407s

Date: 2026-08-26T00:29:40.550Z
Source URL: https://github.com/Jahia/javascript-modules/actions/runs/32914282146