qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fwd] Issue 26558 in oss-fuzz: qemu: Fuzzing build failure


From: Alexander Bulekov
Subject: Re: [Fwd] Issue 26558 in oss-fuzz: qemu: Fuzzing build failure
Date: Wed, 21 Oct 2020 13:13:55 -0400

On 201021 1002, Alexander Bulekov wrote:
> oops.. looks like we need to install ninja on the oss-fuzz build docker.
> I'll send a PR to oss-fuzz.
> 
> -Alex

PR: https://github.com/google/oss-fuzz/pull/4557

> 
> ----- Forwarded message from ClusterFuzz-External via monorail 
> <monorail+v2.382749006@chromium.org> -----
> 
> Date: Wed, 21 Oct 2020 03:16:20 -0700
> From: ClusterFuzz-External via monorail <monorail+v2.382749006@chromium.org>
> To: alxndr@bu.edu
> Subject: Issue 26558 in oss-fuzz: qemu: Fuzzing build failure
> 
> Status: New
> Owner: ----
> CC: b...@redhat.com, stefa...@redhat.com, alx...@bu.edu, pbonz...@redhat.com, 
> darre...@oracle.com 
> Labels: Proj-qemu
> Type: Build-Failure
> 
> New issue 26558 by ClusterFuzz-External: qemu: Fuzzing build failure
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26558
> 
> The last 2 builds for qemu have been failing.
> Build log: 
> https://oss-fuzz-build-logs.storage.googleapis.com/log-fd076577-292c-45f5-8c56-b5993850d2bb.txt
> Build type: fuzzing
> 
> To reproduce locally, please see: 
> https://google.github.io/oss-fuzz/advanced-topics/reproducing#reproducing-build-failures
> 
> This bug tracker is not being monitored by OSS-Fuzz team. If you have any 
> questions, please create an issue at 
> https://github.com/google/oss-fuzz/issues/new.
> 
> **This bug will be automatically closed within a day once it is fixed.**
> 
> -- 
> You received this message because:
>   1. You were specifically CC'd on the issue
> 
> You may adjust your notification preferences at:
> https://bugs.chromium.org/hosting/settings
> 
> Reply to this email to add a comment.
> 
> ----- End forwarded message -----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]