This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/74/46774/1
in repository toolchain/jenkins-scripts.
discards c5673dea8 tcwg_chromium.sh: add chromium script
new bdf60c40f tcwg_chromium.sh: add chromium script
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 (c5673dea8)
\
N -- N -- N refs/changes/74/46774/1 (bdf60c40f)
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/74/46474/1
in repository toolchain/jenkins-scripts.
discards 121cb0b2e tcwg_aosp-build: try to fix aosp build error
adds 7fa99d811 tcwg_aosp-build: try to fix aosp build error
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 (121cb0b2e)
\
N -- N -- N refs/changes/74/46474/1 (7fa99d811)
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/74/46374/2
in repository toolchain/jenkins-scripts.
discards 0d217e631 round-robin-notify.sh: calculate_results_date called only once
discards 73ae825f6 Revert "tcwg_bmk-config.sh: Skip fortran tests when asking for O..."
adds 18a7531a8 Revert "tcwg_bmk-config.sh: Skip fortran tests when asking for 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 (0d217e631)
\
N -- N -- N refs/changes/74/46374/2 (18a7531a8)
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:
round-robin-baseline.sh | 567 ------------
round-robin-bisect.sh | 681 --------------
round-robin-notify.sh | 2289 -----------------------------------------------
3 files changed, 3537 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
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/74/46374/1
in repository toolchain/jenkins-scripts.
discards 8a27297c5 round-robin-notify.sh: calculate_results_date called only once
discards c3f2bae99 lnt-utils.sh: Disable some debug traces
adds 99815b931 lnt-utils.sh: Disable some debug traces
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 (8a27297c5)
\
N -- N -- N refs/changes/74/46374/1 (99815b931)
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:
round-robin-baseline.sh | 567 ------------
round-robin-bisect.sh | 681 --------------
round-robin-notify.sh | 2287 -----------------------------------------------
3 files changed, 3535 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
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/74/46174/1
in repository toolchain/jenkins-scripts.
discards b0ef768a0 ansible/bare-metal.yaml: Add playbook for bare metal machines
new 9a520c448 ansible/bare-metal.yaml: Add playbook for bare metal machines
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 (b0ef768a0)
\
N -- N -- N refs/changes/74/46174/1 (9a520c448)
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/74/45974/3
in repository toolchain/jenkins-scripts.
discards 484f718fc tcwg-report-stale-rr-jobs.sh: Fix remote repository handling
adds 6b7db9b03 tcwg-report-stale-rr-jobs.sh: Fix remote repository handling
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 (484f718fc)
\
N -- N -- N refs/changes/74/45974/3 (6b7db9b03)
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/74/45974/2
in repository toolchain/jenkins-scripts.
discards a98e9d484 tcwg-report-stale-rr-jobs.sh: Fix remote repository handling
adds b0733f575 tcwg-report-stale-rr-jobs.sh: Fix remote repository handling
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 (a98e9d484)
\
N -- N -- N refs/changes/74/45974/2 (b0733f575)
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/74/45974/1
in repository toolchain/jenkins-scripts.
discards 114a70055 tcwg-report-stale-rr-jobs.sh: Fix remote repository handling
new 7e82fc9d2 tcwg-report-stale-rr-jobs.sh: Fix remote repository handling
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 (114a70055)
\
N -- N -- N refs/changes/74/45974/1 (7e82fc9d2)
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/74/45674/1
in repository toolchain/jenkins-scripts.
discards 08db330b1 tcwg_bmk-build.sh: Test history rewrite on SPEC CPU2006 configs
adds 0c9f4f98d tcwg_bmk-build.sh: Test history rewrite on SPEC CPU2006 configs
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 (08db330b1)
\
N -- N -- N refs/changes/74/45674/1 (0c9f4f98d)
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/74/45474/5
in repository toolchain/jenkins-scripts.
discards c9edc7b90 tcwg_bmk-build.sh,round-robin-notify.sh: Regenerate details a [...]
adds 93999da25 tcwg_bmk-build.sh,round-robin-notify.sh: Regenerate details a [...]
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 (c9edc7b90)
\
N -- N -- N refs/changes/74/45474/5 (93999da25)
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.