Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/34/44634/4 updated (b14fd131d -> 6621100cc)

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/34/44634/4 in repository toolchain/jenkins-scripts. discards b14fd131d round-robin*.sh: Use ${rr[no_regression_result]} adds 6621100cc round-robin*.sh: Use ${rr[no_regression_result]} 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 (b14fd131d) \ N -- N -- N refs/changes/34/44634/4 (6621100cc) 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/34/44634/3 updated (dbb51d410 -> 74c0c21df)

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/34/44634/3 in repository toolchain/jenkins-scripts. discards dbb51d410 round-robin*.sh: Use ${rr[no_regression_result]} adds 74c0c21df round-robin*.sh: Use ${rr[no_regression_result]} 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 (dbb51d410) \ N -- N -- N refs/changes/34/44634/3 (74c0c21df) 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/34/44634/2 updated (b4b2d1b77 -> 7a6b68c9a)

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/34/44634/2 in repository toolchain/jenkins-scripts. discards b4b2d1b77 round-robin*.sh: Use ${rr[no_regression_result]} new 7a6b68c9a round-robin*.sh: Use ${rr[no_regression_result]} 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 (b4b2d1b77) \ N -- N -- N refs/changes/34/44634/2 (7a6b68c9a) 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/34/44634/1 updated (b1f0fda1f -> 565d2a556)

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/34/44634/1 in repository toolchain/jenkins-scripts. discards b1f0fda1f round-robin*.sh: Use ${rr[no_regression_result]} new 565d2a556 round-robin*.sh: Use ${rr[no_regression_result]} 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 (b1f0fda1f) \ N -- N -- N refs/changes/34/44634/1 (565d2a556) 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/34/43034/1 updated (2208063db -> 543ec946d)

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/34/43034/1 in repository toolchain/jenkins-scripts. discards 2208063db round-robin.sh: Fix for jira card creation, related to projec [...] adds 543ec946d round-robin.sh: Fix for jira card creation, related to projec [...] 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 (2208063db) \ N -- N -- N refs/changes/34/43034/1 (543ec946d) 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/34/42434/2 updated (0e1a8a3f0 -> ac094a005)

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/34/42434/2 in repository toolchain/jenkins-scripts. discards 0e1a8a3f0 wrappers/shadow-cc.sh: Handle "-D foo" and "-fuse-ld=lld" adds ac094a005 wrappers/shadow-cc.sh: Handle "-D foo" and "-fuse-ld=lld" 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 (0e1a8a3f0) \ N -- N -- N refs/changes/34/42434/2 (ac094a005) 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/34/42434/1 updated (d58f0d6cc -> ba390f2f9)

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/34/42434/1 in repository toolchain/jenkins-scripts. discards d58f0d6cc wrappers/shadow-cc.sh: Handle "-D foo" and "-fuse-ld=lld" new ba390f2f9 wrappers/shadow-cc.sh: Handle "-D foo" and "-fuse-ld=lld" 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 (d58f0d6cc) \ N -- N -- N refs/changes/34/42434/1 (ba390f2f9) 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/34/42334/2 updated (ba8e238fb -> b61ed4089)

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/34/42334/2 in repository toolchain/jenkins-scripts. discards ba8e238fb round-robin.sh: Keep rr[results_date] if existing new b61ed4089 round-robin.sh: Keep rr[results_date] if existing 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 (ba8e238fb) \ N -- N -- N refs/changes/34/42334/2 (b61ed4089) 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/34/42334/1 updated (fb02a3152 -> df4879de8)

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/34/42334/1 in repository toolchain/jenkins-scripts. discards fb02a3152 round-robin.sh: Keep rr[results_date] if existing new df4879de8 round-robin.sh: Keep rr[results_date] if existing 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 (fb02a3152) \ N -- N -- N refs/changes/34/42334/1 (df4879de8) 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/34/42034/2 updated (870189094 -> d8389d726)

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/34/42034/2 in repository toolchain/jenkins-scripts. discards 870189094 round-robin-bisect.sh: Regenerate the list of interesting-commits discards e52161e1f round-robin-bisect.sh: Check all available interesing commits discards ef11d493b round-robin-bisect.sh: Cleanup code to try interesting-commits discards e20e5a5fc round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...] adds d8389d726 round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...] 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 (870189094) \ N -- N -- N refs/changes/34/42034/2 (d8389d726) 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 | 638 -------------------------------------------------- round-robin-notify.sh | 224 ------------------ 2 files changed, 862 deletions(-) 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