Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/29/44629/1 updated (b8881946b -> 3bdfdfaad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44629/1 in repository toolchain/jenkins-scripts. discards b8881946b round-robin-notify.sh: Import build manifest directly from co [...] discards 2f1c110f6 round-robin-notify.sh (setup_notify_environment): Simplify discards 680eac835 round-robin.sh (clone_repo): Remove unneeded manifest entries adds 3bdfdfaad round-robin.sh (clone_repo): Remove unneeded manifest entries 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 (b8881946b) \ N -- N -- N refs/changes/29/44629/1 (3bdfdfaad) 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 | 166 ------ round-robin-bisect.sh | 653 --------------------- round-robin-notify.sh | 1440 ----------------------------------------------- 3 files changed, 2259 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44529/6 updated (4b36216d7 -> c793d7418)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44529/6 in repository toolchain/jenkins-scripts. discards 4b36216d7 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] adds c793d7418 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] 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 (4b36216d7) \ N -- N -- N refs/changes/29/44529/6 (c793d7418) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44529/5 updated (1571c8f41 -> 7c0a0cefe)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44529/5 in repository toolchain/jenkins-scripts. discards 1571c8f41 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] adds 7c0a0cefe round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] 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 (1571c8f41) \ N -- N -- N refs/changes/29/44529/5 (7c0a0cefe) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44529/4 updated (384cf6d29 -> 0e60bede3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44529/4 in repository toolchain/jenkins-scripts. discards 384cf6d29 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] adds 0e60bede3 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] 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 (384cf6d29) \ N -- N -- N refs/changes/29/44529/4 (0e60bede3) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44529/3 updated (6c2c3fe38 -> 4b043f7ba)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44529/3 in repository toolchain/jenkins-scripts. discards 6c2c3fe38 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] adds 4b043f7ba round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] 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 (6c2c3fe38) \ N -- N -- N refs/changes/29/44529/3 (4b043f7ba) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44529/2 updated (7f9bd9cb1 -> b607cd508)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44529/2 in repository toolchain/jenkins-scripts. discards 7f9bd9cb1 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] new b607cd508 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] 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 (7f9bd9cb1) \ N -- N -- N refs/changes/29/44529/2 (b607cd508) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44529/1 updated (fd5a36b87 -> 5f754e8e6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44529/1 in repository toolchain/jenkins-scripts. discards fd5a36b87 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] new 5f754e8e6 round-robin.sh,tcwg_bmk-build.sh,tcwg-benchmark-results.sh: S [...] 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 (fd5a36b87) \ N -- N -- N refs/changes/29/44529/1 (5f754e8e6) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44429/6 updated (4fe33ced0 -> 1dbd8f374)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44429/6 in repository toolchain/jenkins-scripts. discards 4fe33ced0 tcwg_bmk-build.sh: Use output-bmk-results output for bmk adds 1dbd8f374 tcwg_bmk-build.sh: Use output-bmk-results output for bmk 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 (4fe33ced0) \ N -- N -- N refs/changes/29/44429/6 (1dbd8f374) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44429/5 updated (e26eb9681 -> 16d79c20d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44429/5 in repository toolchain/jenkins-scripts. discards e26eb9681 tcwg_bmk-build.sh: Use output-bmk-results output for bmk adds 16d79c20d tcwg_bmk-build.sh: Use output-bmk-results output for bmk 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 (e26eb9681) \ N -- N -- N refs/changes/29/44429/5 (16d79c20d) 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/44429/4 updated (d8b4ebe87 -> afa059f12)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44429/4 in repository toolchain/jenkins-scripts. discards d8b4ebe87 tcwg_bmk-build.sh: Use output-bmk-results output for bmk adds afa059f12 tcwg_bmk-build.sh: Use output-bmk-results output for bmk 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 (d8b4ebe87) \ N -- N -- N refs/changes/29/44429/4 (afa059f12) 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.

11 months, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024