Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/73/36073/2 updated (9b14091d6 -> 0c9566dd1)

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/73/36073/2 in repository toolchain/jenkins-scripts. discards 9b14091d6 jenkins-helpers.sh: Add "failsafe" parameter to print_host_for_node adds 0c9566dd1 jenkins-helpers.sh: Add "failsafe" parameter to print_host_for_node 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 (9b14091d6) \ N -- N -- N refs/changes/73/36073/2 (0c9566dd1) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/36073/1 updated (968110fbb -> e6f64df8b)

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/73/36073/1 in repository toolchain/jenkins-scripts. discards 968110fbb jenkins-helpers.sh: Add "failsafe" parameter to print_host_for_node new e6f64df8b jenkins-helpers.sh: Add "failsafe" parameter to print_host_for_node 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 (968110fbb) \ N -- N -- N refs/changes/73/36073/1 (e6f64df8b) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/35073/1 updated (5d1684771 -> 1c14116e0)

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/73/35073/1 in repository toolchain/jenkins-scripts. discards 5d1684771 Revert "tcwg_bmk-build.sh: Use parallel8x4 and parallel8x1 bm [...] adds 1c14116e0 Revert "tcwg_bmk-build.sh: Use parallel8x4 and parallel8x1 bm [...] 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 (5d1684771) \ N -- N -- N refs/changes/73/35073/1 (1c14116e0) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/33473/4 updated (81d2bd4a8 -> 516412a23)

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/73/33473/4 in repository toolchain/jenkins-scripts. discards 81d2bd4a8 tcwg-llvm-release: Get test-release.sh from GitHub adds 516412a23 tcwg-llvm-release: Get test-release.sh from GitHub 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 (81d2bd4a8) \ N -- N -- N refs/changes/73/33473/4 (516412a23) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/33473/3 updated (47f8c10df -> bc44d6349)

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/73/33473/3 in repository toolchain/jenkins-scripts. discards 47f8c10df tcwg-llvm-release: Get test-release.sh from GitHub new bc44d6349 tcwg-llvm-release: Get test-release.sh from GitHub 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 (47f8c10df) \ N -- N -- N refs/changes/73/33473/3 (bc44d6349) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/33473/2 updated (b14d199de -> e683230cf)

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/73/33473/2 in repository toolchain/jenkins-scripts. discards b14d199de tcwg-llvm-release: Get test-release.sh from GitHub new e683230cf tcwg-llvm-release: Get test-release.sh from GitHub 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 (b14d199de) \ N -- N -- N refs/changes/73/33473/2 (e683230cf) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/33473/1 updated (444be3e58 -> 837f03042)

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/73/33473/1 in repository toolchain/jenkins-scripts. discards 444be3e58 tcwg-llvm-release: Get test-release.sh from GitHub new 837f03042 tcwg-llvm-release: Get test-release.sh from GitHub 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 (444be3e58) \ N -- N -- N refs/changes/73/33473/1 (837f03042) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/29773/2 updated (267741394 -> f11f7df2e)

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/73/29773/2 in repository toolchain/jenkins-scripts. discards 267741394 tcwg_kernel-build.sh: Stabilize kernel build for ccache adds f11f7df2e tcwg_kernel-build.sh: Stabilize kernel build for ccache 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 (267741394) \ N -- N -- N refs/changes/73/29773/2 (f11f7df2e) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/29773/1 updated (7ff4b7dde -> 37ba4da14)

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/73/29773/1 in repository toolchain/jenkins-scripts. discards 7ff4b7dde tcwg_kernel-build.sh: Stabilize kernel build for ccache new 37ba4da14 tcwg_kernel-build.sh: Stabilize kernel build for ccache 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 (7ff4b7dde) \ N -- N -- N refs/changes/73/29773/1 (37ba4da14) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/73/29573/3 updated (432f1088f -> 301303024)

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/73/29573/3 in repository toolchain/jenkins-scripts. discards 432f1088f tcwg-benchmark.sh: Determine toolchain_type when toolchain_ur [...] adds 301303024 tcwg-benchmark.sh: Determine toolchain_type when toolchain_ur [...] 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 (432f1088f) \ N -- N -- N refs/changes/73/29573/3 (301303024) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024