testPartnerUploadToNonReleaseOrProposedPocket disabled (was incorrectly passing / failing if run on own)

[Robert Collins]

testPartnerUploadToNonReleaseOrProposedPocket has been compromised by bug 640007 - it only passes because the immediate oops-generating test before it generates a suitable oops. It does not generate an oops itself.

 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testMoveUpload
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testOopsCreation
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPGPSignatureNotPreserved
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPackageUploadPermissions
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPackagesetUploadPermissions
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPartnerArchiveMissingForPartnerUploadFails
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPartnerReusingOrigFromPartner
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPartnerUpload
 lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testPartnerUploadToNonReleaseOrProposedPocket

is the order of tests - one of those will cause it.

To reproduce:
rm -rf /var/tmp/lperr.test/*
bin/test -vvt testPartnerUploadToNonReleaseOrProposedPocket

And you'll trigger an error when None.write (in trunk today) is called, or
AttributeError: 'NoneType' object has no attribute 'value'

Once my oops extraction branch (where I noticed this) lands.

For now, I am disabling the test as it doesn't actually work and does cause problems in parallel test mode.