Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/28/32328/3 updated (f805415ba -> 07f12f87f)

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/32328/3 in repository toolchain/jenkins-scripts. discards f805415ba tcwg-llvm-release.sh: Use ninja by default adds 07f12f87f tcwg-llvm-release.sh: Use ninja by default 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 (f805415ba) \ N -- N -- N refs/changes/28/32328/3 (07f12f87f) 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/32328/2 updated (359cbc42f -> 315774867)

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/32328/2 in repository toolchain/jenkins-scripts. discards 359cbc42f tcwg-llvm-release.sh: Use ninja by default new 315774867 tcwg-llvm-release.sh: Use ninja by default 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 (359cbc42f) \ N -- N -- N refs/changes/28/32328/2 (315774867) 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/32328/1 updated (4fc5c7cdd -> f42ed0684)

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/32328/1 in repository toolchain/jenkins-scripts. discards 4fc5c7cdd tcwg-llvm-release.sh: Use ninja by default new f42ed0684 tcwg-llvm-release.sh: Use ninja by default 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 (4fc5c7cdd) \ N -- N -- N refs/changes/28/32328/1 (f42ed0684) 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/31228/2 updated (228bc3552 -> 2f38ad1ef)

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/31228/2 in repository toolchain/jenkins-scripts. discards 228bc3552 round-robin-bisect.sh: Update email preferences discards 7b30ff45b tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops adds 2f38ad1ef tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops 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 (228bc3552) \ N -- N -- N refs/changes/28/31228/2 (2f38ad1ef) 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 | 504 -------------------------------------------------- 1 file changed, 504 deletions(-) delete mode 100755 round-robin-bisect.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/28/31228/1 updated (3b6051a87 -> 1940f66b7)

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/31228/1 in repository toolchain/jenkins-scripts. discards 3b6051a87 round-robin-bisect.sh: Update email preferences discards 4c3af25d6 tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops new 1940f66b7 tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops 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 (3b6051a87) \ N -- N -- N refs/changes/28/31228/1 (1940f66b7) 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: round-robin-bisect.sh | 504 -------------------------------------------------- 1 file changed, 504 deletions(-) delete mode 100755 round-robin-bisect.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/28/30928/2 updated (9a3008b40 -> c86dc9cd6)

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/30928/2 in repository toolchain/jenkins-scripts. discards 9a3008b40 jenkins-helpers.sh: run_step: Use 'ts' adds c86dc9cd6 jenkins-helpers.sh: run_step: Use 'ts' 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 (9a3008b40) \ N -- N -- N refs/changes/28/30928/2 (c86dc9cd6) 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/30928/1 updated (820b271fb -> 3fd70b282)

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/30928/1 in repository toolchain/jenkins-scripts. discards 820b271fb jenkins-helpers.sh: run_step: Use 'ts' new 3fd70b282 jenkins-helpers.sh: run_step: Use 'ts' 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 (820b271fb) \ N -- N -- N refs/changes/28/30928/1 (3fd70b282) 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/30828/1 updated (0aaeac201 -> de85375bb)

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/30828/1 in repository toolchain/jenkins-scripts. discards 0aaeac201 Merge branch 'master' into tcwg_bmk new de85375bb Merge branch 'master' into tcwg_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 (0aaeac201) \ N -- N -- N refs/changes/28/30828/1 (de85375bb) 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/30728/1 updated (706939dbd -> 407196855)

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/30728/1 in repository toolchain/jenkins-scripts. discards 706939dbd Merge branch 'tcwg_gnu' new 407196855 Merge branch 'tcwg_gnu' 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 (706939dbd) \ N -- N -- N refs/changes/28/30728/1 (407196855) 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/3 updated (22f96d2f3 -> a2e297c17)

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/3 in repository toolchain/jenkins-scripts. discards 22f96d2f3 jenkins-helpers.sh: Don't touch step's artifacts directory un [...] adds a2e297c17 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 (22f96d2f3) \ N -- N -- N refs/changes/28/30528/3 (a2e297c17) 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