This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/87/44387/10
in repository toolchain/jenkins-scripts.
discards 00ca471cd start-container-docker.sh: Add "--task precommit"
new 1b5e89e7d start-container-docker.sh: Add "--task precommit"
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 (00ca471cd)
\
N -- N -- N refs/changes/87/44387/10 (1b5e89e7d)
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/87/44387/1
in repository toolchain/jenkins-scripts.
discards 4424695f4 start-container-docker.sh: Add "--task precommit"
adds 42387542a start-container-docker.sh: Add "--task precommit"
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 (4424695f4)
\
N -- N -- N refs/changes/87/44387/1 (42387542a)
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/87/43787/1
in repository toolchain/jenkins-scripts.
discards 9455f5489 round-robin.sh: Commit missing hunk
adds 1d1f72107 round-robin.sh: Commit missing hunk
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 (9455f5489)
\
N -- N -- N refs/changes/87/43787/1 (1d1f72107)
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/87/42787/1
in repository toolchain/jenkins-scripts.
discards e2d957893 tcwg-report-stale-rr-jobs.sh: output array more readable
adds cd95a7adf tcwg-report-stale-rr-jobs.sh: output array more readable
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 (e2d957893)
\
N -- N -- N refs/changes/87/42787/1 (cd95a7adf)
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/87/42687/2
in repository toolchain/jenkins-scripts.
discards f3132906d tcwg_aosp-build.sh (no_regression_p): Add code-size analysis
adds 2e46fb30b tcwg_aosp-build.sh (no_regression_p): Add code-size analysis
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 (f3132906d)
\
N -- N -- N refs/changes/87/42687/2 (2e46fb30b)
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/87/42687/1
in repository toolchain/jenkins-scripts.
discards 9e599fd58 tcwg_aosp-build.sh (no_regression_p): Add code-size analysis
adds 4daaac033 tcwg_aosp-build.sh (no_regression_p): Add code-size analysis
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 (9e599fd58)
\
N -- N -- N refs/changes/87/42687/1 (4daaac033)
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/87/41987/1
in repository toolchain/jenkins-scripts.
discards 8ffc6ce77 dashboard*: handle when project doesnot exists
adds eea6dcf21 dashboard*: handle when project doesnot 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 (8ffc6ce77)
\
N -- N -- N refs/changes/87/41987/1 (eea6dcf21)
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/87/41887/2
in repository toolchain/jenkins-scripts.
discards ece2df851 tcwg_bmk-build.sh: Fix reporting improvement as a regression
adds bf770036a tcwg_bmk-build.sh: Fix reporting improvement as a regression
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 (ece2df851)
\
N -- N -- N refs/changes/87/41887/2 (bf770036a)
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/87/41887/1
in repository toolchain/jenkins-scripts.
discards 45ca469bc tcwg_bmk-build.sh: Fix reporting improvement as a regression
new 609437922 tcwg_bmk-build.sh: Fix reporting improvement as a regression
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 (45ca469bc)
\
N -- N -- N refs/changes/87/41887/1 (609437922)
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/87/39387/1
in repository toolchain/jenkins-scripts.
discards 01a014bc5 tcwg_gnu-build.sh: Update settings for tcwg_gnu_* ci_projects
adds b72ee0195 tcwg_gnu-build.sh: Update settings for tcwg_gnu_* ci_projects
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 (01a014bc5)
\
N -- N -- N refs/changes/87/39387/1 (b72ee0195)
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.