Closed
Bug 1400652
Opened 7 years ago
Closed 5 years ago
[tryselect] mach try fuzzy hangs in Windows Powershell due to More Utility
Categories
(Developer Infrastructure :: Try, defect, P3)
Developer Infrastructure
Try
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1520309
People
(Reporter: mak, Unassigned)
References
Details
When I use mach try fuzzy on Win10, it apparently hangs after trying to remove its own changeset, thus I have to CTRL+C, uncommit the config file and hg purge.
Comment 1•7 years ago
|
||
Is this reproducible? What version of Mercurial? Using MQ? Evolve? Is your version-control-tools repo up to date? (Run `mach mercurial-setup --update-only`) If nothing works, please add `[ui] traceback = true` to your hgrc file (`hg config -e`) and report the traceback that results when you kill the "hung" process.
Flags: needinfo?(mak77)
Updated•7 years ago
|
Blocks: require-mach-try
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to Gregory Szorc [:gps] from comment #1) > Is this reproducible? Every time for me. > What version of Mercurial? 4.3.1 > Using MQ? Evolve? Evolve > Is your version-control-tools repo up to date? (Run `mach mercurial-setup > --update-only`) yes, updated weekly > If nothing works, please add `[ui] traceback = true` to your hgrc file (`hg > config -e`) and report the traceback that results when you kill the "hung" > process. I will do as soon as I can use it again, now I'm getting this error Exception: extra parameters: release_history File "d:\src\tools/tryselect/mach_commands.py", line 143, in try_fuzzy return run_fuzzy_try(**kwargs) File "d:\src\tools\tryselect\selectors\fuzzy.py", line 214, in run_fuzzy_try all_tasks = generate_tasks(parameters, full) File "d:\src\tools\tryselect\tasks.py", line 49, in generate_tasks params.check() File "d:\src\taskcluster\taskgraph\parameters.py", line 56, in check raise Exception("; ".join(msg))
Reporter | ||
Comment 3•7 years ago
|
||
So this is the complete output after I confirm a try fuzzy: Creating temporary commit for remote... ? 0 problems (0 errors, 0 warnings) [0;32;1mA [0m[0;32;1mtry_task_config.json[0m pushing to ssh://hg.mozilla.org/try searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 2 changesets with 7 changes to 7 files (+1 heads) remote: recorded push in pushlog remote: remote: View your changes here: remote: https://hg.mozilla.org/try/rev/3984e273d0469a2870798c4f4677f2682e884655 remote: https://hg.mozilla.org/try/rev/a3f02df4583346380c898fa85eba897be0e6dfe5 remote: remote: Follow the progress of your build on Treeherder: remote: https://treeherder.mozilla.org/#/jobs?repo=try&revision=a3f02df4583346380c898fa85eba897be0e6dfe5 remote: recorded changegroup in replication log in 0.023s push complete temporary commit removed, repository restored ...Then it just stops here... If I CTRL+C to terminate, it doesn't print anything, even with traceback enabled. Then: $ hg status A try_task_config.json Anything else I can provide?
Flags: needinfo?(mak77) → needinfo?(gps)
Comment 4•7 years ago
|
||
Sometimes I've seen MozillaBuild's terminal just kind of "hang". If you press ENTER things get restored. I wonder if that's happening here? If it is truly Mercurial spinning, adding --profile to any `hg` command will print where it is spending the time. I should be able to interpret that output into a meaningful bug report.
Flags: needinfo?(gps) → needinfo?(mak77)
Reporter | ||
Comment 5•7 years ago
|
||
(In reply to Gregory Szorc [:gps] from comment #4) > Sometimes I've seen MozillaBuild's terminal just kind of "hang". If you > press ENTER things get restored. I wonder if that's happening here? No, I know well that "bug" (it's a feature of the powershell), it's not this case.
Reporter | ||
Comment 6•7 years ago
|
||
Ok, I have found the culprit, even if it's puzzling. When .mach try fuzzy runs, I see a "More Utility" process in task manager, killing that process lets it proceed properly. There no other key that makes it proceed apart from ctrl+c that leaves the try config file committed. Though killing "More Utility" lets the command complete correctly.
Flags: needinfo?(mak77)
Comment 7•7 years ago
|
||
Huh, that looks like a Windows system utility. No idea what it's for though.
Reporter | ||
Comment 8•7 years ago
|
||
I suspect the PowerShell has some kind of automatic pager, and this may be part of it.
Reporter | ||
Updated•7 years ago
|
Summary: mach try fuzzy doesn't cleanup after itself on Windows → mach try fuzzy hangs in Windows Powershell due to More Utility
Comment 9•6 years ago
|
||
Jmaher seems to be hitting this as well, though he isn't using PowerShell and doesn't seem to see the 'More Utility' in his task manager.
Updated•6 years ago
|
Component: Task Configuration → General
Product: Taskcluster → Testing
Summary: mach try fuzzy hangs in Windows Powershell due to More Utility → [tryselect] mach try fuzzy hangs in Windows Powershell due to More Utility
Updated•6 years ago
|
Priority: -- → P3
Updated•6 years ago
|
Component: General → Try
Product: Testing → Firefox Build System
Comment 11•5 years ago
|
||
Duping this bug as the other one has a more succinct description without all the false leads at the beginning.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•