[
https://issues.apache.org/jira/browse/IGNITE-28431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070536#comment-18070536
]
Maksim Davydov commented on IGNITE-28431:
-----------------------------------------
visa:
https://ci2.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyleDucktests?branch=pull%2F12967%2Fhead&buildTypeTab=overview#all-projects
> [ducktests] Stabilize Ducktests tox environments by removing shared homedir
> usage
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-28431
> URL: https://issues.apache.org/jira/browse/IGNITE-28431
> Project: Ignite
> Issue Type: Task
> Reporter: Maksim Davydov
> Assignee: Maksim Davydov
> Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Ducktests codestyle/test step in CI occasionally fails due to corrupted
> or inconsistent tox environments stored under a shared directory:
> {code}
> /home/teamcity/.virtualenvs/ignite-ducktests-*
> {code}
> This happens because the current tox configuration uses:
> {code}
> envdir = {homedir}/.virtualenvs/ignite-ducktests-{envname}
> {code}
> Since {homedir} resolves to the global $HOME directory (e.g.,
> /home/teamcity), multiple builds reuse the same environments. This leads to:
> * Cross-build contamination
> * Broken or partially created virtualenvs
> * Non-deterministic failures (e.g., “cowardly refusing to delete envdir”)
> * Increased flakiness in CI
> *Proposed Solution*: Update tox configuration to use an isolated,
> per-checkout environment directory
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
