Jean-Paul Calderone 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
..
config.yml	Update the CircleCI configuration to get the reporter working for py36	2020-08-14 11:24:42 -04:00
create-virtualenv.sh	Fix wording of comment	2020-01-13 20:12:43 -05:00
Dockerfile.centos	FROM creates a new build stage which discards all prior ARGs	2020-08-03 17:02:14 -04:00
Dockerfile.debian	FROM creates a new build stage which discards all prior ARGs	2020-08-03 17:02:14 -04:00
Dockerfile.fedora	FROM creates a new build stage which discards all prior ARGs	2020-08-03 17:02:14 -04:00
Dockerfile.pypy	Use 2.7-buster Docker image for pypy	2020-04-14 16:14:07 -04:00
Dockerfile.ubuntu	strace not used by anything now	2020-08-11 18:33:01 -04:00
fix-permissions.sh	Fix the permissions ... twice. Thanks, COPY.	2019-04-06 10:00:19 -04:00
populate-wheelhouse.sh	try doing the pip wheel with the right LANG	2020-08-03 17:02:15 -04:00
prepare-image.sh	try telling the virtualenv to use pypy	2019-06-25 18:51:11 -04:00
run-build-locally.sh	Factor steps out for use by machine executer	2018-06-15 14:21:33 -04:00
run-tests.sh	Back out subunit2junitxml exit status change from ticket:3336	2020-08-14 13:10:54 -04:00
secret-env-cipher	Re-generate with a new key because I leaked the old one	2019-04-03 14:18:19 -04:00
setup-virtualenv.sh	this was vaguely helpful sort of not really	2019-06-26 08:50:13 -04:00