fuzz: Avoid timeout in bitdeque fuzz target #26012

1. 
   MarcoFalke commented at 1:40 PM on September 5, 2022: member

   I'd guess that any bug should be discoverable within 10 ops. However, 900 seems also better than no limit at all, which causes timeouts such as https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50892

2. fuzz: Avoid timeout in bitdeque fuzz target fa642286b8
3. 
   MarcoFalke commented at 1:44 PM on September 5, 2022: member

   Flame graph on my machine for the oss-fuzz timeout:

   

4. DrahtBot added the label Tests on Sep 5, 2022
5. fuzz: Remove no-op call to get() fa4ba04c15
6. fanquake requested review from sipa on Sep 22, 2022
7. fanquake requested review from sdaftuar on Sep 22, 2022
8. 
   sipa commented at 1:49 PM on September 22, 2022: member

   ACK fa4ba04c157b83b827f7541fa007710bd6211fe7

   No need for the fuzzing loop to continue forever.

9. fanquake merged this on Sep 22, 2022
10. fanquake closed this on Sep 22, 2022

    ---

11. 
    fanquake commented at 7:01 PM on September 22, 2022: member

    @MarcoFalke are you going to backport this?

12. sidhujag referenced this in commit ee9b22a362 on Sep 23, 2022
13. MarcoFalke referenced this in commit 2a56cc1f58 on Sep 23, 2022
14. MarcoFalke deleted the branch on Sep 23, 2022
15. 
    fanquake commented at 1:35 PM on September 23, 2022: member

    Backported to 24.x in #26160.

16. bitcoin locked this on Sep 23, 2023

Review Requested
sdaftuar