Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/28/39928/1 updated (591f25a85 -> a9ccc54b4)

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/39928/1 in repository toolchain/jenkins-scripts. discards 591f25a85 round-robin-bisect.sh: Do not cd to $current_project directory discards 6f07ff7bd tcwg-start-container.sh: Yet another fix to gracefull stoppin [...] adds a9ccc54b4 tcwg-start-container.sh: Yet another fix to gracefull stoppin [...] 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 (591f25a85) \ N -- N -- N refs/changes/28/39928/1 (a9ccc54b4) 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 | 848 -------------------------------------------------- 1 file changed, 848 deletions(-) delete mode 100755 round-robin-bisect.sh -- 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/28/39428/2 updated (fe7677432 -> 863ebd542)

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/39428/2 in repository toolchain/jenkins-scripts. discards fe7677432 tcwg-update-llvmbot-containers.sh: Move LLDB bots back to normal adds 863ebd542 tcwg-update-llvmbot-containers.sh: Move LLDB bots back to normal 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 (fe7677432) \ N -- N -- N refs/changes/28/39428/2 (863ebd542) 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/28/39428/1 updated (b50d9c5c4 -> 11358ba0e)

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/39428/1 in repository toolchain/jenkins-scripts. discards b50d9c5c4 tcwg-update-llvmbot-containers.sh: Move LLDB bots back to normal new 11358ba0e tcwg-update-llvmbot-containers.sh: Move LLDB bots back to normal 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 (b50d9c5c4) \ N -- N -- N refs/changes/28/39428/1 (11358ba0e) 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/28/39228/1 updated (f9df16b38 -> 4e5c5a3af)

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/39228/1 in repository toolchain/jenkins-scripts. discards f9df16b38 tcwg_gnu-build.sh: Add type_of_test:check_gcc adds 4e5c5a3af tcwg_gnu-build.sh: Add type_of_test:check_gcc 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 (f9df16b38) \ N -- N -- N refs/changes/28/39228/1 (4e5c5a3af) 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/28/39128/3 updated (770c63761 -> e05299a8d)

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/39128/3 in repository toolchain/jenkins-scripts. discards 770c63761 tcwg_gnu-build.sh: Compare results using validate_failures.py adds e05299a8d tcwg_gnu-build.sh: Compare results using validate_failures.py 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 (770c63761) \ N -- N -- N refs/changes/28/39128/3 (e05299a8d) 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/28/39128/2 updated (f4175d0c9 -> 4ef6be5aa)

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/39128/2 in repository toolchain/jenkins-scripts. discards f4175d0c9 tcwg_gnu-build.sh: Compare results using validate_failures.py adds 4ef6be5aa tcwg_gnu-build.sh: Compare results using validate_failures.py 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 (f4175d0c9) \ N -- N -- N refs/changes/28/39128/2 (4ef6be5aa) 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/28/39128/1 updated (66b3dea24 -> 06ebb788e)

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/39128/1 in repository toolchain/jenkins-scripts. discards 66b3dea24 tcwg_gnu-build.sh: Compare results using validate_failures.py adds 06ebb788e tcwg_gnu-build.sh: Compare results using validate_failures.py 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 (66b3dea24) \ N -- N -- N refs/changes/28/39128/1 (06ebb788e) 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/28/37828/1 updated (fe96f71c2 -> 9effa5550)

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/37828/1 in repository toolchain/jenkins-scripts. discards fe96f71c2 tcwg-benchmark-bare.sh: Start run container on the local machine new 9effa5550 tcwg-benchmark-bare.sh: Start run container on the local machine 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 (fe96f71c2) \ N -- N -- N refs/changes/28/37828/1 (9effa5550) 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/28/33928/1 updated (69a164db1 -> ef8bf2200)

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/33928/1 in repository toolchain/jenkins-scripts. discards 69a164db1 tcwg_bmk-build.sh: Convert $benchmarks to bash array adds ef8bf2200 tcwg_bmk-build.sh: Convert $benchmarks to bash array 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 (69a164db1) \ N -- N -- N refs/changes/28/33928/1 (ef8bf2200) 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/28/32628/1 updated (f0dcb6f10 -> d50e51abe)

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/32628/1 in repository toolchain/jenkins-scripts. discards f0dcb6f10 tcwg_bmk-build.sh: Build benchmarks for Thumb2 adds d50e51abe tcwg_bmk-build.sh: Build benchmarks for Thumb2 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 (f0dcb6f10) \ N -- N -- N refs/changes/28/32628/1 (d50e51abe) 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