[Wireshark-bugs] [Bug 13215] Buildbot crash output: fuzz-2016-12-07-6687.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13215

--- Comment #2 from Gerald Combs  ---
(In reply to Michael Mann from comment #1)

> However, the Change-Id listed for the commit is for the cherry-pick done to
> the master-2.2 and master-2.0 branches, but buildbot URLS, etc. claim this
> is from master branch.  Did something break and we don't distinguish master
> from 2.2 and 2.0 properly on the buildbot?

The recent Gerrit upgrade changed the event stream format slightly to include
full branch paths instead of plain branch names. It took me a couple of tries
to update the master Buildbot configuration correctly. As a result it was
building from all branches for a short time.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13215] Buildbot crash output: fuzz-2016-12-07-6687.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13215

Michael Mann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||mman...@netscape.net
 Resolution|--- |DUPLICATE

--- Comment #1 from Michael Mann  ---
Some of the information here has to be wrong, and I'm not sure which it is.

The line referenced in packet-cops.c (1103) is #if 0ed out when the git commit
listed occurred (i.e. after Guy's changes to break big if statement up) on the
master branch.

However, the Change-Id listed for the commit is for the cherry-pick done to the
master-2.2 and master-2.0 branches, but buildbot URLS, etc. claim this is from
master branch.  Did something break and we don't distinguish master from 2.2
and 2.0 properly on the buildbot?

*** This bug has been marked as a duplicate of bug 13044 ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe