ZyX
0058919c2b
Remove blank lines from pdb output
...
It is the problem that causes python-3.2 pdb tests to fail on travis.
2015-02-21 19:55:39 +03:00
ZyX
9a89d4defa
Do not special-case PyPy+ipython
2015-02-21 19:55:39 +03:00
ZyX
74e81bf788
Restore the timeout
...
There may be a reason for a test to take 3 minutes long, but there is no reason
for the test to take even half a minute long *without any output*.
2015-02-21 19:55:39 +03:00
ZyX
678faed4c2
Force destroying child after everything was done
...
Normally this line should not do anything useful.
2015-02-21 19:55:39 +03:00
ZyX
b7c7d29aa0
Use “non-blocking” read and stop on TIMEOUT and EOF
2015-02-21 19:55:39 +03:00
ZyX
deee40505d
Do not repeat `if` more times then needed
2015-02-21 19:55:39 +03:00
ZyX
38a05b34d7
Do not use “which ipython” in echo since it is no longer relevant
2015-02-21 19:55:38 +03:00
ZyX
6a6991bcb4
Use 3 minutes for timeout
2015-02-21 19:55:38 +03:00
ZyX
7d98218b64
Do not wait, just .read()
...
.read() without arguments should read until EOF is received.
2015-02-21 19:55:38 +03:00
ZyX
0a87b558d9
Do not use child.wait(), it hangs
2015-02-21 19:55:38 +03:00
ZyX
0710f2760f
Open log as binary file for writing
...
Child output is binary.
2015-02-21 16:11:04 +03:00
ZyX
d5361337c1
Use script to test whether python zsh uses matches $PYTHON
2015-02-21 16:08:50 +03:00
ZyX
0f86bbf819
In place of running ipython executable run IPython module
...
This should fix the problem with using wrong ipython for tests.
2015-02-21 15:59:10 +03:00
ZyX
b2ecb8ca84
Do not append PYTHON to *_REPO paths
...
$PYTHON variable is sometimes a full path which makes everything fail. It is
also useless move since directories are destroyed after tests and running two
test.sh scripts in parallel is not supported in any case.
2015-02-21 15:59:10 +03:00
ZyX
bb6342c12a
Tell tmux correct path to shell to use
2015-02-21 15:59:10 +03:00
ZyX
d53c780071
Do not use absolute path for tmux socket
...
Absolute path is too long when using tests in ebuild.
2015-02-21 15:59:10 +03:00
ZyX
1e85f5df15
Disable vterm tests for PyPy completely
2015-02-21 15:59:10 +03:00
ZyX
22162a9656
Replace screen-based tests with pexpect-based tests
...
Currently works for all tests, but dash ones. Not much of a problem since dash
tests were disabled for being unstable.
2015-02-21 15:59:10 +03:00
ZyX
8524ee35e7
Ignore stderr from printf and env
...
socat may close pipe before they succeed to write something which results in
env: write error: Broken pipe
(according to my experience leading printf’s always succeeds to write before
socat closes pipe).
2015-02-21 13:56:58 +03:00
ZyX
e6b3bff50a
Rerun main() only after running finally block
2015-02-21 04:35:56 +03:00
ZyX
5ecf50b4d8
Use different $HOME
2015-02-21 04:35:56 +03:00
ZyX
683691931d
Make sure that there is at least one blank line after full log
2015-02-21 02:38:17 +03:00
ZyX
fb0fba6c6d
Do not modify $PATH and $LD_LIBRARY_PATH unless on travis
2015-02-21 02:38:17 +03:00
ZyX
e7c381a63f
Make sure USER and HOME variables are defined
2015-02-21 02:38:17 +03:00
ZyX
be3fd917a9
Limit maximum amount of attempts to set register a
2015-02-21 02:38:16 +03:00
ZyX
75c5295a8c
Adjust fish version tests for bot-ci-compiled fish
2015-02-21 00:08:12 +03:00
ZyX
0a0af212ad
Allow specifying path to libvterm from environment
...
Uses POWERLINE_LIBVTERM environment variable.
2015-02-20 23:48:26 +03:00
ZyX
8629999379
Make sure that it is possible to use “system” libvterm.so
2015-02-20 23:47:18 +03:00
ZyX
02b31f36bd
Only run fish tests for development version or for 2.1.2 and higher
...
Currently tests also test Vi key bindings support, but it is not in any release
yet.
2015-02-20 23:37:13 +03:00
ZyX
b349d6e390
Make sure that fish tests are not run for old fishes
2015-02-20 23:16:01 +03:00
ZyX
4d09f4fdb0
Do not run Vim tests if Vim is not available, fallback to system Vim
2015-02-20 22:39:50 +03:00
ZyX
8fff21d77b
Set the default value for POWERLINE_TMUX_EXE
2015-02-20 22:36:39 +03:00
ZyX
feb9a57dc0
Move code that prints tmux logs to test_tmux.py
2015-02-19 11:39:12 +03:00
ZyX
f8ba6b021c
Restart failed tmux vterm test a few times
2015-02-19 11:39:12 +03:00
ZyX
4c6a2e3e59
Also check that MIME type matches during tests
...
MIME type names are inconsistent across different systems, so only first
component is used. For example, `file` in Travis Ubuntu detects Python scripts
as `text/x-java`, in Gentoo these are `text/x-python`.
Travis Ubuntu also uses magic file format different from the one
sys-apps/file-5.22 from Gentoo has, making it impossible to fix the issue by
just copying the files from my system.
2015-02-19 02:48:03 +03:00
ZyX
66c6128b66
Wait less in vterm tmux tests
2015-02-07 11:14:09 +03:00
ZyX
92d4beffa4
Wait more before failing tmux vterm tests
...
May fix random test failures.
2015-02-07 05:00:37 +03:00
ZyX
d57be8324a
Do not alter the way keys are fed with PyPy
2015-02-02 00:12:06 +03:00
ZyX
f4e3c3099f
Remove everything up until `class Foo(object):` in pdb tests
...
PyPy3 displays prompt two times on the line where `s` is present.
2015-02-01 12:13:56 +03:00
ZyX
c3e541d16a
Remove empty lines
2015-02-01 12:08:09 +03:00
ZyX
0db8154b9a
Document how to pdb bindings with Python-2.6 and update tests
2015-01-31 21:44:43 +03:00
ZyX
e63a1c7cb5
Display the log after long wait
2015-01-31 21:34:26 +03:00
ZyX
f9d65fb34d
Do not wait for too long in do_run_test
2015-01-31 20:25:40 +03:00
ZyX
2ef5107628
Import overrides from environment in PDB prompts
2015-01-31 20:23:10 +03:00
ZyX
f74320fba8
Add unit tests for pdb segments
2015-01-31 18:54:13 +03:00
ZyX
ef02ab70fb
Also test powerline.bindings.pdb module
2015-01-31 18:52:04 +03:00
ZyX
47dbdd571d
Add pdb integration tests
2015-01-31 18:52:04 +03:00
ZyX
1e7dc7900d
Fix issues found in 1256 pull request
...
Ref #1256
2015-01-25 12:51:19 +03:00
S0lll0s
dd77d420a3
Add BAR (bar ain't recursive) renderer and fitting i3 bindings
2015-01-25 12:26:13 +03:00
ZyX
332a266d87
When testing Vim do not rely on test order and do not save state
...
This commit refactors `TestVim` test class in test_configuration so that
1. `test_environ_update` does not leave state (value of `powerline_config_paths`
global Vim variable) behind other tests can use.
2. `test_local_themes` does not rely on state left from `test_environ_update`,
instead using new facility for providing needed value of
`Powerline.get_config_paths` call. This facility will be used later in BAR
tests.
Ref #1256
2015-01-25 01:58:27 +03:00