Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #76709
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Subject | Re: Test failure while building cpython |
| Date | 2014-08-21 02:18 -0400 |
| References | <09843563-B0FD-451B-BF66-0FB720CEC67A@ja.net> <lt3daq$k55$1@ger.gmane.org> <40FF81B6-4698-4AE6-9D4C-6549EEC33818@ja.net> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.13234.1408601931.18130.python-list@python.org> (permalink) |
On 8/20/2014 8:24 PM, Adam Bishop wrote: >> Or you can ignore it. > > It's a little tricky with mock, as failures during the test phase are fatal. Unfortunately, I have no idea what 'mock' is in this context. > Thanks for pointing me in the right direction. If you possibly can, also act on Ned's ending comment and either get the source for the later 3.3.5, with a few hundred bug fixes since 3.3.2, or for 3.4.0+, which will have the same fixes. Both are available from python.org. I did check that the same test is currently passing on the RHEL buildbots testing the repository version of 3.4.1+. -- Terry Jan Reedy
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Test failure while building cpython Terry Reedy <tjreedy@udel.edu> - 2014-08-21 02:18 -0400
csiph-web