New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 918296 link

Starred by 2 users
Status: Untriaged
Owner:
xiaochu@chromium.org
Cc:
█ s...@chomium.org
metzman@chromium.org
█ ahass...@chomium.org
manojgupta@chromium.org
█ xiao...@chomium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in chromeos_update_engine_omaha_request_action_fuzzer

Project Member Reported by ClusterFuzz, Dec 30 
Detailed report: https://clusterfuzz.com/testcase?key=5698291232407552

Project: chromeos
Fuzzer: libFuzzer_chromeos_update_engine_omaha_request_action_fuzzer
Fuzz target binary: update_engine_omaha_request_action_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  chromeos_update_engine_omaha_request_action_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=3191849:3202633

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5698291232407552

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for instructions to reproduce this bug locally.
Project Member

Comment 1 by ClusterFuzz, Dec 30

Cc: ahass...@google.com senj@google.com xiaochu@google.com de...@google.com benchan@google.com
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 2 by ahass...@chromium.org, Jan 2

Cc: -de...@google.com -benchan@google.com -ahass...@google.com -xiaochu@google.com -senj@google.com ahass...@chomium.org xiao...@chomium.org s...@chomium.org
Owner: xiaochu@chromium.org
►

Sign in to add a comment