[
https://issues.apache.org/jira/browse/SLING-12600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910558#comment-17910558
]
Stefan Seifert commented on SLING-12600:
----------------------------------------
i'm not able to reproduce the problem locally. detailed log excerpt:
{noformat}
[ERROR] Failures:
[ERROR]
NodetypeRenderingTest.testEspHtml:90->RenderingTestBase.assertContains:38
Content does not contain 'ESP template' (content=/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
RENDERED BY nodetype-and-path.esp
TYPE nt:unstructured
PATH /NodetypeRenderingTest/1736172683139/this_is_a_test_17361)
[ERROR] NodetypeRenderingTest.testMiniScriptHtml:69 expected:<[There's no
code in this script, just this constant string]> but was:<[/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
RENDERED BY nodetype-and-path.esp
TYPE nt:unstructured
PATH /NodetypeRenderingTest/1736172683883/this_is_a_test_17361]>
[ERROR]
NodetypeRenderingTest.testPrint:80->RenderingTestBase.assertContains:38 Content
does not contain 'print.esp ends' (content=/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
RENDERED BY nodetype-and-path.esp
TYPE nt:unstructured
PATH /NodetypeRenderingTest/1736172683531/this_is_a_test_17361)
[INFO]
[ERROR] Tests run: 572, Failures: 3, Errors: 0, Skipped: 1
{noformat}
basically, there are a lot of integration tests which upload different ESP
rendering files to the same location and file name (html.esp), and then run an
integration test against it. this should happen in a serial manner, so each
test should be completed before the file is overwritten with a different script
for the next test.
it seems that on windows it sometimes happens that a script from a previous
test is executed, and not the script of the current test.
in the example above {{NodetypeRenderingTest.testEspHtml}} is executed but a
script from {{NodeTypeBasedRenderingTest}} is actually executed in sling.
the question is:
* why is this happening at all? if tests would be executed in parallel by
accident, much more errors should happen and also under Linux
* why does it happen only with windows? some file system specifics involved?
* why i'm not able to reproduce the problem locally? it looks like a racing
condition, and maybe the windows boxes used by jenkins are much slower and more
loaded than my powerful local dev machine
> 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)
