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

Revert "Add lzo" #1900

Merged
merged 1 commit into from
Oct 23, 2018
Merged

Revert "Add lzo" #1900

merged 1 commit into from
Oct 23, 2018

Conversation

inferno-chromium
Copy link
Collaborator

Reverts #1862

@inferno-chromium
Copy link
Collaborator Author

Fails

Step #5: INFO: performing bad build checks for /workspace/out/address/lzo_compress_target.
Step #5: INFO: performing bad build checks for /workspace/out/address/lzo_decompress_target.
Step #5: Broken fuzz targets (1):
Step #5: lzo_decompress_target:
Step #5: BAD BUILD: /workspace/out/address/lzo_decompress_target does not seem to have coverage instrumentation.
Step #5: BAD BUILD: /workspace/out/address/lzo_decompress_target seems to have either startup crash or exit:
Step #5: INFO: Seed: 877411823
Step #5: INFO: Loaded 1 modules (478 inline 8-bit counters): 478 [0x8c8190, 0x8c836e),
Step #5: INFO: Loaded 1 PC tables (478 PCs): 478 [0x66fea0,0x671c80),
Step #5: INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
Step #5: INFO: A corpus is not provided, starting from an empty corpus
Step #5: #2 INITED lim: 4 exec/s: 0 rss: 27Mb
Step #5: ERROR: no interesting inputs were found. Is the code instrumented for coverage? Exiting.
Step #5: ERROR: 50% of fuzz targets seem to be broken. See the list above for a detailed information.
Finished Step #5

@bshastry - please take a look, till then reverting the cl.

@inferno-chromium inferno-chromium merged commit cf78fed into master Oct 23, 2018
bshastry added a commit to bshastry/oss-fuzz that referenced this pull request Oct 25, 2018
inferno-chromium pushed a commit that referenced this pull request Oct 25, 2018
@Dor1s Dor1s deleted the revert-1862-add-lzo branch February 1, 2019 18:34
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