moz-phab hanging/spinning while performing long running actions
Categories
(Conduit :: moz-phab, defect, P2)
Tracking
(Not tracked)
People
(Reporter: ruchikag826, Assigned: zalun)
References
Details
(Keywords: conduit-triaged)
Attachments
(3 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
After changing directory to <mozilla-central>, I ran the following command to submit my patch:
/Users/ruchikagosain/Desktop/review/moz-phab submit
Actual results:
The terminal hung and it shows "looking for commits" for as long as terminal runs.
At last, I had to kill the process.
Even after <self-update> command, the above process repeated.
Expected results:
The patch should have been submitted for review via moz-phab.
Reporter | ||
Updated•6 years ago
|
Please re-run using the following command and attach the output:
DEBUG=1 /Users/ruchikagosain/Desktop/review/moz-phab submit
As this will generate a lot of output copy and pasting the text into an attachment would be better/easier than attaching a screenshot.
we've had a few more reports of this spinning, including zalun hitting this in his dev environment.
appears to be related to the progress spinner.
Assignee | ||
Comment 3•6 years ago
|
||
@njn Do you remember the message the spinner displayed when stuck?
![]() |
||
Comment 4•6 years ago
|
||
The last line of the terminal output said Updating D39133..
with the text spinner at the end of the line.
Assignee | ||
Comment 5•6 years ago
|
||
Thanks, so it's really random - I've asked as in my local environment it was constantly hanging on one command, but it was just a coincident.
I'm removing the spinner for now.
Assignee | ||
Comment 6•6 years ago
|
||
Comment 7•6 years ago
|
||
Got at far as "Submitting 1 commit for review:\n Loading commits /" and spinning.
Not using much cpu. No network connections.
^C doesn't interrupt. ^\ does.
Assignee | ||
Comment 8•6 years ago
|
||
I've created a release without the spinner. Please report if this would happen again.
I'll continue to work on fixing it properly.
Assignee | ||
Comment 10•6 years ago
|
||
I've switched it to check if the problem solved itself after the move to Python3.
I've run it a few hundred times in the suite environment. No hangs (I remember it was hanging about 1-3% of the time)
Do you think we can just switch it on?
Assignee | ||
Comment 11•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Description
•