Issue 63223 in oss-fuzz: abseil-cpp: Fuzzing build failure

[ClusterFuzz-External via monorail]

Status: New
Owner: ----
CC: absei...@googlegroups.com
Labels: Proj-abseil-cpp
Type: Build-Failure

New issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223

The last 3 builds for abseil-cpp have been failing.
Build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-31945193-b598-4e51-ac8e-78c15158e133.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.

[ClusterFuzz-External via monorail]

Comment #1 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c1

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.
Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-fbcf59c5-2a83-49fa-9c88-8383141d36b2.txt

[ClusterFuzz-External via monorail]

Comment #2 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c2

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-5e956e30-1e68-4307-b867-deda1df5d320.txt

[ClusterFuzz-External via monorail]

Comment #3 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c3

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-0b0e23ad-8d7a-4f6e-9a8c-c421d1636bc5.txt

[ClusterFuzz-External via monorail]

Comment #4 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c4

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-baf6ff43-5a67-4d6b-8f7f-ff95537d7094.txt

[ClusterFuzz-External via monorail]

Comment #5 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c5

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-1e5fa0c9-c494-46db-a192-96a35525b1af.txt

[Mark Barolak]

We looked at this a few weeks ago and came to the conclusion that the enclosed logs indicate an infrastructure problem rather than a fuzz test failure (see below).  We thought this would be a transient issue, but that now seems unlikely.

Unless we're mistaken, this is something that needs to be fixed in the OSS Fuzz configuration.  Would y'all mind taking a look at this?

Thanks,

-Mark

[1A [K [31m [1mERROR: [0m/root/.cache/bazel/_bazel_root/f8087e59fd95af1ae29e8fcb7ff1a3dc/external/com_google_absl/absl/base/BUILD.bazel:246:11: Compiling absl/base/internal/unscaledcycleclock.cc failed: undeclared inclusion(s) in rule '@com_google_absl//absl/base:base':
Step #3 - "compile-afl-address-x86_64": this rule is missing dependency declarations for the following files included by 'absl/base/internal/unscaledcycleclock.cc':
Step #3 - "compile-afl-address-x86_64":   'bazel-out/k8-fastbuild/bin/external/com_google_absl/absl/base/errno_saver.cppmap'
Step #3 - "compile-afl-address-x86_64": [32m[70 / 165] [0m 31 actions running
Step #3 - "compile-afl-address-x86_64":     Compiling absl/strings/internal/str_format/extension.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     Compiling absl/synchronization/internal/kernel_timeout.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     Compiling absl/base/internal/spinlock_wait.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     Compiling absl/strings/str_cat.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     Compiling absl/base/internal/sysinfo.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     Compiling absl/strings/internal/cord_internal.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     Compiling absl/base/internal/cycleclock.cc; 0s local
Step #3 - "compile-afl-address-x86_64":     @com_google_absl//absl/strings:str_format_internal; 0s local ...
Step #3 - "compile-afl-address-x86_64":
[1A [K
[1A [K
[1A [K
[1A [K
[1A [K
[1A [K
[1A [K
[1A [K
[1A [K [32mINFO: [0mElapsed time: 9.608s, Critical Path: 0.40s
Step #3 - "compile-afl-address-x86_64": [32m[101 / 165] [0m checking cached actions
Step #3 - "compile-afl-address-x86_64":
[1A [K [32mINFO: [0m101 processes: 101 internal.
Step #3 - "compile-afl-address-x86_64": [32m[101 / 165] [0m checking cached actions
Step #3 - "compile-afl-address-x86_64":
[1A [K [31m [1mFAILED: [0m Build did NOT complete successfully
Step #3 - "compile-afl-address-x86_64": [0m********************************************************************************
Step #3 - "compile-afl-address-x86_64": Failed to build.
Step #3 - "compile-afl-address-x86_64": To reproduce, run:
Step #3 - "compile-afl-address-x86_64": python infra/helper.py build_image abseil-cpp
Step #3 - "compile-afl-address-x86_64": python infra/helper.py build_fuzzers --sanitizer address --engine afl --architecture x86_64 abseil-cpp
Step #3 - "compile-afl-address-x86_64": ********************************************************************************
Finished Step #3 - "compile-afl-address-x86_64"
ERROR
ERROR: build step 3 "gcr.io/cloud-builders/docker" failed: step exited with non-zero status: 1

You received this message because you are subscribed to the Google Groups "Abseil.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to abseil-io+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/abseil-io/00000000000007e2b00609f395d1%40google.com.

[ClusterFuzz-External via monorail]

Comment #6 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c6

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-8f79eaca-a126-4496-880b-ab1e27862f90.txt

[ClusterFuzz-External via monorail]

Comment #7 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c7

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-ee264be6-54c8-4d48-a509-3925e536b9f2.txt

[jmeng… via monorail]

Comment #8 on issue 63223 by jmeng...@gmail.com: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c8

upgraded or change

[ClusterFuzz-External via monorail]

Comment #9 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c9

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-1dfdbb42-0023-40b8-8a38-dbffad2d9cc8.txt

[ClusterFuzz-External via monorail]

Comment #10 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c10

Friendly reminder that the build is still failing.
Please try to fix this failure to ensure that fuzzing remains productive.

Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-569ceacc-ee5e-4f7c-8cd9-daeb1591edd2.txt

[jun… via monorail]

Comment #11 on issue 63223 by jun...@google.com: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c11

https://github.com/google/oss-fuzz/commit/b8aa5dce48a446c2e679a2f75af06c759b2465fd should fix this...

[ClusterFuzz-External via monorail]

Updates:
Status: Verified

Comment #12 on issue 63223 by ClusterFuzz-External: abseil-cpp: Fuzzing build failure
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63223#c12

The latest build has succeeded, closing this issue.