Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/33/34233/1 updated (bed581c4b -> 79c2349d2)

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/33/34233/1 in repository toolchain/jenkins-scripts. discards bed581c4b tcwg-start-container.sh: Reduce container downtime adds 79c2349d2 tcwg-start-container.sh: Reduce container downtime 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 (bed581c4b) \ N -- N -- N refs/changes/33/34233/1 (79c2349d2) 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/33/33433/1 updated (588a4354f -> 6acfdadb5)

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/33/33433/1 in repository toolchain/jenkins-scripts. discards 588a4354f round-robin.sh: Fix "set -e" behavior of no_regression_p predicates adds 6acfdadb5 round-robin.sh: Fix "set -e" behavior of no_regression_p predicates 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 (588a4354f) \ N -- N -- N refs/changes/33/33433/1 (6acfdadb5) 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/33/32033/2 updated (26c8fcdd2 -> ed00d2fec)

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/33/32033/2 in repository toolchain/jenkins-scripts. discards 26c8fcdd2 tcwg-update-llvmbot-containers.sh: Restart existing bot containers adds ed00d2fec tcwg-update-llvmbot-containers.sh: Restart existing bot containers 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 (26c8fcdd2) \ N -- N -- N refs/changes/33/32033/2 (ed00d2fec) 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/33/32033/1 updated (f91d6fea3 -> a16d40981)

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/33/32033/1 in repository toolchain/jenkins-scripts. discards f91d6fea3 tcwg-update-llvmbot-containers.sh: Restart existing bot containers new a16d40981 tcwg-update-llvmbot-containers.sh: Restart existing bot containers 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 (f91d6fea3) \ N -- N -- N refs/changes/33/32033/1 (a16d40981) 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/33/30433/1 updated (8fb56bc0a -> 292479dd9)

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/33/30433/1 in repository toolchain/jenkins-scripts. discards 8fb56bc0a tcwg_kernel-build.sh: Update build step name adds 292479dd9 tcwg_kernel-build.sh: Update build step name 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 (8fb56bc0a) \ N -- N -- N refs/changes/33/30433/1 (292479dd9) 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/33/30333/1 updated (d57ba50ea -> 3a7f0a965)

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/33/30333/1 in repository toolchain/jenkins-scripts. discards d57ba50ea tcwg_bmk-build.sh: Print some info when a regression is detected. adds 3a7f0a965 tcwg_bmk-build.sh: Print some info when a regression is detected. 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 (d57ba50ea) \ N -- N -- N refs/changes/33/30333/1 (3a7f0a965) 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/33/29433/2 updated (fab3817fc -> bd4f0b256)

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/33/29433/2 in repository toolchain/jenkins-scripts. discards fab3817fc Fix handling of $top_artifacts adds bd4f0b256 Fix handling of $top_artifacts 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 (fab3817fc) \ N -- N -- N refs/changes/33/29433/2 (bd4f0b256) 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/33/29433/1 updated (62ac0e765 -> 294569065)

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/33/29433/1 in repository toolchain/jenkins-scripts. discards 62ac0e765 Fix handling of $top_artifacts adds 294569065 Fix handling of $top_artifacts 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 (62ac0e765) \ N -- N -- N refs/changes/33/29433/1 (294569065) 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/32/47232/2 updated (6ffbddc0b -> bb702a7c1)

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/32/47232/2 in repository toolchain/jenkins-scripts. discards 6ffbddc0b round-robin-bisect.sh: fix bisect first_bad revision discards d5553b2d1 round-robin.sh (build_abe): Use ABE's --force_build adds bb702a7c1 round-robin.sh (build_abe): Use ABE's --force_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 (6ffbddc0b) \ N -- N -- N refs/changes/32/47232/2 (bb702a7c1) 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 | 650 ------------- round-robin-bisect.sh | 744 --------------- round-robin-notify.sh | 2416 ----------------------------------------------- 3 files changed, 3810 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/32/47232/1 updated (d169b224d -> 32f13a6d7)

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/32/47232/1 in repository toolchain/jenkins-scripts. discards d169b224d round-robin-bisect.sh: fix bisect first_bad revision discards 2755a6898 round-robin-baseline.sh: Respect expiration date when trimmin [...] adds 32f13a6d7 round-robin-baseline.sh: Respect expiration date when trimmin [...] 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 (d169b224d) \ N -- N -- N refs/changes/32/47232/1 (32f13a6d7) 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 | 669 ------------- round-robin-bisect.sh | 744 --------------- round-robin-notify.sh | 2419 ----------------------------------------------- 3 files changed, 3832 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