#2249: change merging is no longer picking the newest change
-------------------+-------------------------
Reporter: dustin | Owner:
Type: defect | Status: closed
Priority: major | Milestone: 0.8.7
Version: 0.8.6 | Resolution: worksforme
Keywords: |
-------------------+-------------------------
Comment (by brendan):
I've been struck by this issue. In my case, the sourcestamps have no
associated change lists (not sure why, but probably because the builder
was scheduled by a trigger -- though the invoker's sourcestamps have
single entry change lists). Looking at sourceStamp.mergeWith, it seems
you'd get the oldest revision if the changes list is empty?
--
Ticket URL: <http://trac.buildbot.net/ticket/2249#comment:4>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
