Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/28/30528/2 updated (9dc895030 -> f4659eeae)

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/28/30528/2 in repository toolchain/jenkins-scripts. discards 9dc895030 jenkins-helpers.sh: Don't touch step's artifacts directory un [...] new f4659eeae jenkins-helpers.sh: Don't touch step's artifacts directory un [...] 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 (9dc895030) \ N -- N -- N refs/changes/28/30528/2 (f4659eeae) 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/28/30528/1 updated (f2c612ddb -> 8e36bd3d7)

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/28/30528/1 in repository toolchain/jenkins-scripts. discards f2c612ddb jenkins-helpers.sh: Don't touch step's artifacts directory un [...] adds 8e36bd3d7 jenkins-helpers.sh: Don't touch step's artifacts directory un [...] 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 (f2c612ddb) \ N -- N -- N refs/changes/28/30528/1 (8e36bd3d7) 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/28/29828/1 updated (b53942356 -> 50a46f449)

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/28/29828/1 in repository toolchain/jenkins-scripts. discards b53942356 tcwg-benchmark-size.sh: New script to track SPEC CPU2006 code [...] adds 50a46f449 tcwg-benchmark-size.sh: New script to track SPEC CPU2006 code [...] 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 (b53942356) \ N -- N -- N refs/changes/28/29828/1 (50a46f449) 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/27/47327/1 updated (bc3441401 -> 8437865af)

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/27/47327/1 in repository toolchain/jenkins-scripts. discards bc3441401 Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent" adds 8437865af Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent" 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 (bc3441401) \ N -- N -- N refs/changes/27/47327/1 (8437865af) 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/27/47227/1 updated (0f44b6c2b -> a3370bef4)

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/27/47227/1 in repository toolchain/jenkins-scripts. discards 0f44b6c2b tcwg_chromium-build.sh: gclient sync is needed even in fast_demo adds a3370bef4 tcwg_chromium-build.sh: gclient sync is needed even in fast_demo 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 (0f44b6c2b) \ N -- N -- N refs/changes/27/47227/1 (a3370bef4) 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/27/47127/1 updated (1e7d74d00 -> 1ffd07636)

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/27/47127/1 in repository toolchain/jenkins-scripts. discards 1e7d74d00 cimonitor-configs: Add new pages adds 1ffd07636 cimonitor-configs: Add new pages 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 (1e7d74d00) \ N -- N -- N refs/changes/27/47127/1 (1ffd07636) 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/27/47027/1 updated (aee13be64 -> 8247c82e3)

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/27/47027/1 in repository toolchain/jenkins-scripts. discards aee13be64 tcwg_chromium_build: re-enable full build adds 8247c82e3 tcwg_chromium_build: re-enable full build 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 (aee13be64) \ N -- N -- N refs/changes/27/47027/1 (8247c82e3) 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/27/46727/1 updated (53e55426b -> dc29ffd1f)

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/27/46727/1 in repository toolchain/jenkins-scripts. discards 53e55426b tcwg-update-lnt-results.sh: Fix lnt_results.csv file extract adds dc29ffd1f tcwg-update-lnt-results.sh: Fix lnt_results.csv file extract 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 (53e55426b) \ N -- N -- N refs/changes/27/46727/1 (dc29ffd1f) 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/27/46227/1 updated (b77a11e60 -> 52a53f178)

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/27/46227/1 in repository toolchain/jenkins-scripts. discards b77a11e60 round-robin-notify.sh (setup_notify_environment): Support "-- [...] discards 3286c0602 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Handle [...] adds 52a53f178 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Handle [...] 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 (b77a11e60) \ N -- N -- N refs/changes/27/46227/1 (52a53f178) 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 | 1979 ----------------------------------------------- 3 files changed, 3227 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/27/45727/4 updated (4de03c17a -> e6ca3d772)

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/27/45727/4 in repository toolchain/jenkins-scripts. discards 4de03c17a round-robin-notify.sh (print_commits): Remove 'basepoints/' f [...] discards db16af9a8 round-robin-notify.sh (print_icommits_link): Use git-us.l.o discards 9c4c80a6b Revert "Revert "tcwg-update-llvmbot-containers.sh: Add silent [...] adds e6ca3d772 Revert "Revert "tcwg-update-llvmbot-containers.sh: Add silent [...] 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 (4de03c17a) \ N -- N -- N refs/changes/27/45727/4 (e6ca3d772) 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 | 553 --------------- round-robin-bisect.sh | 681 ------------------ round-robin-notify.sh | 1808 ----------------------------------------------- 3 files changed, 3042 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024