This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/36/42036/3 in repository toolchain/jenkins-scripts.
discards b3e0747c5 round-robin-bisect.sh: Prioritize interesting commits discards b324481d2 round-robin-bisect.sh: Cleanup and simplify processing of int [...] discards 870189094 round-robin-bisect.sh: Regenerate the list of interesting-commits discards e52161e1f round-robin-bisect.sh: Check all available interesing commits discards ef11d493b round-robin-bisect.sh: Cleanup code to try interesting-commits discards e20e5a5fc round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...] adds d8389d726 round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (b3e0747c5) \ N -- N -- N refs/changes/36/42036/3 (d8389d726)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
No new revisions were added by this update.
Summary of changes: round-robin-bisect.sh | 647 -------------------------------------------------- round-robin-notify.sh | 224 ----------------- 2 files changed, 871 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh