Unflake cctest/test-cpu-profiler/JsNativeJsRuntimeJsSample on Win32 Debug

Unflake cctest/test-cpu-profiler/JsNativeJsRuntimeJsSample on Win32 Debug

Profiler is now started from JavaScript. Since we always capture stack trace when starting profiler there should always be at least one expected sample in the profile.

Also changed ProfilerEventsProcessor::AddCurrentStack to make sure it call TickSample::Init to instead of custom initialization code.

BUG=v8:2920
R=jkummerow@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=17140

[yurys, 2013-10-08 16:43:44]

ping

[Jakob Kummerow, 2013-10-10 08:52:40]

LGTM.

If this successfully eliminates flakiness, the next step is to update
test/cctest/cctest.status, but we can leave that for now and watch the bots for
a few days.

[yurys, 2013-10-10 13:03:51]

Committed patchset #1 manually as r17140 (presubmit successful).

[yurys, 2013-10-10 13:06:23]

On 2013/10/10 08:52:40, Jakob wrote:
> LGTM.
> 
> If this successfully eliminates flakiness, the next step is to update
> test/cctest/cctest.status, but we can leave that for now and watch the bots
for
> a few days.

Let's watch the tree for a few days and I'll remove custom expectations after
that.