add mojo into Dr.Memory test build target

add mojo into Dr.Memory test build target

R=bruening@chromium.org, yzshen@chromium.org
BUG=NONE
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=268897

[yzshen1, 2014-05-07 16:34:59]

https://codereview.chromium.org/274643002/diff/1/build/all.gyp
File build/all.gyp (right):

https://codereview.chromium.org/274643002/diff/1/build/all.gyp#newcode1081
build/all.gyp:1081: '../mojo/mojo.gyp:mojo',
- It seems this list is ordered alphabetically.

- Some of the mojo targets won't be needed, is that okay?
I am fine building them, but not sure whether that will slow down the build.

[zhaoqin, 2014-05-07 16:53:14]

https://codereview.chromium.org/274643002/diff/1/build/all.gyp
File build/all.gyp (right):

https://codereview.chromium.org/274643002/diff/1/build/all.gyp#newcode1081
build/all.gyp:1081: '../mojo/mojo.gyp:mojo',
On 2014/05/07 16:34:59, yzshen1 wrote:
> - It seems this list is ordered alphabetically.
DONE

> 
> - Some of the mojo targets won't be needed, is that okay?
> I am fine building them, but not sure whether that will slow down the build.

most mojo files should have been built for other tests like content_browertests,
so it should be fine to build mojo all directly, which probably just add a few
test targets.

[yzshen1, 2014-05-07 16:54:34]

lgtm

[zhaoqin, 2014-05-07 17:00:07]

The CQ bit was checked by zhaoqin@google.com

[commit-bot: I haz the power, 2014-05-07 17:03:22]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/zhaoqin@google.com/274643002/20001

[commit-bot: I haz the power, 2014-05-07 19:33:11]

Change committed as 268897