Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/35/35435/1 updated (10177183c -> 0692a0fbb)

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/35/35435/1 in repository toolchain/jenkins-scripts. discards 10177183c round-robin-bisect.sh: Fix shellcheck warnings discards f83ab343d round-robin*.sh: Pass component URL alongside component branches adds 0692a0fbb round-robin*.sh: Pass component URL alongside component branches 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 (10177183c) \ N -- N -- N refs/changes/35/35435/1 (0692a0fbb) 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 | 655 -------------------------------------------------- 1 file changed, 655 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/35/33635/1 updated (24accba5b -> 56149cc96)

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/35/33635/1 in repository toolchain/jenkins-scripts. discards 24accba5b tcwg_bmk-build.sh: Fix fallout from generalizing cflags handling adds 56149cc96 tcwg_bmk-build.sh: Fix fallout from generalizing cflags handling 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 (24accba5b) \ N -- N -- N refs/changes/35/33635/1 (56149cc96) 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/35/32735/3 updated (2b6a0349c -> ec4e13723)

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/35/32735/3 in repository toolchain/jenkins-scripts. discards 2b6a0349c start-container-docker.sh: Create workspace lock only when ... adds ec4e13723 start-container-docker.sh: Create workspace lock only when ... 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 (2b6a0349c) \ N -- N -- N refs/changes/35/32735/3 (ec4e13723) 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/35/32735/2 updated (e0ec512fb -> 8b2a55de1)

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/35/32735/2 in repository toolchain/jenkins-scripts. discards e0ec512fb start-container-docker.sh: Handle locks on remote host new 8b2a55de1 start-container-docker.sh: Handle locks on remote host 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 (e0ec512fb) \ N -- N -- N refs/changes/35/32735/2 (8b2a55de1) 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/35/32735/1 updated (f688f4da9 -> 3993acbe8)

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/35/32735/1 in repository toolchain/jenkins-scripts. discards f688f4da9 start-container-docker.sh: Handle locks on remote host new 3993acbe8 start-container-docker.sh: Handle locks on remote host 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 (f688f4da9) \ N -- N -- N refs/changes/35/32735/1 (3993acbe8) 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/35/32435/1 updated (c497f1155 -> b73b29c9d)

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/35/32435/1 in repository toolchain/jenkins-scripts. discards c497f1155 tcwg_gnu-build.sh: Set rr[components] correctly adds b73b29c9d tcwg_gnu-build.sh: Set rr[components] correctly 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 (c497f1155) \ N -- N -- N refs/changes/35/32435/1 (b73b29c9d) 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/35/31235/1 updated (fba29c39b -> dbff5e3b6)

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/35/31235/1 in repository toolchain/jenkins-scripts. discards fba29c39b jenkins-helpers.sh: Avoid inconsistent state of remote by re- [...] adds dbff5e3b6 jenkins-helpers.sh: Avoid inconsistent state of remote by re- [...] 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 (fba29c39b) \ N -- N -- N refs/changes/35/31235/1 (dbff5e3b6) 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/35/30435/1 updated (e39d16ca9 -> 14a713fe5)

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/35/30435/1 in repository toolchain/jenkins-scripts. discards e39d16ca9 tcwg_bmk-build.sh: Support llvm adds 14a713fe5 tcwg_bmk-build.sh: Support llvm 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 (e39d16ca9) \ N -- N -- N refs/changes/35/30435/1 (14a713fe5) 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/35/29835/3 updated (a85440a3d -> 88364b40f)

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/35/29835/3 in repository toolchain/jenkins-scripts. discards a85440a3d jenkins-helpers: Enable clone_or_update_repo to fetch single branch adds 88364b40f jenkins-helpers: Enable clone_or_update_repo to fetch single branch 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 (a85440a3d) \ N -- N -- N refs/changes/35/29835/3 (88364b40f) 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/35/29835/2 updated (5ab2892b3 -> 07d768eac)

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/35/29835/2 in repository toolchain/jenkins-scripts. discards 5ab2892b3 jenkins-helpers: Enable clone_or_update_repo to fetch single branch adds 07d768eac jenkins-helpers: Enable clone_or_update_repo to fetch single branch 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 (5ab2892b3) \ N -- N -- N refs/changes/35/29835/2 (07d768eac) 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