Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/05/44205/2 updated (22caef4d3 -> 6d8c0b0df)

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/05/44205/2 in repository toolchain/jenkins-scripts. discards 22caef4d3 jenkins-helpers.sh: Fix get_baseline_manifest adds 6d8c0b0df jenkins-helpers.sh: Fix get_baseline_manifest 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 (22caef4d3) \ N -- N -- N refs/changes/05/44205/2 (6d8c0b0df) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/44205/1 updated (65eec6f91 -> 87cc1e4cf)

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/05/44205/1 in repository toolchain/jenkins-scripts. discards 65eec6f91 jenkins-helpers.sh: Fix get_baseline_manifest new 87cc1e4cf jenkins-helpers.sh: Fix get_baseline_manifest 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 (65eec6f91) \ N -- N -- N refs/changes/05/44205/1 (87cc1e4cf) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/43505/3 updated (13006f152 -> 0c9854c26)

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/05/43505/3 in repository toolchain/jenkins-scripts. discards 13006f152 tcwg_aosp-build.sh: Use AOSP superproject adds 0c9854c26 tcwg_aosp-build.sh: Use AOSP superproject 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 (13006f152) \ N -- N -- N refs/changes/05/43505/3 (0c9854c26) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/43505/2 updated (4aa5f1e0d -> ed7c9e25b)

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/05/43505/2 in repository toolchain/jenkins-scripts. discards 4aa5f1e0d tcwg_aosp-build.sh: Use AOSP superproject new ed7c9e25b tcwg_aosp-build.sh: Use AOSP superproject 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 (4aa5f1e0d) \ N -- N -- N refs/changes/05/43505/2 (ed7c9e25b) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/43505/1 updated (b1416ab08 -> 348059b28)

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/05/43505/1 in repository toolchain/jenkins-scripts. discards b1416ab08 tcwg_aosp-build.sh: Use AOSP superproject new 348059b28 tcwg_aosp-build.sh: Use AOSP superproject 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 (b1416ab08) \ N -- N -- N refs/changes/05/43505/1 (348059b28) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/41605/2 updated (ac883f26a -> 78644e27b)

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/05/41605/2 in repository toolchain/jenkins-scripts. discards ac883f26a round-robin.sh: prepare_abe(): Get Abe's repo and branch from [...] adds 78644e27b round-robin.sh: prepare_abe(): Get Abe's repo and branch from [...] 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 (ac883f26a) \ N -- N -- N refs/changes/05/41605/2 (78644e27b) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/41605/1 updated (9b3486d70 -> 5db7a3a93)

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/05/41605/1 in repository toolchain/jenkins-scripts. discards 9b3486d70 round-robin.sh: prepare_abe(): Get Abe's repo and branch from [...] new 5db7a3a93 round-robin.sh: prepare_abe(): Get Abe's repo and branch from [...] 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 (9b3486d70) \ N -- N -- N refs/changes/05/41605/1 (5db7a3a93) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/39805/1 updated (3f1cc8d93 -> f823ace19)

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/05/39805/1 in repository toolchain/jenkins-scripts. discards 3f1cc8d93 round-robin-bisect.sh: Move regression reports to per-project lists discards ae3ef5bd5 Use linaro-local/vect-metric/master for vect-metric patch. adds f823ace19 Use linaro-local/vect-metric/master for vect-metric patch. 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 (3f1cc8d93) \ N -- N -- N refs/changes/05/39805/1 (f823ace19) 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 | 839 -------------------------------------------------- 1 file changed, 839 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/39605/1 updated (fa99393be -> f16651270)

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/05/39605/1 in repository toolchain/jenkins-scripts. discards fa99393be build_llvm_package.bat: Add MSVC compatibility setting adds f16651270 build_llvm_package.bat: Add MSVC compatibility setting 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 (fa99393be) \ N -- N -- N refs/changes/05/39605/1 (f16651270) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/05/39305/3 updated (dd67a90ec -> 3995067e9)

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/05/39305/3 in repository toolchain/jenkins-scripts. discards dd67a90ec tcwg_bmk-build.sh: Cleanup adds 3995067e9 tcwg_bmk-build.sh: Cleanup 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 (dd67a90ec) \ N -- N -- N refs/changes/05/39305/3 (3995067e9) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024