upload integration test is not using a unique name

Bug #1595319 reported by Leo Arias
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
Low
Leo Arias

Bug Description

If the upload test doesn't use a unique name, then it can't be executed by a user that we don't control and have previously set up.

I tried to do this in a previous branch but left a bug which makes it use the old snap name.

[Impact]

 * For users, none.

 * For developers, this forces us to share the staging test account password in order to run the tests.

[Test Case]

 * Run: <email address hidden> TEST_USER_PASSWORD=Hola123* ./runtests.sh integration test_store_upload.py
   (replacing the credentials with some staging user with the developer agreement signed.

[Regression Potential]

 * This could make the staging store tests fail.

Leo Arias (elopio)
Changed in snapcraft:
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Leo Arias (elopio)
milestone: none → 2.12
Revision history for this message
Leo Arias (elopio) wrote :
Changed in snapcraft:
status: In Progress → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Leo, or anyone else affected,

Accepted snapcraft into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snapcraft/2.12 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Leo Arias (elopio) wrote :

There is nothing to verify in xenial-proposed. I'm marking this as done.

Thanks Steve!

tags: added: verification-done
removed: verification-needed
Changed in snapcraft:
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Mathew Hodson (mhodson)
no longer affects: Ubuntu Xenial
no longer affects: Ubuntu Yakkety
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.