Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 8257] Buildbot crash output: fuzz-2013-01-24-29553.pcap

[bugzilla-daemon@xxxxxxxxxxxxx]

Comment # 5 on bug 8257 from Bugzilla administrator

(In reply to comment #4)
> The most recent fuzz failure on trunk ends with the following:
> 
>     /home/wireshark/menagerie/menagerie/7561-paging1.pcap: 
> ls: cannot access
> /fuzz/buildbot/clangcodeanalysis/menagerie-fuzz/fuzz-*.pcap: No such file or
> directory
> CPU time limit exceeded (core dumped)
> program finished with exit code 152
> elapsedTime=48297.289086
> 
> So it looks like we're somehow still hitting the mount-point issue as well...
> 
> http://buildbot.wireshark.org/trunk/builders/Clang-Code-Analysis/builds/1765/
> steps/fuzz-menagerie/logs/stdio

After further investigation it looks like the mount point is OK. I think the
problem is that we're exceeding our self-imposed CPU time limit:

    /home/wireshark/menagerie/menagerie/701-data_sm.pcap:  OK
%CPU     TIME
 4.0 00:14:53
    /home/wireshark/menagerie/menagerie/7012-call.pcap:  OK
%CPU     TIME
 4.0 00:14:53
    /home/wireshark/menagerie/menagerie/7013-call_sdp16k.pcap:  OK
%CPU     TIME
 4.0 00:14:53   
/home/wireshark/menagerie/menagerie/7016-mysql-prepared_statements.capture: 
ls: cannot access /fuzz/buildbot/fuzztest/menagerie-fuzz-1.8/fuzz-*.pcap: No
such file or directory

I checked in a fix in trunk-1.8 and will forward-port it shortly. We aren't
seeing the issue in trunk-1.6 because we run fewer passes.

---

      You are receiving this mail because:

• You are watching all bug changes.