Issue metadata
Sign in to add a comment
|
media_pipeline_integration_fuzzer is hitting the default Run() timeout |
||||||||||||||||||||||||
Issue descriptionThis fuzzer normally runs with a 25s timeout specified on the command-line, but for some reason is still managing to hit the default Run() timeout (set to TestTimeouts::action_max_timeout(), which is usually 30s or 45s) that was added in issue 918724 . This resulted in several fuzzer-reported issues being incorrectly closed-out as Fixed (see issues 917024 , 763620, 807515 and 908222).
,
Jan 9
,
Jan 9
,
Jan 9
,
Jan 9
Not clear why the default Run() timeout is firing in this case; the build Linux+Debug+ASAN, so the action_max_timeout() is 90s, whereas dalecurtis@ observes that the timeout is being hit after only ~2s in fuzzer runs.
,
Jan 9
Looks like we were actually just crashing the fuzzer fixture at startup, due to issue 920111 . |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by w...@chromium.org
, Jan 9