Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/81/39381/1 updated (22f2b2cb2 -> fc795ae23)

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/81/39381/1 in repository toolchain/jenkins-scripts. discards 22f2b2cb2 round-robin.sh: Fix sed command adds fc795ae23 round-robin.sh: Fix sed command 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 (22f2b2cb2) \ N -- N -- N refs/changes/81/39381/1 (fc795ae23) 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/81/39181/1 updated (509182803 -> 03218719b)

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/81/39181/1 in repository toolchain/jenkins-scripts. discards 509182803 round-robin-bisect.sh: Fix shellcheck warning discards 263e03a8a tcwg_gnu-build.sh: Ignore progressions in bisections adds 03218719b tcwg_gnu-build.sh: Ignore progressions in bisections 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 (509182803) \ N -- N -- N refs/changes/81/39181/1 (03218719b) 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 | 782 -------------------------------------------------- 1 file changed, 782 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/81/38381/3 updated (04fa208c2 -> f3611090f)

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/81/38381/3 in repository toolchain/jenkins-scripts. discards 04fa208c2 tcwg-update-llvmbot-containers.sh: Move all flang bots into p [...] adds f3611090f tcwg-update-llvmbot-containers.sh: Move all flang bots into p [...] 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 (04fa208c2) \ N -- N -- N refs/changes/81/38381/3 (f3611090f) 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/81/38381/2 updated (a3c8994e9 -> 5d9354bbc)

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/81/38381/2 in repository toolchain/jenkins-scripts. discards a3c8994e9 tcwg-update-llvmbot-containers.sh: Move all flang bots into p [...] adds 5d9354bbc tcwg-update-llvmbot-containers.sh: Move all flang bots into p [...] 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 (a3c8994e9) \ N -- N -- N refs/changes/81/38381/2 (5d9354bbc) 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/81/38381/1 updated (cde370918 -> 1e00e4f29)

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/81/38381/1 in repository toolchain/jenkins-scripts. discards cde370918 tcwg-update-llvmbot-containers.sh: Move all flang bots into p [...] new 1e00e4f29 tcwg-update-llvmbot-containers.sh: Move all flang bots into p [...] 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 (cde370918) \ N -- N -- N refs/changes/81/38381/1 (1e00e4f29) 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/81/38081/1 updated (8b0c0798d -> b820ccf1e)

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/81/38081/1 in repository toolchain/jenkins-scripts. discards 8b0c0798d abe-bisect.sh: Fix typo adds b820ccf1e abe-bisect.sh: Fix typo 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 (8b0c0798d) \ N -- N -- N refs/changes/81/38081/1 (b820ccf1e) 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/81/37381/1 updated (6374b0313 -> a6872cd29)

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/81/37381/1 in repository toolchain/jenkins-scripts. discards 6374b0313 Docker image pull: And one more fix adds a6872cd29 Docker image pull: And one more fix 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 (6374b0313) \ N -- N -- N refs/changes/81/37381/1 (a6872cd29) 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/81/35781/9 updated (ddfc89f27 -> 529ce9ecc)

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/81/35781/9 in repository toolchain/jenkins-scripts. discards ddfc89f27 tcwg-cleanup-stale-results.sh: New script to delete stale ben [...] new 529ce9ecc tcwg-cleanup-stale-results.sh: New script to delete stale ben [...] 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 (ddfc89f27) \ N -- N -- N refs/changes/81/35781/9 (529ce9ecc) 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/81/35781/8 updated (dfaaf2441 -> e787354f2)

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/81/35781/8 in repository toolchain/jenkins-scripts. discards dfaaf2441 tcwg-cleanup-stale-results.sh: New script to delete stale ben [...] adds e787354f2 tcwg-cleanup-stale-results.sh: New script to delete stale ben [...] 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 (dfaaf2441) \ N -- N -- N refs/changes/81/35781/8 (e787354f2) 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/81/35781/7 updated (9f3f03fb8 -> 559764f6a)

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/81/35781/7 in repository toolchain/jenkins-scripts. discards 9f3f03fb8 tcwg-cleanup-stale-results.sh: New script to delete stale ben [...] adds 559764f6a tcwg-cleanup-stale-results.sh: New script to delete stale ben [...] 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 (9f3f03fb8) \ N -- N -- N refs/changes/81/35781/7 (559764f6a) 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