d77d8d09fc
Give the integration tests a little longer to finish.
2023-01-20 19:58:06 -05:00
db59eb12c0
Increase timeout.
2022-11-02 15:22:36 -04:00
Itamar Turner-Trauring
2787554a8b
Make sure CircleCI see progress output from subunitv2 reporter.
2020-09-04 12:05:42 -04:00
6eba1469f3
Back out subunit2junitxml exit status change from ticket:3336
...
I don't know why I included this change. It was certainly based on a faulty
assumption (that the tox command would exit with error if a test failed - it
won't). Apart from that, the motivation was the Python 3.6 ratchet job. The
test run was expected to fail but then the *ratchet* tool was in charge of
deciding if this indicated real failure or not. Failing at this point
prevented that logic from running. Now the ratchet is gone and we want CI to
turn red if anything fails.
2020-08-14 13:10:54 -04:00
Chad Whitacre
306df53012
Expose TAHOE_LAFS_TRIAL_ARGS to config
...
This allows for working around a bug in trial under Python 3 where
--reporter and --rterror collide.
2020-08-13 05:55:51 -04:00
0c2cf9f0c5
Don't fail if subunit2junitxml fails
2020-08-10 09:11:14 -04:00
a927ebbafa
what's up
2020-08-08 00:04:13 -04:00
7ba6daeed5
maybe get some more visibility into errors
2020-08-07 23:58:24 -04:00
23d7ffa369
Check for subunit2 output here
2020-08-07 23:56:13 -04:00
fbe12ba748
Take a shot at really timing out the PyPy job.
2019-08-13 15:57:29 -04:00
c80a28c543
this was vaguely helpful sort of not really
...
it's definitely extremely noisy though
2019-06-26 08:50:13 -04:00
c94578d3ad
"debugging"
2019-06-25 18:31:15 -04:00
a6b4bf55ba
try to make subunit2 processing allowed-to-fail too
2019-06-25 15:20:55 -04:00
67d76a0cc5
it's shell, dude
2019-06-25 15:11:20 -04:00
d5c21adb43
correct shell syntax
2019-06-25 15:02:34 -04:00
32a9f9be0f
Attempt to build an allowed failure mechanism
...
And use it to let the PyPy job fail.
2019-06-25 14:50:42 -04:00
3fdc0e1ca2
Bind the variables in both branches
2019-04-04 15:36:08 -04:00
11dd42a3fa
Remove one more sudo
...
Unnecessary and broken since we run this step as nobody now
2019-04-04 13:23:26 -04:00
4d15504e4a
Try avoiding some of the sudo'ing
2019-04-04 12:54:24 -04:00
904a175be4
Parameterize venv and source paths more
2019-04-04 12:07:32 -04:00
4def49ed54
ask subunitreporter for progress reporting
2019-03-25 13:20:04 -04:00
6ee727d67e
Avoid the artifact steps for integration tests
...
Integration tests produce none and trying to do these things breaks.
2019-01-24 16:04:26 -05:00
93881f34a7
consistent indentation
2018-07-10 15:43:30 -04:00
a1196fccdb
Prevent retrieval of source packages for test step
2018-07-10 15:23:16 -04:00
97bc77d96b
Go straight to a file with the subunit2 output.
...
It's just too hard otherwise.
2018-07-08 18:49:45 -04:00
869a6ad390
Go straight to subunit v2
2018-07-06 16:55:19 -04:00
4b98440e6a
Try harder to find the right output from Tox
2018-07-06 12:49:19 -04:00
fcf4480cbc
use TOX_JSON where it is appropriate
2018-07-06 12:06:46 -04:00
305d16af69
move path var definition higher up
2018-07-06 12:06:38 -04:00
da007ef21d
make sure nobody owns the artifacts directory
2018-07-06 12:06:21 -04:00
61f88c5359
nothing else will create it, I think
2018-07-06 11:32:19 -04:00
a23fc6b006
Make more intermediate state visible as artifacts
2018-07-06 11:28:52 -04:00
d074d52b48
Get junitxml uploaded as an artifact as well
2018-07-06 10:59:10 -04:00
a47877891b
Account for comma-separated tox env list
2018-07-06 10:47:28 -04:00
4e0863436f
Perhaps do a better job of generating junitxml
2018-07-06 10:15:52 -04:00
8300891ca2
Use a slightly better tox working directory
2018-07-06 10:15:32 -04:00
0ff1e100e1
Probably has to have this specific name
...
Or it won't be used
2018-07-05 19:47:11 -04:00
cead72ac58
Generate subunit1 and then junitxml test results
...
Successfully this time, perhaps.
2018-07-05 16:03:37 -04:00
16e4370630
Generate junitxml and give it to CircleCI
2018-07-05 14:19:23 -04:00
3837fd880c
make test args optional
2018-06-15 16:02:49 -04:00
9abb323d31
try passing positional args instead
2018-06-15 15:40:50 -04:00
fd26551c17
_not available_ in the build environment!
2018-06-15 15:17:32 -04:00
182d6aec94
necessary but not sufficient
2018-06-15 15:13:17 -04:00
00e3a04c7e
Factor steps out for use by machine executer
2018-06-15 14:21:33 -04:00
