[ 
https://issues.apache.org/jira/browse/IGNITE-29167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anton Vinogradov reassigned IGNITE-29167:
-----------------------------------------

    Assignee: Anton Vinogradov

> Python thin client: name test_examples by the example file, not its absolute 
> path
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-29167
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29167
>             Project: Ignite
>          Issue Type: Task
>          Components: python, thin client
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Minor
>
> {{test_examples}} in ignite-python-thin-client is parametrized with the 
> absolute path of each example script, and pytest puts that path into the test 
> name. The agents of ci2.ignite.apache.org have two work roots, 
> {{/opt/teamcity/work}} and {{/data/tcAgent/work}}, so each of the 13 example 
> tests has two names and two histories:
> {noformat}
> tests.test_examples.test_examples(/opt/teamcity/work/425d7af4e9aa99d9/ignite-python-thin-client/tests/__/examples/read_binary_py)
> tests.test_examples.test_examples(/data/tcAgent/work/425d7af4e9aa99d9/ignite-python-thin-client/tests/__/examples/read_binary_py)
> {noformat}
> From 2026-10-03 to 2026-10-18, master ran read_binary.py 106 times: 25 runs 
> under the first name and 81 under the second. Because of this:
> * the history of each example test is split in two, so a PR run is compared 
> with only part of it;
> * a passing re-run on an agent with the other work root does not clear a 
> failure, because TeamCity sees another test.
> Fix: use the script file name as the pytest parameter id 
> ({{ids=os.path.basename}}). The test still runs the script by its full path. 
> TeamCity then reports {{tests.test_examples.test_examples(read_binary_py)}} 
> on every agent. The 13 example tests get new names once, and their history 
> starts again from this change.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to