Python runners aren't aware of suites: they report ``fully.qualified.test.names``.
These names are splitted to the suites on the Python side, and just before process ends we close all of them.
GitOrigin-RevId: 4e1ad5b308cd393ac8877e1f6e1f616b254a130c
Note that `os.path.basename(path)` returns an empty string (`''`) when `path` ends in a slash.
GitOrigin-RevId: e400e794d5e0de0cf29ab6796ffac5972f50eb53
``assert "[]" == []``
``assert "123" == 123``
is only displayed correctly when we ``repr`` both
GitOrigin-RevId: ff962dffe7341e95ceeda613e557e9de5cb2620f
Fixed by merging correct version of teamcity runners.
Boolean option brakes all other arguments when used incorrectly
GitOrigin-RevId: e61955cb10fc98eb3dcf741650b79c64a5a573fc
No need to show summary for pytest in most cases, but some plugins may need it.
So, we add advanced option to enable that
GitOrigin-RevId: 15106a4a68ea2adc048119ad4b45e82640086ce0
Logic implemented in ``teamcity-messages``, see changes in diff_tools.py and pytest_plugin.py
GitOrigin-RevId: 8e9cc8cb350e33a9a1cb49ea78ed7ad29c4e1f96
It seems that every IJ product needs to know WSL-2 IP, but there are no guarantees for an interpreter/runtime to exist on WSL except glibc and kernel of course.
Binary tool runs everywhere.
It must be compiled statically on the oldest Linux possible. It gives us guarantee that it runs on distros without of glibc (i.e. Alpine).
GitOrigin-RevId: 92b26d4e176cc3a46ede7970a2b08a228d0f89b7
The correct way to use parameters is to add them to the test name.
"-k" is also works in some cases, but it is not official nor stable.
* pytest runner reports "testname[param]" as metainfo
* we fetch param
* add "parameters" field to the pytest
* glue it with test name
GitOrigin-RevId: 56c5d93fd93a12ba5742b21af51ea04823a9d8f7
When test runner returns code > 0 (because of test failure), our runner must do the same.
See issue description for the reason
GitOrigin-RevId: 231c9ab337e80f70872bf6e6f61a397599f18e26
According to POSIX, getcwd must resolve symbolic links.
But links in backtrace should not be resolved, otherwise link might point to some dir outside of project root.
We check ``PWD`` (works for bash) with fallback to ``
getcwd``
GitOrigin-RevId: 449e5961d0d59c3fe9a627351c79deb83805d58d
* Remote process command line must be patched to support debug, profile etc.
It is now done with PyRemoteCommandLinePatcher.kt
* WSL2 must run with closed stdin because of MS bug.
So, we check if we are on WSL2, and close it.
* WSL2 uses different approach to connect to host for debug (see PyWSLSocketProvider)
* WSL2 needs several commands to run to get list of mappings, so we wrap it with modal dialog.
GitOrigin-RevId: 1789afd9832f048d10d972f5e0f23977e92f973f
With testdir fixture, pytest runs test under separate pytest (which may be inline or separate process).
Previously we monkeypatched prepareconfig not to call it twice.
But this approach fails with testdir, because same config returned twice leading to double plugin registration.
See comment in YT
GitOrigin-RevId: bd9f11a2a10900fa3c059791d7c0183a20b1ed70
First record in sys.path must be script directory. If it is helpers path, we pop it, and move to the end.
GitOrigin-RevId: 3ca787ebd9a48db15984e5d0552c38073ce09c2b
When we see test runner in "commands" section of tox, we substitute it with our test runners so user may benefit from test trees.
We also pass "offset" because test runners must use it as "parent node".
Set "_jb_do_not_patch_test_runners" to disable this substitution
(cherry picked from commit c7d469e1fed52f2d7fe3aec6d96b665c4aa80a4e)
GitOrigin-RevId: b9eec43a6d26fecb72270b733266ef31989fec2c
Env plugin could break PYTHONPATH.
Helpers import each other, so we need to have helpers dir in sys.path
GitOrigin-RevId: d47b763765f6ff26ab77898f03008c4078e28acc
