Revision information still missing
Categories
(Tree Management :: Perfherder, defect, P1)
Tracking
(Not tracked)
People
(Reporter: igoldan, Assigned: igoldan)
References
Details
Attachments
(1 file)
Turns out that the reland of bug 1519323 didn't entirely fix the missing revision information section.
These links are reproducing the bug:
[1] https://treeherder.mozilla.org/perf.html#/compare?originalProject=mozilla-inbound&originalRevision=2c7c37b0ce9ca5f6745140b6551e9faa79e6c099&newProject=mozilla-inbound&newRevision=8686beefb44f25a78bb91bc6d5a9e5582f9ffa9a&framework=10
[2] https://treeherder.mozilla.org/perf.html#/compare?originalProject=autoland&originalRevision=edc9fc80bf25f7bfa6896db4274dfedf4e4bcc76&newProject=autoland&newRevision=c31d2c5695b185f5dab74513f911388ddcb23a46&framework=10
Comment 1•6 years ago
|
||
Ionut, have you made any progress on a patch? The revision information seems to be missing regardless of whether an originalRevision
is selected or not. I'll be starting on the compare view conversion in the next few days so it'd be good to have this fixed.
Assignee | ||
Comment 2•6 years ago
|
||
(In reply to Sarah Clements [:sclements] from comment #1)
Ionut, have you made any progress on a patch? The revision information seems to be missing regardless of whether an
originalRevision
is selected or not. I'll be starting on the compare view conversion in the next few days so it'd be good to have this fixed.
No, I haven't looked over this yet. I'm working on it now.
Assignee | ||
Comment 3•6 years ago
|
||
This is an awkward situation: I'm not able to reproduce the bug locally, while using yarn stage with latest master.
Assignee | ||
Comment 4•6 years ago
|
||
Sarah, are you having the same issue locally as I am?
Assignee | ||
Comment 5•6 years ago
|
||
I somehow managed to reproduce the bug on my machine. I've run yarn build + ./manage.py runserver 0:8000 while pointing to the production database. Basically, you need to build FE in production mode.
Resuming my debug now.
Comment 6•6 years ago
|
||
Assignee | ||
Comment 7•6 years ago
•
|
||
Looks like RevisionInformation component wasn't able to fetch the props from CompareResultsCtrl. They weren't defined in the react2angular's second argument. The docs confused me:
Note: If you defined propTypes on your component, they will be used to compute component's bindings, and you can omit the 2nd argument:
Comment 8•6 years ago
|
||
Yes, I was having the same issue where I wouldn't see the component on production but I would see it while doing local development using the prod server (yarn start
).
Comment 9•6 years ago
|
||
Landed in:
https://github.com/mozilla/treeherder/commit/5d052ed0d594628ea1ba9eebb5508c3a83ebc692
(the bot that leaves the commit message comment no longer works, so we need to add these manually)
Description
•