Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/99/44699/2 updated (657a7d24b -> 41bb9b1e2)

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/99/44699/2 in repository toolchain/jenkins-scripts. discards 657a7d24b llvm-vect-metric.diff: update patch due to llvm source change adds 41bb9b1e2 llvm-vect-metric.diff: update patch due to llvm source change 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 (657a7d24b) \ N -- N -- N refs/changes/99/44699/2 (41bb9b1e2) 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/99/44699/1 updated (0ff5ab9c1 -> 1231bf6f3)

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/99/44699/1 in repository toolchain/jenkins-scripts. discards 0ff5ab9c1 llvm-vect-metric.diff: update patch due to llvm source change new 1231bf6f3 llvm-vect-metric.diff: update patch due to llvm source change 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 (0ff5ab9c1) \ N -- N -- N refs/changes/99/44699/1 (1231bf6f3) 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/99/44299/1 updated (bc88bce5f -> 823758ad0)

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/99/44299/1 in repository toolchain/jenkins-scripts. discards bc88bce5f round-robin.sh (build_abe): Add --check_patch option adds 823758ad0 round-robin.sh (build_abe): Add --check_patch option 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 (bc88bce5f) \ N -- N -- N refs/changes/99/44299/1 (823758ad0) 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/99/43599/4 updated (9cc425dd4 -> 3cbcb3c7b)

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/99/43599/4 in repository toolchain/jenkins-scripts. discards 9cc425dd4 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] adds 3cbcb3c7b round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] 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 (9cc425dd4) \ N -- N -- N refs/changes/99/43599/4 (3cbcb3c7b) 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/99/43599/3 updated (1ef0a5de0 -> 4dbf9d09c)

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/99/43599/3 in repository toolchain/jenkins-scripts. discards 1ef0a5de0 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] new 4dbf9d09c round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] 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 (1ef0a5de0) \ N -- N -- N refs/changes/99/43599/3 (4dbf9d09c) 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/99/43599/2 updated (2ad664114 -> d76e14860)

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/99/43599/2 in repository toolchain/jenkins-scripts. discards 2ad664114 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] new d76e14860 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] 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 (2ad664114) \ N -- N -- N refs/changes/99/43599/2 (d76e14860) 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/99/43599/1 updated (c32f79239 -> 595574145)

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/99/43599/1 in repository toolchain/jenkins-scripts. discards c32f79239 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] new 595574145 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...] 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 (c32f79239) \ N -- N -- N refs/changes/99/43599/1 (595574145) 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/99/43299/1 updated (d6ad73e6b -> 36c3ed028)

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/99/43299/1 in repository toolchain/jenkins-scripts. discards d6ad73e6b tcwg-generate-source-cache.sh: Re-clone repos on update failures adds 36c3ed028 tcwg-generate-source-cache.sh: Re-clone repos on update failures 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 (d6ad73e6b) \ N -- N -- N refs/changes/99/43299/1 (36c3ed028) 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/99/42799/1 updated (ef69d8c91 -> 008eefe8b)

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/99/42799/1 in repository toolchain/jenkins-scripts. discards ef69d8c91 round-robin.sh: Workaround containers running out of RAM on a [...] adds 008eefe8b round-robin.sh: Workaround containers running out of RAM on a [...] 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 (ef69d8c91) \ N -- N -- N refs/changes/99/42799/1 (008eefe8b) 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/99/42399/4 updated (81192f02f -> b3c161e71)

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/99/42399/4 in repository toolchain/jenkins-scripts. discards 81192f02f tcwg_aosp-build.sh: Build AOSP using shadow wrappers adds b3c161e71 tcwg_aosp-build.sh: Build AOSP using shadow wrappers 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 (81192f02f) \ N -- N -- N refs/changes/99/42399/4 (b3c161e71) 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