Closed
Bug 1283638
Opened 8 years ago
Closed 8 years ago
lack verification process for addon signatures in tree
Categories
(Testing :: General, defect)
Testing
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1259528
People
(Reporter: kmoir, Unassigned)
References
Details
I didn't know what bucket to put this in so here it goes. We currently have a preference installed on beta that forces addons to be installed. This means tests fail if the addon is not signed. However, this preference is not flipped on other branches. So the tests don't fail if the addon had an invalid signature, is not signed or some other permutation of breakage. This means that on uplift from aurora to beta, any addons that were modified and not resigned correctly will cause failures. We need to have an automated process that verifies that the addons that are signed in tree to avoid a scramble to fix test failures at every uplift. The current approach is very expensive.
Reporter | ||
Comment 1•8 years ago
|
||
Also, see bug 1281578
Reporter | ||
Comment 5•8 years ago
|
||
:Ahal: is this a duplicate of bug 1259528 or are there other use cases that need to be addressed?
Flags: needinfo?(ahalberstadt)
Comment 6•8 years ago
|
||
Yeah, I think these two are dupes. Feel free to use whichever one you want, and if we use the other one I'll rename the reftest/mochitest to all test suites.
Flags: needinfo?(ahalberstadt)
Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•