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

[DEBUG] Expected to pass #5

Closed
wants to merge 2 commits into from
Closed

Conversation

hebasto
Copy link
Owner

@hebasto hebasto commented Feb 5, 2024

No description provided.

@hebasto hebasto force-pushed the 240205-pass-expected branch from 805e7bb to 54df62b Compare February 5, 2024 09:22
@hebasto hebasto closed this Feb 5, 2024
hebasto pushed a commit that referenced this pull request Mar 24, 2024
this should hopefully resolve the recent build issue:
```
Step #5: warning: /workspace/out/libfuzzer-coverage-x86_64/dumps/parser.14845295624977050394_0.profraw: unsupported instrumentation profile format version
Step #5: error: no profile can be merged
Step #5: [2024-02-28 06:09:14,766 INFO] Finding shared libraries for targets (if any).
Step #5: [2024-02-28 06:09:14,775 INFO] Finished finding shared libraries for targets.
Step #5: error: parser: 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: Traceback (most recent call last):
Step #5:   File "/usr/local/bin/profraw_update.py", line 129, in <module>
Step #5:     sys.exit(main())
Step #5:   File "/usr/local/bin/profraw_update.py", line 120, in main
Step #5:     profraw_latest = upgrade(profraw_base, sect_prf_cnts, sect_prf_data)
Step #5:   File "/usr/local/bin/profraw_update.py", line 87, in upgrade
Step #5:     relativize_address(data, offset + 16, dataref, sect_prf_cnts, sect_prf_data)
Step #5:   File "/usr/local/bin/profraw_update.py", line 35, in relativize_address
Step #5:     value = struct.unpack('Q', data[offset:offset + 8])[0]
Step #5: struct.error: unpack requires a buffer of 8 bytes
```
@hebasto hebasto deleted the 240205-pass-expected branch August 28, 2024 13:36
hebasto pushed a commit that referenced this pull request Nov 18, 2024
## Description

This will make it easier to debug coverage failures that are not
reproducible locally.

The failure that I am trying to debug:
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=62231
-
https://oss-fuzz-build-logs.storage.googleapis.com/log-c420cf0c-f073-4c42-b75c-422971ef272e.txt

```
Step #5: Already have image (with digest): gcr.io/oss-fuzz-base/base-runner
Step #5: Entering python fuzzing
Step #5: Error happened getting coverage of fuzz_parse
Step #5: This is likely because Atheris did not exit gracefully
```

Similar log data is displayed in other blocks:

https://github.com/google/oss-fuzz/blob/f7165902492d5cff5ee23c018875395061a3bd2b/infra/base-images/base-runner/coverage#L101-L105


https://github.com/google/oss-fuzz/blob/f7165902492d5cff5ee23c018875395061a3bd2b/infra/base-images/base-runner/coverage#L149-L153


https://github.com/google/oss-fuzz/blob/f7165902492d5cff5ee23c018875395061a3bd2b/infra/base-images/base-runner/coverage#L206-L210


https://github.com/google/oss-fuzz/blob/f7165902492d5cff5ee23c018875395061a3bd2b/infra/base-images/base-runner/coverage#L255-L260

---

This PR is a continuation of
google#12405 with a renamed branch to
avoid trial-build errors:

```
ERROR: (gcloud.builds.submit) INVALID_ARGUMENT: invalid build: invalid build tag "testing-cm/display-coverage-log": must match format "^[\\w][\\w.-]{0,127}$"
```

Co-authored-by: Vitor Guidi <[email protected]>
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

Successfully merging this pull request may close these issues.

1 participant