Chromium Code Reviews
|
|
Chromium Code Reviews
Issue
1703033002:
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the moment. (Closed)
Description[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
Committed: https://crrev.com/0e477e65ba0cff13a60b871aae3af0b95dee43d6
Cr-Commit-Position: refs/heads/master@{#375900}
Patch Set 1 #
Messages
Total messages: 30 (14 generated)
Description was changed from
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer failes for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
to
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
TBR=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
The CQ bit was checked by mmoroz@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1703033002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1703033002/1
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. Only full committers are accepted. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
The CQ bit was checked by kcc@chromium.org
lgtm 2) is the same as 1) -- hapens when libFuzzer is loading the corpus for too long. Pruning would be good, but for this target we need to figure our why it generates such a large corpus.
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1703033002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1703033002/1
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. Only full committers are accepted. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
On 2016/02/17 15:21:01, mmoroz wrote: I let myself to put 'TBR' and click Commit, because this fuzzer is currently wasting our computation resources.
The CQ bit was checked by mmoroz@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1703033002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1703033002/1
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. Only full committers are accepted. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
On 2016/02/17 15:25:07, commit-bot: I haz the power wrote: > No L-G-T-M from a valid reviewer yet. Only full committers are accepted. > Even if an L-G-T-M may have been provided, it was from a non-committer, > _not_ a full super star committer. > See http://www.chromium.org/getting-involved/become-a-committer > Note that this has nothing to do with OWNERS files. Oh, I'm not chromium committer, so TBR doesn't work for me.
Description was changed from
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
TBR=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
to
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
The CQ bit was checked by mmoroz@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1703033002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1703033002/1
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. Only full committers are accepted. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
mmoroz@chromium.org changed reviewers: + jochen@chromium.org
lgtm
The CQ bit was checked by mmoroz@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1703033002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1703033002/1
Message was sent while issue was closed.
Description was changed from
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
to
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
==========
to
==========
[libfuzzer] disable v8_script_parser_fuzzer, because it is useless at the
moment.
v8_script_parser_fuzzer fails for two reasons atm:
1) too large corpus -> need to implement corpus pruning
2) strange timeouts ("ALARM: working on the last Unit for 1455099776 seconds")
R=inferno@chromium.org, kcc@chromium.org
BUG=539572
Committed: https://crrev.com/0e477e65ba0cff13a60b871aae3af0b95dee43d6
Cr-Commit-Position: refs/heads/master@{#375900}
==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/0e477e65ba0cff13a60b871aae3af0b95dee43d6 Cr-Commit-Position: refs/heads/master@{#375900} |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
