Closed
Description
The Tokio build on oss-fuzz has started failing with the following output:
Running fuzz_linked_list
Running fuzz_stream_map
Traceback (most recent call last):
File "/usr/local/bin/profraw_update.py", line 129, in <module>
sys.exit(main())
File "/usr/local/bin/profraw_update.py", line 120, in main
profraw_latest = upgrade(profraw_base, sect_prf_cnts, sect_prf_data)
File "/usr/local/bin/profraw_update.py", line 87, in upgrade
relativize_address(data, offset + 16, dataref, sect_prf_cnts, sect_prf_data)
File "/usr/local/bin/profraw_update.py", line 35, in relativize_address
value = struct.unpack('Q', data[offset:offset + 8])[0]
struct.error: unpack requires a buffer of 8 bytes
warning: /workspace/out/libfuzzer-coverage-x86_64/dumps/fuzz_stream_map.16753151517152022731_0.profraw: unsupported instrumentation profile format version
error: no profile can be merged
[2024-02-21 06:24:21,463 INFO] Finding shared libraries for targets (if any).
[2024-02-21 06:24:21,473 INFO] Finished finding shared libraries for targets.
error: fuzz_stream_map: Failed to load coverage: No such file or directory
error: Could not load coverage information
error: No such file or directory: Could not read profile data!
Traceback (most recent call last):
File "/usr/local/bin/profraw_update.py", line 129, in <module>
sys.exit(main())
File "/usr/local/bin/profraw_update.py", line 120, in main
profraw_latest = upgrade(profraw_base, sect_prf_cnts, sect_prf_data)
File "/usr/local/bin/profraw_update.py", line 87, in upgrade
relativize_address(data, offset + 16, dataref, sect_prf_cnts, sect_prf_data)
File "/usr/local/bin/profraw_update.py", line 35, in relativize_address
value = struct.unpack('Q', data[offset:offset + 8])[0]
struct.error: unpack requires a buffer of 8 bytes
warning: /workspace/out/libfuzzer-coverage-x86_64/dumps/fuzz_linked_list.14910788477734546202_0.profraw: unsupported instrumentation profile format version
error: no profile can be merged
This error seems very similar to #6268, and the latest Rust release has the following in its changelog:
Let me know if the problem is on our end, or if there's anything I can do to help.
For more information, see the chromium bug for the build failure.