Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/93/42793/1 updated (2441cbd78 -> 925d67194)

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/93/42793/1 in repository toolchain/jenkins-scripts. discards 2441cbd78 tcwg-update-llvmbot-containers: Move clang-native-arm-lnt-per [...] new 925d67194 tcwg-update-llvmbot-containers: Move clang-native-arm-lnt-per [...] 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 (2441cbd78) \ N -- N -- N refs/changes/93/42793/1 (925d67194) 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/93/42393/3 updated (e81bd4486 -> b18b0b248)

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/93/42393/3 in repository toolchain/jenkins-scripts. discards e81bd4486 wrappers/shadow-cc.sh: Use generate_shadow_rsp() adds b18b0b248 wrappers/shadow-cc.sh: Use generate_shadow_rsp() 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 (e81bd4486) \ N -- N -- N refs/changes/93/42393/3 (b18b0b248) 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/93/42393/2 updated (8b78e848a -> 55bc05c37)

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/93/42393/2 in repository toolchain/jenkins-scripts. discards 8b78e848a wrappers/shadow-cc.sh: Use generate_shadow_rsp() adds 55bc05c37 wrappers/shadow-cc.sh: Use generate_shadow_rsp() 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 (8b78e848a) \ N -- N -- N refs/changes/93/42393/2 (55bc05c37) 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/93/42393/1 updated (66ebb6ccc -> 82a18f90d)

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/93/42393/1 in repository toolchain/jenkins-scripts. discards 66ebb6ccc wrappers/shadow-cc.sh: Use generate_shadow_rsp() adds 82a18f90d wrappers/shadow-cc.sh: Use generate_shadow_rsp() 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 (66ebb6ccc) \ N -- N -- N refs/changes/93/42393/1 (82a18f90d) 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/93/40993/1 updated (cbed5a7a6 -> ea5baec76)

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/93/40993/1 in repository toolchain/jenkins-scripts. discards cbed5a7a6 tcwg_bmk-build.sh: Replace comparison in compare_results with [...] new ea5baec76 tcwg_bmk-build.sh: Replace comparison in compare_results with [...] 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 (cbed5a7a6) \ N -- N -- N refs/changes/93/40993/1 (ea5baec76) 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/93/40893/1 updated (dbf55f8dd -> bb18d2314)

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/93/40893/1 in repository toolchain/jenkins-scripts. discards dbf55f8dd tcwg-stale-rr-jobs : enhance automatic detection adds bb18d2314 tcwg-stale-rr-jobs : enhance automatic detection 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 (dbf55f8dd) \ N -- N -- N refs/changes/93/40893/1 (bb18d2314) 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/93/40393/4 updated (d51cb3a69 -> 1ea00be39)

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/93/40393/4 in repository toolchain/jenkins-scripts. discards d51cb3a69 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 bu [...] adds 1ea00be39 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 bu [...] 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 (d51cb3a69) \ N -- N -- N refs/changes/93/40393/4 (1ea00be39) 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/93/40393/3 updated (99e424162 -> 12dad17c0)

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/93/40393/3 in repository toolchain/jenkins-scripts. discards 99e424162 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 bu [...] new 12dad17c0 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 bu [...] 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 (99e424162) \ N -- N -- N refs/changes/93/40393/3 (12dad17c0) 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/93/40393/2 updated (5587ac7f2 -> 9fa940b66)

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/93/40393/2 in repository toolchain/jenkins-scripts. discards 5587ac7f2 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 bu [...] new 9fa940b66 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 bu [...] 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 (5587ac7f2) \ N -- N -- N refs/changes/93/40393/2 (9fa940b66) 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/93/40393/1 updated (ad1b9b1ec -> 2c87c4031)

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/93/40393/1 in repository toolchain/jenkins-scripts. discards ad1b9b1ec tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 to [...] new 2c87c4031 tcwg-update-llvmbot-containers.sh: Move a tk1 to the Armv7 to [...] 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 (ad1b9b1ec) \ N -- N -- N refs/changes/93/40393/1 (2c87c4031) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024