If you update your git clone these Windows-specific extra errors and failures shouldn't be there anymore either.
Please report back if that isn't the case. Ramiro Morales @ramiromorales On Oct 30, 2013 10:12 AM, "Antony J" <[email protected]> wrote: > Sam, Marc, > > Thank you for your responses. Sorry I could not get back on this sooner. > > I ran the command “netstat -anob | findstr 8081” and found that the McAfee > framework service was listening in port 8081. > After killing the frameworkservice.exe, the errors went away. > > However, there still are 2 failures and the UnicodeDecodeError. > I am going to investigate them more, because the Django documentation > states that all tests should pass. > > Thank you for your help. I will get back with more info on the 2 failures > soon. > > Regards, > Antony > > > On Friday, October 25, 2013 10:05:30 AM UTC+5:30, Marc Tamlyn wrote: >> >> As this is about running the Django teat suite in order to try to write a >> patch it does belong on this mailing list. >> >> I don't have any concrete ideas what's wrong - but it does look like all >> your issues are related to running the LiveServer (selenium) tests. >> Something bound to a certain port already is likely the culprit, or some >> sort of version mismatch. Is your code running in a virtual python >> environment? I don't like selenium tests should run by default so of you >> set yourself up a virtualenv where selenium isn't installed but your Django >> checkout is then you shouldn't get these tests running. This may be the >> difference Sam was seeing. >> >> In any case, if the patch you were looking to write is not related to >> this area of the tests, I suggest you try just running the tests on the >> area you know works (and your new tests) or ignoring the failures. >> >> Alternatively, spin up a Linux VM ;) >> >> Marc >> On 25 Oct 2013 00:18, "Sam Lai" <[email protected]> wrote: >> >>> Do you have anything running on port 8081 (running netstat will tell >>> you)? >>> >>> I just ran Django's test suite on my machine (Windows 7, Python >>> 3.3.2), from the trunk cloned an hour ago, and it completed mostly >>> without an issue (there's a UnicodeDecodeError but that's likely >>> because it's printing a character to stdout that isn't supported by >>> the Windows console codepage). >>> >>> Can you move this discussion over to django-users (just post your >>> reply with the rest of the email chain over there)? I don't think it's >>> an issue with Django itself. >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/d90610d8-afd9-4958-a225-de21b1ee1e76%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAO7PdF-J6uc_bFUV0aCMLPjQgHHY25eMd-wu2PHUSVYoG%3D%3D6zQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
