Closed Bug 1380077 Opened 8 years ago Closed 8 years ago

Verify that the win32 tc signature formats match those from BB builds

Categories

(Firefox Build System :: Task Configuration, task)

Product:
Firefox Build System
Component:
Task Configuration
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: catlee, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #1357136 +++
After installing hal's verify-sigs https://github.com/hwine/verify-sigs , the recursively-exploded l10n installer gave me all the same signature info for all exe and dll files between buildbot and tc.
win32 stub installers and contents look to have the same sig info
I exploded the mars and got this diff: (bb on the left, tc on the right) I'm hoping it's because I'm comparing varying m-c / date revisions, so someone could have added/removed files. 295,296d294 < ./browser/omni/chrome/browser/content/browser/preferences/in-content-new/advanced.js < ./browser/omni/chrome/browser/content/browser/preferences/in-content-new/applications.js 302a301 > ./browser/omni/chrome/browser/content/browser/preferences/in-content-new/search.js 3206a3206,3208 > ./omni/chrome/toolkit/content/payments/paymentRequest.css > ./omni/chrome/toolkit/content/payments/paymentRequest.js > ./omni/chrome/toolkit/content/payments/paymentRequest.xhtml 3328d3329 < ./omni/chrome/toolkit/skin/classic/global/icons/Search-glass.png
recursive complete mar sig checks look good.
Any other concerns? Or is this closable?
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: TaskCluster → Firefox Build System
You need to log in before you can comment on or make changes to this bug.