Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oss-fuzz: opendal: Coverage build failure #4242

Closed
Xuanwo opened this issue Feb 22, 2024 · 3 comments
Closed

oss-fuzz: opendal: Coverage build failure #4242

Xuanwo opened this issue Feb 22, 2024 · 3 comments

Comments

@Xuanwo
Copy link
Member

Xuanwo commented Feb 22, 2024

Step #5: error: no profile can be merged
Step #5: [2024-02-21 06:32:25,054 INFO] Finding shared libraries for targets (if any).
Step #5: [2024-02-21 06:32:25,064 INFO] Finished finding shared libraries for targets.
Step #5: error: fuzz_writer_fs: Failed to load coverage: No such file or directory
Step #5: error: Could not load coverage information
Step #5: error: No such file or directory: Could not read profile data!
Step #5: error: /workspace/out/libfuzzer-coverage-x86_64/dumps/*.profdata: No such file or directory
Step #5: ********************************************************************************
Step #5: Code coverage report generation failed.
Step #5: To reproduce, run:
Step #5: python infra/helper.py build_image opendal
Step #5: python infra/helper.py build_fuzzers --sanitizer coverage opendal
Step #5: python infra/helper.py coverage opendal
Step #5: ********************************************************************************
Finished Step #5

https://oss-fuzz-build-logs.storage.googleapis.com/log-6e7c9e9a-7caa-46f5-b7a1-5320951ced5b.txt

cc @dqhl76, would you like to take a look? Thanks!

@dqhl76
Copy link
Member

dqhl76 commented Feb 22, 2024

I checked it yesterday and noticed that other Rust projects have encountered this issue as well: https://bugs.chromium.org/u/382749006/updates.
I also found that the problem has been reported in the OSS-Fuzz issues list: google/oss-fuzz#11626.

It seems we don't need to take any action on our side.

@Xuanwo
Copy link
Member Author

Xuanwo commented Feb 22, 2024

Understood. Thank you for the investigation.

@dqhl76
Copy link
Member

dqhl76 commented Mar 14, 2024

The latest build has succeeded, closing this issue.

@dqhl76 dqhl76 closed this as completed Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants