New issue
Advanced search Search tips

Issue 661692 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Make it possible to run mus in synchronous mode

Project Member Reported by sky@chromium.org, Nov 2 2016

Issue description

It would be nice if we had the ability to run tests in a synchronous mode. That is, each call to mus runs a nested message loop until acked. This way we could easily tell if there is a problem, rather than possibly seeing a problem depending upon threading. Additionally I suspect for debugging a sync model would prove very helpful.

This should be possible with a stub implementation of a WindowTree that forwards the call to the real WindowTree and runs a nested message loop until the ack is received. I suspect this would entail some changes to WindowTreeClient to make sure it can deal with sync responses.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Nov 3 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Internals>MUS
Components: -Internals>MUS Internals>Services>WindowService
Labels: -Proj-Mustash-Mus Proj-Mustash
Migrating Proj-Mustash-Mus to components Internals>Services>WindowService and Internals>Services>Ash

Status: WontFix (was: Untriaged)
We kinda have this with FooAsyncWaiter in mojo, and kinda have this with WS2 + SingleProcessMash.

Sign in to add a comment