Phabricator doesn't get notified of new tasks for revision
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 52
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 54
Description
It can be seen in D187545 that there were no tasks associated with this revision.
Looking other the logs there was a local mercurial error even if the push was successful on the server side since the tasks for this differential were created, https://treeherder.mozilla.org/jobs?repo=try&revision=9086153f853187d4f43d03b5847042b879d0c6c7
If mercurial is killed libmozevent doesn't capture the exception accordingly in order to also signal Phabricator that something happened. In this case this is a false positive issue since, as mentioned above the pushed was successful on the server.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing libmozevent's Mercurial error handling and how it signals Phabricator after a push. Reproduce or inspect the killed-Mercurial case described in the issue, then verify that a successful server-side push still notifies Phabricator without reporting a false failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100