fd26551c17
_not available_ in the build environment!
2018-06-15 15:17:32 -04:00
9ad7257614
find the project
2018-06-15 15:14:55 -04:00
182d6aec94
necessary but not sufficient
2018-06-15 15:13:17 -04:00
02c5a72924
the env var has an unexpanded ~ in it
...
more trouble than it is worth
2018-06-15 15:00:47 -04:00
0abb7cf350
need sudo here
2018-06-15 14:55:57 -04:00
82b07f3714
not installed yet
2018-06-15 14:55:16 -04:00
dd1d934b25
What is going on with not being able to run these?
2018-06-15 14:53:19 -04:00
7dda09bb20
Cannot use an in-repo script to install git...
2018-06-15 14:51:11 -04:00
00e3a04c7e
Factor steps out for use by machine executer
2018-06-15 14:21:33 -04:00
414c0907a7
Give test_system an ip
executable
...
Same as the net-tools fix for CentOS 7, basically.
2018-06-15 14:01:42 -04:00
f39a85dbd8
Add a VM-based magic-folder test job
2018-06-15 13:46:58 -04:00
c45a53590e
re-enable full test suite
2018-06-15 13:24:01 -04:00
a4ac9ba9ce
Upload the deprecation warning logs as artifacts
2018-06-15 13:20:46 -04:00
be8dca9f58
remove debug env
2018-06-15 13:20:18 -04:00
933096bdab
Spell the test module correctly.
2018-06-15 13:08:40 -04:00
b109850683
A better comment about the deprecations job.
2018-06-15 11:36:15 -04:00
69a7573745
Use yaml merge mapping correctly
...
At least, correctly as far as Ruby is concerned...
2018-06-15 11:07:56 -04:00
03bb4ef1a9
Add a deprecations job
2018-06-15 10:58:51 -04:00
663f98101c
Put more of the Tox setup in the setup step
...
This will give more accurate test step timings.
2018-06-15 10:58:51 -04:00
83cb49e83d
Clean up the CircleCI presentation a bit
2018-06-15 10:58:51 -04:00
66903ba3d7
Make the environment a mapping
...
The documentation explains it as a list of single mappings. That makes
no sense but "no sense" is par for the course. However, "circleci
config validate" is happy if it is merely a mapping.
Making it a mapping lets us do a yaml mapping merge later and reduce
duplication.
2018-06-15 10:58:51 -04:00
7cd387bf5b
Specify tox environment with an env var
...
This will make it easier to override.
2018-06-15 10:58:51 -04:00
e9cddda898
Always run coverage
...
If you do not always run coverage, how will you know what the coverage is?
Also remove some duplication in the environment setup.
2018-06-15 10:58:51 -04:00
9d9a725794
Avoid yaml merge map in one place where possible
2018-06-15 10:58:51 -04:00
e5e5bde7b6
Make the test log available as an artifact
2018-06-15 10:58:51 -04:00
ea046cd30f
Add a locale env var
2018-06-15 10:58:51 -04:00
f51e6da9d2
Factor out the duplicate environment config
2018-06-15 10:58:51 -04:00
afa321ae5f
Factor out more of the test suite run config
2018-06-15 10:58:51 -04:00
30380a0d18
Add an Ubuntu 16.04 job
2018-06-15 10:58:51 -04:00
72fb92a045
whitespace
2018-06-15 10:58:51 -04:00
70c9973b8e
Add an Ubuntu 18.04 job
2018-06-15 10:58:50 -04:00
9cd41b900f
Add a Fedora 28 job
2018-06-15 08:44:52 -04:00
dc1f6d3fec
Add a Fedora 27 job
2018-06-15 08:44:52 -04:00
d728c245f3
Factor out the duplicate test step command
2018-06-15 08:44:52 -04:00
8e782aa33f
Add a CentOS 7 test-running job
2018-06-15 08:44:52 -04:00
53adf5083d
Shorten the long path used by the long path test
2018-06-15 08:44:52 -04:00
4bd55b56d1
Set our Hypothesis profile
2018-06-15 08:44:52 -04:00
0b6cb1cceb
Run the test suite unprivileged
2018-06-15 08:44:52 -04:00
7c1ac62c78
Factor duplication out of Debian configuration
2018-06-15 08:44:52 -04:00
d8d83478c8
Install Git first.
...
Hopefully this allows CircleCI to use the real Git client to check out
the source.
2018-06-15 08:44:52 -04:00
20cf504973
Remove these duplicated pyflakes checks
...
There is a dedicated `codechecks` environment. Use that if you want to
do code checks.
2018-06-15 08:44:52 -04:00
13bcb26129
Add current Debian stable
2018-06-15 08:44:52 -04:00
c16026bd88
Try running the test suite
2018-06-15 08:44:52 -04:00
659d661711
Get tox
2018-06-15 08:44:26 -04:00
ed3c7cba0c
Take a stab at an initial CircleCI configuration
2018-06-15 08:44:26 -04:00
c9c62fb076
Remove check-interfaces.py for spuriousness
...
It reports a bunch of problems with non-Tahoe-LAFS code and nothing with
Tahoe-LAFS code and therefore is not very useful.
2018-06-15 08:44:26 -04:00
36539eb11c
[debugging] Temporarily reduce the cost of testing
2018-06-15 08:44:24 -04:00
c43eacc3a9
clarify which party is vulnerable
2018-06-13 08:27:45 -04:00
Jean-Paul Calderone
b31b78e6cf
Merge pull request #501 from exarkun/1595.address-already-in-use-test_introducer-create_tub
...
Fix "Address already in use" errors from test_introducer on POSIX
2018-06-08 16:21:34 -04:00
1911b35499
Get the fcntl import up to the top as well
2018-06-08 13:15:19 -04:00