And the final exception (lp.services.gpg.interfaces.GPGVerificationError) is visible to the "user/developer/test runner" as :
[u"GPG verification of /tmp/tmpX1xckK/incoming/bar_1.0-1/bar_1.0-1_source.changes failed: (7, 8, u'Bad signature')"]
Not sure how we get from here to the exception stack in the Bug assessment.
I'm expecting the added test to fail with the stack in the bug 1910403 but it fails with the following stack:
getVerifiedSign ature, handler.py:253 atureResilient, handler.py:147 collect_ errors, nascentupload. py:434 reject_ on_error, nascentupload. py:445 py:145 .py:538 .py:368 essor.py: 337 utMaintainerEma il, test_uploadproc essor.py: 553 result, runtest.py:108
getVerifiedSign
_verifySignature, dscfile.py:190
parse, dscfile.py:153
parseChanges, changesfile.py:109
run_and_
run_and_
process, nascentupload.
_processUpload, uploadprocessor
processChangesFile, uploadprocessor
processUpload, test_uploadproc
testUploadWitho
_run_test_method, testcase.py:723
_run_user, runtest.py:191
_run_core, runtest.py:144
_run_prepared_
_run_one, runtest.py:94
run, runtest.py:80
run, testcase.py:675
__call__, case.py:673
run_tests, runner.py:396
run_layer, runner.py:474
run_tests, runner.py:293
run, runner.py:191
main, test.py:275
<module>, test:8
And the final exception (lp.services. gpg.interfaces. GPGVerification Error) is visible to the "user/developer /test runner" as : incoming/ bar_1.0- 1/bar_1. 0-1_source. changes failed: (7, 8, u'Bad signature')"]
[u"GPG verification of /tmp/tmpX1xckK/
Not sure how we get from here to the exception stack in the Bug assessment.