[
https://issues.apache.org/jira/browse/SLING-12600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-12600:
-----------------------------------
Description:
since
[https://github.com/apache/sling-org-apache-sling-starter/commit/bf8d1246a552b9390dab60afdf4a64b28908dc6b]
(in context of SLING-11905) which enabled the starter IT builds again for
windows, the starter ITs are flaky on the windows builds.
sometimes only the Java 17 windows build fails, sometimes only the Java 21
windows build, sometimes they pass. seems to be random flakyness.
example:
[https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/PR-424/6/cloudbees-pipeline-explorer/]
[https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/PR-423/5/cloudbees-pipeline-explorer/]
the builds fails with some URLs called by the ITs return something unexpected
(script code instead of the processed result?). in those two examples it was
related to
{{org.apache.sling.launchpad.webapp.integrationtest.NodetypeRenderingTest}}
was:
since
[https://github.com/apache/sling-org-apache-sling-starter/commit/bf8d1246a552b9390dab60afdf4a64b28908dc6b]
(in context of SLING-11905) which enabled the starter IT builds again for
windows, the starter ITs are flaky on the windows builds.
sometimes only the Java 17 windows build fails, sometimes only the Java 21
windows build, sometimes they pass. seems to be random flakyness.
example:
[https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/PR-424/6/cloudbees-pipeline-explorer/]
[https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/PR-423/5/cloudbees-pipeline-explorer/]
the builds fails with some URLs called by the ITs return something unexpected
(script code instead of the processed result?). in those two examples it was
related to {{org.apache.sling.launchpad.webapp.jsp.TagFileTest}}
Summary: Starter builds are flaky on Windows nodes:
org.apache.sling.launchpad.webapp.integrationtest.NodetypeRenderingTest (was:
Starter builds are flaky on Windows nodes: in
org.apache.sling.launchpad.webapp.jsp.TagFileTest)
> Starter builds are flaky on Windows nodes:
> org.apache.sling.launchpad.webapp.integrationtest.NodetypeRenderingTest
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-12600
> URL: https://issues.apache.org/jira/browse/SLING-12600
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Reporter: Stefan Seifert
> Priority: Major
> Fix For: Starter 13
>
>
> since
> [https://github.com/apache/sling-org-apache-sling-starter/commit/bf8d1246a552b9390dab60afdf4a64b28908dc6b]
> (in context of SLING-11905) which enabled the starter IT builds again for
> windows, the starter ITs are flaky on the windows builds.
> sometimes only the Java 17 windows build fails, sometimes only the Java 21
> windows build, sometimes they pass. seems to be random flakyness.
> example:
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/PR-424/6/cloudbees-pipeline-explorer/]
> [https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/PR-423/5/cloudbees-pipeline-explorer/]
> the builds fails with some URLs called by the ITs return something unexpected
> (script code instead of the processed result?). in those two examples it was
> related to
> {{org.apache.sling.launchpad.webapp.integrationtest.NodetypeRenderingTest}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
