This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/30/41330/2
in repository toolchain/jenkins-scripts.
discards 35947e857 tcwg_bmk-build.sh, tcwg-benchmark.sh: Handle fx hardware
adds 7e3ec3c11 tcwg_bmk-build.sh, tcwg-benchmark.sh: Handle fx hardware
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 (35947e857)
\
N -- N -- N refs/changes/30/41330/2 (7e3ec3c11)
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/30/41330/1
in repository toolchain/jenkins-scripts.
discards 90d813274 tcwg_bmk-build.sh, tcwg-benchmark.sh: Handle fx hardware
new a9ca28fa3 tcwg_bmk-build.sh, tcwg-benchmark.sh: Handle fx hardware
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 (90d813274)
\
N -- N -- N refs/changes/30/41330/1 (a9ca28fa3)
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/30/35230/5
in repository toolchain/jenkins-scripts.
discards 31e16ccd5 round-robin.sh: Fix "bootstrap check" build step
adds 1f53432a3 round-robin.sh: Fix "bootstrap check" build 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 (31e16ccd5)
\
N -- N -- N refs/changes/30/35230/5 (1f53432a3)
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/30/35230/4
in repository toolchain/jenkins-scripts.
discards 8f5d9ccef round-robin.sh: Always delete ABE build dirs
adds fe7c0ad3f round-robin.sh: Always delete ABE build dirs
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 (8f5d9ccef)
\
N -- N -- N refs/changes/30/35230/4 (fe7c0ad3f)
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/30/35230/3
in repository toolchain/jenkins-scripts.
discards 658c5fc82 round-robin.sh: Always delete ABE build dirs
adds daa3fc464 round-robin.sh: Always delete ABE build dirs
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 (658c5fc82)
\
N -- N -- N refs/changes/30/35230/3 (daa3fc464)
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/30/35230/2
in repository toolchain/jenkins-scripts.
discards 4adac79d1 round-robin.sh: Always delete ABE build dirs
adds 587955878 round-robin.sh: Always delete ABE build dirs
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 (4adac79d1)
\
N -- N -- N refs/changes/30/35230/2 (587955878)
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/30/35230/1
in repository toolchain/jenkins-scripts.
discards 668c11fe5 round-robin.sh: Temporarily revert shellcheck fix
adds 598a153bd round-robin.sh: Temporarily revert shellcheck fix
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 (668c11fe5)
\
N -- N -- N refs/changes/30/35230/1 (598a153bd)
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/30/33630/1
in repository toolchain/jenkins-scripts.
discards e43f2ad6e round-robin-bisect.sh: Fix reference to undefined variable
discards a00319c08 round-robin-bisect.sh: Fix silly bug
discards 98a92b584 round-robin-bisect.sh: Add "git bisect replay" support
discards 579ea29a8 round-robin-bisect.sh: Simplify handling of bisect data
discards a40448f56 tcwg_bmk-build.sh: Allow more cflags combinations
adds 624ba2e9e tcwg_bmk-build.sh: Allow more cflags combinations
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 (e43f2ad6e)
\
N -- N -- N refs/changes/30/33630/1 (624ba2e9e)
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-bisect.sh | 594 --------------------------------------------------
1 file changed, 594 deletions(-)
delete mode 100755 round-robin-bisect.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/30/33030/2
in repository toolchain/jenkins-scripts.
discards 43c294847 tcwg_bmk-build.sh: Fix bug in handling piped output
adds 89c1437ce tcwg_bmk-build.sh: Fix bug in handling piped output
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 (43c294847)
\
N -- N -- N refs/changes/30/33030/2 (89c1437ce)
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/30/33030/1
in repository toolchain/jenkins-scripts.
discards 42163261b tcwg_bmk-build.sh: Fix bug in handling piped output
adds 569c12806 tcwg_bmk-build.sh: Fix bug in handling piped output
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 (42163261b)
\
N -- N -- N refs/changes/30/33030/1 (569c12806)
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.