This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/17/29617/1
in repository toolchain/jenkins-scripts.
discards 4f9c56545 jenkins-helpers.sh: Create directory for manifest file.
adds 1069dad32 jenkins-helpers.sh: Create directory for manifest file.
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 (4f9c56545)
\
N -- N -- N refs/changes/17/29617/1 (1069dad32)
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/16/47116/2
in repository toolchain/jenkins-scripts.
discards 7e0ce3017 cimonitor-configs/LNT.yaml: Update LNT port number
adds c76bbd10b cimonitor-configs/LNT.yaml: Update LNT port number
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 (7e0ce3017)
\
N -- N -- N refs/changes/16/47116/2 (c76bbd10b)
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/16/47116/1
in repository toolchain/jenkins-scripts.
discards ebfa1fd8e cimonitor-configs/LNT.yaml: Update LNT port number
new e4d4369ef cimonitor-configs/LNT.yaml: Update LNT port number
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 (ebfa1fd8e)
\
N -- N -- N refs/changes/16/47116/1 (e4d4369ef)
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/16/46316/2
in repository toolchain/jenkins-scripts.
discards 73d7ea24a tcwg-lnt: add patch showing non-normalized values in graphs
adds 457f9ccfe tcwg-lnt: add patch showing non-normalized values in graphs
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 (73d7ea24a)
\
N -- N -- N refs/changes/16/46316/2 (457f9ccfe)
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/16/46316/1
in repository toolchain/jenkins-scripts.
discards 8aef1775e tcwg-lnt: add patch showing non-normalized values in graphs
adds 11cb80458 tcwg-lnt: add patch showing non-normalized values in graphs
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 (8aef1775e)
\
N -- N -- N refs/changes/16/46316/1 (11cb80458)
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/16/45716/1
in repository toolchain/jenkins-scripts.
discards f2bd8dd39 round-robin-bisect.sh (print_interesting_commit): Re-enable v [...]
discards 9f17f9ccc round-robin-bisect.sh (exit_0): Ensure we have permissions to [...]
discards 89876ce78 round-robin-notify.sh (update_jira_card): Improve handling of [...]
discards f51ae4d13 round-robin-notify.sh (jira cards): Do not update closed cards
discards e764a676c round-robin-notify.sh (gnu_print_result): Add links to useful logs
discards 60d3d8798 round-robin-notify.sh (gnu_print_result): Improve --long version
discards 17d36081f round-robin-notify.sh (print_mail_body): Add more ways to con [...]
discards 03877dae5 jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
adds e498d7bff jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
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 (f2bd8dd39)
\
N -- N -- N refs/changes/16/45716/1 (e498d7bff)
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 | 524 --------------
round-robin-bisect.sh | 681 ------------------
round-robin-notify.sh | 1789 -----------------------------------------------
3 files changed, 2994 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/16/45516/1
in repository toolchain/jenkins-scripts.
discards 96c513631 round-robin-notify.sh: Improve output for precommit testing
adds f9a39e5dd round-robin-notify.sh: Improve output for precommit testing
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 (96c513631)
\
N -- N -- N refs/changes/16/45516/1 (f9a39e5dd)
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/16/44816/1
in repository toolchain/jenkins-scripts.
discards e8ad862c4 round-robin-notify.sh: Post to jira only if jira files were g [...]
discards 11afb556c round-robin-baseline.sh (trim_base_artifacts): Fix removal of [...]
discards 46096e0b6 round-robin-baseline.sh: Fix output counter
discards 9f8abbe12 round-robin-baseline.sh: Avoid creating too many update_basel [...]
adds f5f2d3fbc round-robin-baseline.sh: Avoid creating too many update_basel [...]
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 (e8ad862c4)
\
N -- N -- N refs/changes/16/44816/1 (f5f2d3fbc)
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 | 410 -------------
round-robin-bisect.sh | 653 ---------------------
round-robin-notify.sh | 1485 -----------------------------------------------
3 files changed, 2548 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/16/44516/2
in repository toolchain/jenkins-scripts.
discards f0e452758 tcwg_gnu-build.sh: Apply GDB testsuite patch for tcwg_gdb_che [...]
adds 78a8fa35e tcwg_gnu-build.sh: Apply GDB testsuite patch for tcwg_gdb_che [...]
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 (f0e452758)
\
N -- N -- N refs/changes/16/44516/2 (78a8fa35e)
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/16/44516/1
in repository toolchain/jenkins-scripts.
discards 733d4934b tcwg_gnu-build.sh: Apply GDB testsuite patch for tcwg_gdb_che [...]
new 32b684525 tcwg_gnu-build.sh: Apply GDB testsuite patch for tcwg_gdb_che [...]
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 (733d4934b)
\
N -- N -- N refs/changes/16/44516/1 (32b684525)
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.