anton-vinogradov opened a new pull request, #69: URL: https://github.com/apache/ignite-python-thin-client/pull/69
JIRA: https://issues.apache.org/jira/browse/IGNITE-29167 ## Problem `test_examples` is parametrized with the absolute path of each example script. pytest puts that path into the test id, so the test name depends on the agent's work directory. On ci2.ignite.apache.org ("Thin client: Python" in the RunAll chain) agents have two different work roots, so one test has two names and two histories: ``` 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) ``` 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. The same happens to all 13 example tests. Because of this: - the history of each example test is split in two; - a PR run is compared with only part of the master history; - a passing rerun on an agent with the other work root does not clear the failure, because TeamCity sees it as a different test. ## Change Use the script file name as the parameter id (`ids=os.path.basename`). The test still runs the script by its full path. The TeamCity name becomes: ``` tests.test_examples.test_examples(read_binary_py) ``` TeamCity will see the 13 example tests as new tests once, and their history starts again from this change. ## Testing - `pytest --collect-only -q tests/test_examples.py` shows ids like `test_examples[read_binary.py]` instead of the absolute path. - With `TEAMCITY_VERSION` set, teamcity-messages reports `tests.test_examples.test_examples(read_binary_py)`. - `flake8 tests/test_examples.py` passes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
