Closed Bug 1071296 Opened 11 years ago Closed 11 years ago

Additional regressions found in hg 3.1.1 and pushlog html

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: gps)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1154] )

Attachments

(2 files, 1 obsolete file)

Splitting from bug 1070637, comment #9, as this in not a blocking issue: Justin Wood (:Callek) reports: > While [bug 1070637 comment 4] certainly did fix it for the reported issue, > there is a followup to do which regressed with this update: > > https://hg.mozilla.org/releases/mozilla-beta/ > pushloghtml?changeset=d179d51ba70c > > Note for example, that the specified cset landed on a branch (easy to verify > by clicking down to hg's main view), however pushloghtml doesn't actually > show that its a branch, while it used to. > > Your change basically makes the "old mercurial used repo.branchtags() -- > while in new thats invalid" not raise a real exception that breaks things. > > n-i to bkero and gps to figure out the best path forward here.
moving over correct n-i's
Flags: needinfo?(gps)
Flags: needinfo?(bkero)
Basically from that bugs Questions aimed at me, this was basically "pushes to branches that are not `default` used to show the branch in the UI of pushloghtml" where post-fix from that bug it only shows the tags applied on a cset. This is not a blocking thing imo, but is probably good hygene in terms of UI correctness, and is a regression from pre-webhead-upgrade. I admittedly don't know the code in question, nor do I plan to patch this myself. The mitigation in that bug is also entirely correct for a short-term fix (no traceback with pushlog data is far better than traceback without pushlog data at all.)
I think fix to pushlog to unbust compatibility with 3.1 (https://hg.mozilla.org/hgcustom/version-control-tools/rev/4fcea92fdba0) inadvertently broke display of branch info. I'll look into this.
Assignee: nobody → gps
Status: NEW → ASSIGNED
Flags: needinfo?(gps)
Flags: needinfo?(bkero)
Depends on: 1074491
I just pushed a fix (with tests!) to https://reviewboard-dev.allizom.org/r/179/. ReviewBoard is in a funky state right now, so it didn't notify this bug.
Justin: if you wouldn't mind taking a look at the diff and verifying things look sane. Basically, we should be inserting the branch name next to every commit on a branch that isn't "default."
Flags: needinfo?(bugspam.Callek)
Product: Release Engineering → Developer Services
(In reply to Gregory Szorc [:gps] from comment #5) > Justin: if you wouldn't mind taking a look at the diff and verifying things > look sane. > > Basically, we should be inserting the branch name next to every commit on a > branch that isn't "default." I always sigh when we drop old compat for merely the sake of dropping old compat. But since to my knowledge we're the only ones using this I won't block on that. I also don't understand our test code, so unsure if that is right or not. That said, assuming branchmap does what you claim I'm happy to stamp+ this.
Flags: needinfo?(bugspam.Callek)
Where did I drop compat in the proposed patch?
Flags: needinfo?(bugspam.Callek)
(In reply to Gregory Szorc [:gps] from comment #7) > Where did I drop compat in the proposed patch? "This patch breaks compatibility with Mercurial < 2.9. That should be fine." + the entire removal of `if repo.branchtags().get(branch) == ctx.node():` and similar sections
Flags: needinfo?(bugspam.Callek)
We don't care about 2.5.4 for web hosting any more. We'll soon have the SSH server running 3.1+ as well. The cost to continue to support 2.5.4 and similarly old releases is too high.
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/162]
Attached file MozReview Request: bz://1071296/gps (obsolete) —
Attachment #8514451 - Flags: review?(bkero)
/r/117 - pushlog: add better tests for HTML output /r/119 - pushlog: unbust branch display (bug 1071296) Pull down these commits: hg pull review -r 3f6af9007ed5f2d8268bd611bc335f162cc6a073
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/162] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1145] [kanban:engops:https://kanbanize.com/ctrl_board/6/162]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1145] [kanban:engops:https://kanbanize.com/ctrl_board/6/162] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1151] [kanban:engops:https://kanbanize.com/ctrl_board/6/162]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1151] [kanban:engops:https://kanbanize.com/ctrl_board/6/162] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1152] [kanban:engops:https://kanbanize.com/ctrl_board/6/162]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1152] [kanban:engops:https://kanbanize.com/ctrl_board/6/162] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1154] [kanban:engops:https://kanbanize.com/ctrl_board/6/162]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1154] [kanban:engops:https://kanbanize.com/ctrl_board/6/162] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/1154]
Attachment #8514451 - Flags: review?(mh+mozilla)
/r/117 - pushlog: add better tests for HTML output /r/119 - pushlog: unbust branch display (bug 1071296) Pull down these commits: hg pull review -r 24c191c5f1dca0482e07c30a477c896629999d98
https://reviewboard.mozilla.org/r/115/#review217 I'm working on some pushlog fixes to reduce excessive bandwidth usage. I'd like the new pushlog test infrastructure in place so I can adequately test things. Please review quickly.
https://reviewboard.mozilla.org/r/115/#review273 ::: testing/http-request.py (Diff revision 2) > +import httplib from __future__ import print_function ::: testing/http-request.py (Diff revision 2) > + help='Display only headers in this list') comma-separated list ::: testing/http-request.py (Diff revision 2) > +from optparse import OptionParser Can't you use argparse? Or does that need to run on python < 2.7? ::: testing/xmldump.py (Diff revision 2) > + if action == 'dump-element-with-class': You could use xpath, and you wouldn't need "actions" with random params. ::: hgext/pushlog-legacy/pushlog-feed.py (Diff revision 2) > - if hasattr(repo, 'branchtags'): > + if repo.branchmap().get(branch) == ctx.node(): For the record, since I looked up, branchmap() was added in mercurial 1.3. Mostly nits, but I'd like to read answers before clicking "ship ip".
Attachment #8514451 - Flags: review?(mh+mozilla)
Attachment #8514451 - Flags: review?(mh+mozilla)
/r/117 - pushlog: add better tests for HTML output /r/119 - pushlog: unbust branch display (bug 1071296) Pull down these commits: hg pull review -r 268205876768205a0337b3b2fce81be1f3e4a33a
Attachment #8514451 - Flags: review?(mh+mozilla) → review+
https://reviewboard.mozilla.org/r/115/#review529 This review would have been much easier if running tests in version-control-tools didn't insist on requiring docker even when trying to run tests that don't need it. Especially when on top of using docker, it downloads 1.2G+ of data (I can't tell exactly how much because that's when it failed because of insufficient disk space). ::: testing/http-request.py (Diff revisions 2 - 3) > - help='Display only headers in this list') > + help='Display only headers in this list. Values can be comma delimited.') s/can/must/
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Attachment #8514451 - Flags: review?(bkero) → review+
Attachment #8514451 - Attachment is obsolete: true
Attachment #8618375 - Flags: review+
Attachment #8618376 - Flags: review+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: