dfcd75f20d
Infinite blocking is bad.
2021-01-12 13:58:28 -05:00
b74ec6919d
Don't blow up just because irrelevant cleanup complains.
2021-01-12 13:24:42 -05:00
3489e381be
Get rid of finalizer which, I suspect, is keeping tests from shutting down on Windows.
2021-01-12 11:16:45 -05:00
3764e3b6b1
A (so far failing) test for SSH public key authentication.
2021-01-07 13:59:57 -05:00
a536a1a970
First passing end-to-end test of SFTP
2021-01-07 12:50:31 -05:00
054af4b76e
Sketch of where SFTP setup needs to happen.
2021-01-07 11:25:26 -05:00
7dda680cb2
Already using "tahoe run", de-emphasize "tahoe start"
2020-12-09 10:51:10 -05:00
b9f7bcab4e
flakes
2020-10-27 09:49:58 -04:00
75b3bf1097
Refuse to continue if the introducer fURL has no location hints.
2020-10-16 11:27:05 -04:00
74a77a48cc
Merge 'origin/master' into 3320.github-actions-windows-integration-tests
2020-07-21 13:50:47 -04:00
957e089715
Fix typo
2020-07-21 11:56:44 -04:00
e4e59c7aab
Use a Chutney revision that works with Python 2
2020-07-21 10:44:49 -04:00
9e82df4fa7
Use skipif decorator to omit Tor integration test setup on Windows
2020-07-19 09:19:19 -04:00
7d93ae9213
Skip Tor tests on Windows
2020-06-22 20:18:00 -04:00
25edce6257
Don't create the magic-folder directories for each node
2020-04-13 12:13:45 -04:00
1fba2d6ea2
Remove the magic-folder integration tests
2020-02-13 10:28:25 -05:00
adc6e39cde
introducer fixture returns a TahoeProcess
2019-08-20 00:17:28 -06:00
5db3909478
actual str-ports string
2019-08-20 00:17:28 -06:00
4feba8d7f9
add a --helper command-line option, and a helper-using test
2019-08-20 00:17:28 -06:00
643b26978f
unused import
2019-08-13 10:37:02 -06:00
4dc7f9637e
naming
2019-08-10 20:00:04 -06:00
926fa77ccb
naming for tor-introducer fixture
2019-08-10 13:53:09 -06:00
425d16e39d
get rid of time.sleep usage for 'readiness'
2019-08-08 21:03:39 -06:00
e7c387a7fc
Instead of abusing the process transport, introduce a new object
2019-08-08 21:02:50 -06:00
ba5f44354b
Merge pull request #636 from meejah/integration-test-coverage
...
coverage for integration tests
2019-08-08 18:40:29 +00:00
025b89855f
refactor so we only check coverage in one place
2019-08-07 14:03:16 -06:00
8e4b05214a
add --coverage for integration tests
2019-08-06 16:47:43 -06:00
cd0ec043a8
Rely on the PATH now being passed down to find git
2019-08-02 16:50:21 -06:00
7f1673596f
Pass the whole parent environment down to the child
...
You never know what is in here that is totally essential to the operation of
some random thing. :(
2019-08-02 16:49:50 -06:00
432aaa2904
Do some Eliot logging in the integration test suite
2019-02-27 09:12:00 -05:00
4611e38b01
Merge pull request #548 from tahoe-lafs/2970.keep-tempdir
...
Document --keep-tempdir correctly
Fixes: ticket:2970
2019-02-18 09:51:42 -05:00
f5b7058efe
Allow an error exit status from flogtool dump
...
If the flog is truncated, parsing it will fail and flogtool will exit with an
error. There's no particular reason to allow this to fail a test.
2019-02-15 13:46:25 -05:00
9a77f1d2e9
This default is also not necessary.
2019-02-15 13:37:42 -05:00
7226fedd9c
Avoid having this line crammed onto the end of a line of pytest output
2019-02-15 13:37:27 -05:00
845e1e7a4a
There is no need for a default. There is always a value.
2019-02-15 13:24:23 -05:00
2c994b4417
Document the usage correctly
2019-02-15 13:24:17 -05:00
e511adbf63
Use the new cleanup helper for process cleanup
...
This removes some repetition of logic and switches to a more aggressive
cleanup approach.
2019-02-15 12:41:45 -05:00
19e03bbff0
pyflakes cleanups
2019-02-15 11:50:14 -05:00
f905d80760
switch to pytest_twisted
2019-02-05 11:03:35 -05:00
ab58c7a938
Link to the ticket for that
2019-01-24 15:57:35 -05:00
402b2c3bd3
If TorNet status fails, proceed anyway
2019-01-24 15:57:35 -05:00
bedf092ca3
Try to report the child process output
2019-01-24 15:57:35 -05:00
f7cfd62908
tell travis + tox about pytest.twisted in a different way
2018-01-23 12:52:46 -07:00
da4e7dcfbe
hush a bunch of not-really-problems caught by the lgtm.com static analyzer
...
This is all minor stuff: unreachable debug code (that should be commented-out
instead of in an 'if False:' block), unnecessary 'pass' and 'global'
statements, redundantly-initialized variables. No behavior changes. Nothing
here was actually broken, it just looked suspicious to the static analysis at
https://lgtm.com/projects/g/tahoe-lafs/tahoe-lafs/alerts/?mode=list .
2017-12-31 00:19:41 +01:00
c83dde8629
Use first element returned by which
2017-01-09 19:54:51 +00:00
805be64769
Use which from twisted
...
fixes #2856
2017-01-09 17:58:41 +00:00
e32b664b2b
Adjust default poll_interval
...
Also adds a --poll-interval option to both 'magic-folder join'
and 'magic-folder create' so that the integration tests can pass
something "very short".
2016-12-14 20:29:41 -07:00
b96122a8ff
Adding to the py.test integration tests, this:
...
- (on travis) installs Tor
- installs Chutney
- uses it to build a local Tor test-network
- set up an introducer on this test-network
- sets up two storage servers on this test-network
- proves that one can add a file, and the other can download it
I also mark the two tests that occasionally fail as
expected failures for now
2016-10-18 18:06:41 -07:00
2497435c1a
use full paths for everything
2016-09-26 13:33:45 -07:00
a0fc80d544
Use "python -m allmydata.scripts.runner" instead of tahoe.exe
...
On windows, it seems that the generated tahoe.exe (which comes
via entry_points=) doesn't deal with signals nicely. I'm not
sure if this is a pip bug (or just "one of those Windows things")
but running with python -m allows us to kill our subprocesses.
2016-09-26 13:33:45 -07:00
