This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/43596/1
in repository toolchain/jenkins-scripts.
discards 6336f1a82 round-robin.sh: Re-run failed ABE builds without parallelism
new f5be77bd5 round-robin.sh: Re-run failed ABE builds without parallelism
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 (6336f1a82)
\
N -- N -- N refs/changes/96/43596/1 (f5be77bd5)
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 1 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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42996/2
in repository toolchain/jenkins-scripts.
discards fa9585db1 downstream_patches: Add spec2k6 patch to do atomic creation o [...]
adds 0384f7e77 downstream_patches: Add spec2k6 patch to do atomic creation o [...]
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 (fa9585db1)
\
N -- N -- N refs/changes/96/42996/2 (0384f7e77)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42996/1
in repository toolchain/jenkins-scripts.
discards 059fce3e5 downstream_patches: Add spec2k6 patch to do atomic creation o [...]
new 35a39d2a0 downstream_patches: Add spec2k6 patch to do atomic creation o [...]
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 (059fce3e5)
\
N -- N -- N refs/changes/96/42996/1 (35a39d2a0)
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 1 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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42796/2
in repository toolchain/jenkins-scripts.
discards 5baa80688 LLVM WoA Release: Disable LLDB watchpoint tests
adds e0021151c LLVM WoA Release: Disable LLDB watchpoint tests
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 (5baa80688)
\
N -- N -- N refs/changes/96/42796/2 (e0021151c)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42796/1
in repository toolchain/jenkins-scripts.
discards 118ae3428 LLVM WoA Release: Disable LLDB watchpoint tests
adds 04dfcb4a8 LLVM WoA Release: Disable LLDB watchpoint tests
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 (118ae3428)
\
N -- N -- N refs/changes/96/42796/1 (04dfcb4a8)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42596/1
in repository toolchain/jenkins-scripts.
discards 73882e89c tcwg-report-stale-rr-jobs.sh: fix dumped project url
adds 44fedc571 tcwg-report-stale-rr-jobs.sh: fix dumped project url
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 (73882e89c)
\
N -- N -- N refs/changes/96/42596/1 (44fedc571)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42396/3
in repository toolchain/jenkins-scripts.
discards 62343ad76 wrappers/shadow-cc.sh: Handle expected fails of orig_cc
adds a31132c14 wrappers/shadow-cc.sh: Handle expected fails of orig_cc
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 (62343ad76)
\
N -- N -- N refs/changes/96/42396/3 (a31132c14)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42396/2
in repository toolchain/jenkins-scripts.
discards 76129b6c4 wrappers/shadow-cc.sh: Handle expected fails of orig_cc
adds e585bb751 wrappers/shadow-cc.sh: Handle expected fails of orig_cc
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 (76129b6c4)
\
N -- N -- N refs/changes/96/42396/2 (e585bb751)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/42396/1
in repository toolchain/jenkins-scripts.
discards 92ab5cb29 wrappers/shadow-cc.sh: Handle expected fails of orig_cc
adds 0a02e3f48 wrappers/shadow-cc.sh: Handle expected fails of orig_cc
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 (92ab5cb29)
\
N -- N -- N refs/changes/96/42396/1 (0a02e3f48)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/96/39296/1
in repository toolchain/jenkins-scripts.
discards 1f8fbbae5 tcwg-benchmark.sh: Move handling of "builder" parameter
adds d811dabc2 tcwg-benchmark.sh: Move handling of "builder" parameter
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 (1f8fbbae5)
\
N -- N -- N refs/changes/96/39296/1 (d811dabc2)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.