This is an automated email from the git hooks/post-receive script.

"Maxim Kuvyrkov pushed a change to branch rr-many in repository toolchain/jenkins-scripts.

discards 9cdc36b [WIP] Round-robin improvements new 6618664 tcwg_kernel-bisect.sh: Use rr[ci_config] instead of its sub-items new c2fd531 tcwg_kernel-bisect.sh: Detect linker and make errors in the logs new 2fa4f72 [rr-many 1/N]: Support testing multiple projects in the same build new 8171582 [rr-many 2/N] Update and simplify round-robin.sh: clone_repo() new d4084ea [rr-many 3/N] Rework trigger files for follow-up builds. new b4f6859 [rr-many 4/N] Update round-robin.sh: update_baseline() new a0ff413 [rr-many 5/N] Update update_baseline new f60d654 [rr-many 6/N] Improve update_baseline

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (9cdc36b) \ N -- N -- N refs/heads/rr-many (f60d654)

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.

The 8 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: round-robin.sh | 19 ++++++++++++++++--- tcwg_kernel-build.sh | 1 + 2 files changed, 17 insertions(+), 3 deletions(-)