Closed Bug 1309294 Opened 8 years ago Closed 8 years ago

Duplicate performance signatures being generated after heroku migration

Categories

(Tree Management :: Perfherder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

References

Details

Attachments

(2 files)

We're seeing a ton of duplicated performance signatures being generated after the heroku migration. I believe this is due to heroku's python not being deterministic about what running json.dumps on a dict will generate, which perfherder's signature generation algorithm depends on. An easy solution would be to pass sort_keys to json.dumps (this is what should have been done originally), but since we're here and have to sort out so much messed up data anyway, let's go ahead and just remove the code that incorporates the child signatures into the calculation, which is what required json.dumps (and thus caused this bug).
It's worth noting that SCL3 was stuck on Python 2.7.10 (too much of a hassle to try and update it, since the rsynced venv used system Python ...) whereas Heroku is using Python 2.7.11 (I'm going to update that to 2.7.12 shortly), so presumably either this or different OS or bug 1292720 is responsible for the ordering changing. (iirc Python dicts are not expected to be deterministic, and thus json.dumps() output can vary unless sorted)
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/b2098db6ad63ce31288c2d9c1a4f07c63dd41828 Bug 1309294 - Fixes to signature calculation for remove signatures script (#1924)
Blocks: 1310386
Ok, data on production should be ok again. Unfortunately signature hashes changed so old graph and compare subtest links are now invalid. :( Filed bug 1310386 to fix things up so this doesn't happen again.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: