Discussion:
Re: Issue 587523 in chromium: Media Pipeline Integration Apptests fail in debug
(too old to reply)
c***@googlecode.com
2016-02-17 20:51:43 UTC
Permalink
Raw Message
Comment #14 on issue 587523 by ***@chromium.org: Media Pipeline Integration
Apptests fail in debug
https://code.google.com/p/chromium/issues/detail?id=587523

wait, ignore my last comment, that was an old build. a build dependency is
missing as Ken mentioned
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 21:05:44 UTC
Permalink
Raw Message
Comment #15 on issue 587523 by ***@chromium.org: Media Pipeline
Integration Apptests fail in debug
https://code.google.com/p/chromium/issues/detail?id=587523

I'll take a look, fix component build and possible crash. Thanks for the
help and info!
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-17 22:02:43 UTC
Permalink
Raw Message
Comment #16 on issue 587523 by ***@chromium.org: Media Pipeline Integration
Apptests fail in debug
https://code.google.com/p/chromium/issues/detail?id=587523

I've added the component build change to
https://codereview.chromium.org/1705883002/ as it was blocking it
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-18 06:33:54 UTC
Permalink
Raw Message
Comment #18 on issue 587523 by ***@chromium.org: Media Pipeline
Integration Apptests fail in debug
https://code.google.com/p/chromium/issues/detail?id=587523

BTW, there are 52 tests in total and MediaSource_FillUp_Buffer is the only
one that fails on my local build.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
c***@googlecode.com
2016-02-18 10:09:53 UTC
Permalink
Raw Message
Updates:
Cc: ***@chromium.org

Comment #19 on issue 587523 by ***@chromium.org: Media Pipeline
Integration Apptests fail in debug
https://code.google.com/p/chromium/issues/detail?id=587523

+wolenetz for insights.

Ken: Did you actually see a crash? How did you find/debug it? I tried with
gdb but I am really not good at it when using mojo_runner.

I played with this a bit more and here are observations and questions. It
seems this issue is timing related.

In debug build MediaSource_FillUp_Buffer test always fails.

In a release build, this test passes, but I can easily make it fail by
simply add more logs in the destructor of SourceBufferRange (to make it run
slower?). If I add a lot of log the test always fails. I tweaked the number
of logs a bit so I am at a point where the test is flaky :)

One thing I noticed is that when the test fails, I always see the following
at the bottom of the log:

[ERROR:child_process.cc(223)] Connection error to the shell.

Maybe it's actually crashing, then connection is lost. Then the crash is
timing related. I'll dig more on this.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs

---
You received this message because you are subscribed to the Google Groups "Chromium-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
Loading...