This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/59/39459/1
in repository toolchain/jenkins-scripts.
discards 7dbb69b82 jenkins-helpers.sh (fresh_dir): Handle GDB testsuite leaving files
adds 2fb593226 jenkins-helpers.sh (fresh_dir): Handle GDB testsuite leaving files
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 (7dbb69b82)
\
N -- N -- N refs/changes/59/39459/1 (2fb593226)
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/59/39259/4
in repository toolchain/jenkins-scripts.
discards 050ddab77 round-robin-bisect.sh: Simplify handling of baseline repos/remotes
adds ceae71fe8 round-robin-bisect.sh: Simplify handling of baseline repos/remotes
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 (050ddab77)
\
N -- N -- N refs/changes/59/39259/4 (ceae71fe8)
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/59/39259/3
in repository toolchain/jenkins-scripts.
discards f7ba27678 round-robin-bisect.sh: Simplify handling of baseline repos/remotes
adds 4023635aa round-robin-bisect.sh: Simplify handling of baseline repos/remotes
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 (f7ba27678)
\
N -- N -- N refs/changes/59/39259/3 (4023635aa)
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/59/39259/2
in repository toolchain/jenkins-scripts.
discards 458b235bf round-robin-bisect.sh: Simplify handling of baseline repos/remotes
adds 8729aef86 round-robin-bisect.sh: Simplify handling of baseline repos/remotes
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 (458b235bf)
\
N -- N -- N refs/changes/59/39259/2 (8729aef86)
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/59/39259/1
in repository toolchain/jenkins-scripts.
discards 2b1251092 round-robin-bisect.sh: Simplify handling of baseline repos/remotes
adds 2f9f3705c round-robin-bisect.sh: Simplify handling of baseline repos/remotes
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 (2b1251092)
\
N -- N -- N refs/changes/59/39259/1 (2f9f3705c)
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/59/35659/2
in repository toolchain/jenkins-scripts.
discards bd2d2e766 tcwg-update-llvmbot-containers.sh: Put LLDB bots on tcwg-amp-05
adds ad1e09828 tcwg-update-llvmbot-containers.sh: Put LLDB bots on tcwg-amp-05
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 (bd2d2e766)
\
N -- N -- N refs/changes/59/35659/2 (ad1e09828)
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/59/35659/1
in repository toolchain/jenkins-scripts.
discards 58f2980e2 tcwg-update-llvmbot-containers.sh: Put LLDB bots on tcwg-amp-05
new 2f37d5c40 tcwg-update-llvmbot-containers.sh: Put LLDB bots on tcwg-amp-05
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 (58f2980e2)
\
N -- N -- N refs/changes/59/35659/1 (2f37d5c40)
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/59/35059/5
in repository toolchain/jenkins-scripts.
discards d74b53fbc jenkins-helpers.sh: Add log URL when running a step
adds 0b7d3791d jenkins-helpers.sh: Add log URL when running a step
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 (d74b53fbc)
\
N -- N -- N refs/changes/59/35059/5 (0b7d3791d)
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/59/35059/4
in repository toolchain/jenkins-scripts.
discards 0f4b83390 jenkins-helpers.sh: Add log URL when running a step
adds c3750b53b jenkins-helpers.sh: Add log URL when running a step
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 (0f4b83390)
\
N -- N -- N refs/changes/59/35059/4 (c3750b53b)
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/59/35059/3
in repository toolchain/jenkins-scripts.
discards 426cb110f jenkins-helpers.sh: Add log URL when running a step
adds 2c0ee5372 jenkins-helpers.sh: Add log URL when running a step
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 (426cb110f)
\
N -- N -- N refs/changes/59/35059/3 (2c0ee5372)
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.