[
https://issues.apache.org/jira/browse/IGNITE-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249246#comment-16249246
]
Vyacheslav Daradur commented on IGNITE-6839:
--------------------------------------------
Hi, [~dpavlov], [~avinogradov], sorry for the delay with the answer.
bq. it is not problem in framework, but some local issue: Ignite having newer
code is deployed as 2.2.0 version.
It is the definitely bad situation. In my opinion artifacts of previously
released versions should equal to artifacts in Maven central repo. Manual
deploying should be forbidden.
If necessary to test updates of releases, we should add a new [repository in
Maven
settings|https://maven.apache.org/guides/mini/guide-multiple-repositories.html]
on TeamCity agents with such artifacts, which must be named like 2.2.1, 2.2.2
etc.
The framework supports this feature by tuning of Maven system environment.
bq. To fix this problem it will be required to implement maven-local cleanup
step before compatiblity testing.
There are two ways to implement it:
1) Add a new step of cleaning local repo to the build configuration in TeamCity.
2) Implement a new method of cleaning local repo in Framework, in
{{MavenUtils}} class.
At first sight, both ways can be implemented by calling Maven command [{{mvn
dependency:purge-local-repository}}
|https://maven.apache.org/plugins/maven-dependency-plugin/examples/purging-local-repository.html]
Vote for the first way because it will be called once, before running all test
suites from Framework.
> Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2
> ------------------------------------------------------------------------
>
> Key: IGNITE-6839
> URL: https://issues.apache.org/jira/browse/IGNITE-6839
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: persistence
> Affects Versions: 2.3
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Ignite Compatibility: 2 test are flaky:
>
> org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite:
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
> (fails: 2/55):
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=-1418165996957466785&branch=%3Cdefault%3E&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests&testNameId=1638023358531502921&tab=testDetails&branch_Ignite20Tests=%3Cdefault%3E
> {noformat}
> junit.framework.AssertionFailedError: Directory [binary_meta,
> 135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist
> [/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
> at
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
> at
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
> at
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
> {noformat}
> Test probaly indicates a bug in
> https://issues.apache.org/jira/browse/IGNITE-6285
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
