This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/25/43425/1
in repository toolchain/jenkins-scripts.
discards 473ede816 tcwg_aosp-build.sh: Clean AOSP checkout
adds b87492d86 tcwg_aosp-build.sh: Clean AOSP checkout
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 (473ede816)
\
N -- N -- N refs/changes/25/43425/1 (b87492d86)
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/25/43225/4
in repository toolchain/jenkins-scripts.
discards b05b13e31 tcwg-benchmark-results.sh: Do not assume output directory exists
adds 820b26407 tcwg-benchmark-results.sh: Do not assume output directory exists
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 (b05b13e31)
\
N -- N -- N refs/changes/25/43225/4 (820b26407)
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/25/43225/3
in repository toolchain/jenkins-scripts.
discards 0a9a40223 tcwg-benchmark-results.sh: Do not assume output directory exists
adds d1655122e tcwg-benchmark-results.sh: Do not assume output directory exists
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 (0a9a40223)
\
N -- N -- N refs/changes/25/43225/3 (d1655122e)
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/25/43225/2
in repository toolchain/jenkins-scripts.
discards 684055de9 tcwg-benchmark-results.sh: Do not assume output directory exists
adds f55102440 tcwg-benchmark-results.sh: Do not assume output directory exists
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 (684055de9)
\
N -- N -- N refs/changes/25/43225/2 (f55102440)
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/25/43225/1
in repository toolchain/jenkins-scripts.
discards 77efe6a6e tcwg-benchmark-results.sh: Do not assume output directory exists
adds 56d13ebfe tcwg-benchmark-results.sh: Do not assume output directory exists
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 (77efe6a6e)
\
N -- N -- N refs/changes/25/43225/1 (56d13ebfe)
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/25/42925/2
in repository toolchain/jenkins-scripts.
discards 68eecd612 round-robin.sh: use tcwg_bmk_hw to get the hw to use
adds ee7a80f0f round-robin.sh: use tcwg_bmk_hw to get the hw to use
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 (68eecd612)
\
N -- N -- N refs/changes/25/42925/2 (ee7a80f0f)
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/25/42925/1
in repository toolchain/jenkins-scripts.
discards 662ab87eb round-robin.sh: use tcwg_bmk_hw to get the hw to use
adds d368c8e62 round-robin.sh: use tcwg_bmk_hw to get the hw to use
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 (662ab87eb)
\
N -- N -- N refs/changes/25/42925/1 (d368c8e62)
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/25/42625/5
in repository toolchain/jenkins-scripts.
discards 7eb98aab8 wrappers/shadow-strip.sh: new shadow wrapper
adds c98bad8a9 wrappers/shadow-strip.sh: new shadow wrapper
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 (7eb98aab8)
\
N -- N -- N refs/changes/25/42625/5 (c98bad8a9)
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/25/42625/4
in repository toolchain/jenkins-scripts.
discards 00328bd25 wrappers/shadow-strip.sh: new shadow wrapper
new 5669adc73 wrappers/shadow-strip.sh: new shadow wrapper
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 (00328bd25)
\
N -- N -- N refs/changes/25/42625/4 (5669adc73)
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/25/42625/3
in repository toolchain/jenkins-scripts.
discards ff41a0702 wrappers/shadow-strip.sh: new shadow wrapper
new 60c0ffd01 wrappers/shadow-strip.sh: new shadow wrapper
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 (ff41a0702)
\
N -- N -- N refs/changes/25/42625/3 (60c0ffd01)
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.