Error while running mach mercurial-setup: need more than 2 values to unpack

RESOLVED WORKSFORME

Status

Firefox Build System
General
RESOLVED WORKSFORME
3 years ago
5 months ago

People

(Reporter: jlast, Unassigned)

Tracking

44 Branch

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:44.0) Gecko/20100101 Firefox/44.0
Build ID: 20151117004023

Steps to reproduce:

```
cd fx-team
./mach mercurial-setup
```


Actual results:

The mercurial queues command |hg qnew|, which creates new patches in your patch
queue does not set patch author information by default. Author information
should be included when uploading for review.
Would you like qnew to set patch author by default? [Y/n]

Configured qnew to set patch author by default.

Error running mach:

    ['mercurial-setup']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.

You should consider filing a bug for this issue.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

ValueError: need more than 2 values to unpack

  File "/Users/jlaster/src/_daily/2015/Jul-29/fx-team/tools/mercurial/mach_commands.py", line 68, in mercurial_setup
    result = wizard.run(map(os.path.expanduser, config_paths))
  File "/Users/jlaster/src/_daily/2015/Jul-29/fx-team/tools/mercurial/hgsetup/wizard.py", line 385, in run
    bzuser, bzpass, bzuserid, bzcookie = c.get_bugzilla_credentials()


Expected results:

mercurial-setup would finish
(Reporter)

Comment 1

3 years ago
My `fx-team` directory was actually quite stale.

Just re-downloaded source `hg clone http://hg.mozilla.org/mozilla-central` and ran `./mach mercurial-setup` successfully. I'm comfortable calling a mulligan and closing the ticket.

Updated

3 years ago
Component: Untriaged → Build Config
Product: Firefox → Core

Comment 2

3 years ago
This was almost certainly a bug in mozilla-central that was fixed a few months ago. Pulling and updating your mozilla-central clone would have likely fixed this.

Thank you for taking the time to report this bug. Glad to hear everything worked out all right.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME

Updated

5 months ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.