Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/20/42120/1 updated (702201b02 -> d2004c162)

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/20/42120/1 in repository toolchain/jenkins-scripts. discards 702201b02 tcwg-llvm-release.sh: Use LLVM unwinder on armv7 new d2004c162 tcwg-llvm-release.sh: Use LLVM unwinder on armv7 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 (702201b02) \ N -- N -- N refs/changes/20/42120/1 (d2004c162) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/41920/2 updated (2c7388cb3 -> 0409f928b)

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/20/41920/2 in repository toolchain/jenkins-scripts. discards 2c7388cb3 jenkins-helpers.sh: Make assert() and assert_with_msg quiter adds 0409f928b jenkins-helpers.sh: Make assert() and assert_with_msg quiter 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 (2c7388cb3) \ N -- N -- N refs/changes/20/41920/2 (0409f928b) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/41920/1 updated (520b24822 -> 1706adcd6)

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/20/41920/1 in repository toolchain/jenkins-scripts. discards 520b24822 jenkins-helpers.sh: Make assert() and assert_with_msg quiter adds 1706adcd6 jenkins-helpers.sh: Make assert() and assert_with_msg quiter 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 (520b24822) \ N -- N -- N refs/changes/20/41920/1 (1706adcd6) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/41320/1 updated (cefa0588d -> 7ee692c7c)

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/20/41320/1 in repository toolchain/jenkins-scripts. discards cefa0588d tcwg-benchmark.sh: Wait for ssh server on port from .ssh/config adds 7ee692c7c tcwg-benchmark.sh: Wait for ssh server on port from .ssh/config 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 (cefa0588d) \ N -- N -- N refs/changes/20/41320/1 (7ee692c7c) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/40820/2 updated (d6b664564 -> ac20e4b05)

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/20/40820/2 in repository toolchain/jenkins-scripts. discards d6b664564 tcwg-benchmark-results.sh: Use nm-data-to-csv.py for obtaining size. adds ac20e4b05 tcwg-benchmark-results.sh: Use nm-data-to-csv.py for obtaining size. 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 (d6b664564) \ N -- N -- N refs/changes/20/40820/2 (ac20e4b05) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/40820/1 updated (0f74157dc -> c475e44ab)

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/20/40820/1 in repository toolchain/jenkins-scripts. discards 0f74157dc tcwg-benchmark-results.sh: Use nm-data-to-csv.py for obtaining size. new c475e44ab tcwg-benchmark-results.sh: Use nm-data-to-csv.py for obtaining size. 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 (0f74157dc) \ N -- N -- N refs/changes/20/40820/1 (c475e44ab) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/39720/1 updated (8ba1da4d4 -> fcf23878b)

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/20/39720/1 in repository toolchain/jenkins-scripts. discards 8ba1da4d4 tcwg_bmk-build.sh: Fix directory path adds fcf23878b tcwg_bmk-build.sh: Fix directory path 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 (8ba1da4d4) \ N -- N -- N refs/changes/20/39720/1 (fcf23878b) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/39220/1 updated (09808a78b -> ccf5fe35e)

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/20/39220/1 in repository toolchain/jenkins-scripts. discards 09808a78b round-robin-bisect.sh: Use gerrit to push to repos discards e2e53d0a2 jenkins-helpers.sh (git_init_linaro_local_remote): Add specia [...] adds ccf5fe35e jenkins-helpers.sh (git_init_linaro_local_remote): Add specia [...] 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 (09808a78b) \ N -- N -- N refs/changes/20/39220/1 (ccf5fe35e) 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 | 820 -------------------------------------------------- 1 file changed, 820 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/38920/1 updated (3b766b8fd -> 5c87f6abe)

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/20/38920/1 in repository toolchain/jenkins-scripts. discards 3b766b8fd tcwg-benchmark.sh: Fix shellcheck warning adds 5c87f6abe tcwg-benchmark.sh: Fix shellcheck warning 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 (3b766b8fd) \ N -- N -- N refs/changes/20/38920/1 (5c87f6abe) 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, 1 month

[toolchain/jenkins-scripts] reference refs/changes/20/35220/2 updated (dcc16d9ea -> bdc495570)

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/20/35220/2 in repository toolchain/jenkins-scripts. discards dcc16d9ea start-container-docker.sh: Only try to remove containers that exist adds bdc495570 start-container-docker.sh: Only try to remove containers that exist 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 (dcc16d9ea) \ N -- N -- N refs/changes/20/35220/2 (bdc495570) 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, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024