Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/15/41215/2 updated (7d57c673e -> 386cdc4a1)

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/15/41215/2 in repository toolchain/jenkins-scripts. discards 7d57c673e tcwg-benchmark.sh: Enable bmk host for tk1 and tx1 adds 386cdc4a1 tcwg-benchmark.sh: Enable bmk host for tk1 and tx1 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 (7d57c673e) \ N -- N -- N refs/changes/15/41215/2 (386cdc4a1) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/41215/1 updated (97d0e639e -> 1a70a8c51)

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/15/41215/1 in repository toolchain/jenkins-scripts. discards 97d0e639e tcwg-benchmark.sh: Enable bmk host for tk1 and tx1 new 1a70a8c51 tcwg-benchmark.sh: Enable bmk host for tk1 and tx1 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 (97d0e639e) \ N -- N -- N refs/changes/15/41215/1 (1a70a8c51) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/38715/1 updated (2745b7362 -> 0ac82da97)

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/15/38715/1 in repository toolchain/jenkins-scripts. discards 2745b7362 tcwg-update-llvmbot-containers.sh: Test a single libcxx bot on jade adds 0ac82da97 tcwg-update-llvmbot-containers.sh: Test a single libcxx bot on jade 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 (2745b7362) \ N -- N -- N refs/changes/15/38715/1 (0ac82da97) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/36115/4 updated (c1856649f -> 53aa8815e)

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/15/36115/4 in repository toolchain/jenkins-scripts. discards c1856649f tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal adds 53aa8815e tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal 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 (c1856649f) \ N -- N -- N refs/changes/15/36115/4 (53aa8815e) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/36115/3 updated (ea6115dbf -> 9381c3137)

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/15/36115/3 in repository toolchain/jenkins-scripts. discards ea6115dbf tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal new 9381c3137 tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal 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 (ea6115dbf) \ N -- N -- N refs/changes/15/36115/3 (9381c3137) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/36115/2 updated (8a4cd6430 -> 4294fa8f3)

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/15/36115/2 in repository toolchain/jenkins-scripts. discards 8a4cd6430 tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal new 4294fa8f3 tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal 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 (8a4cd6430) \ N -- N -- N refs/changes/15/36115/2 (4294fa8f3) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/36115/1 updated (7063d725a -> 2807cd55b)

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/15/36115/1 in repository toolchain/jenkins-scripts. discards 7063d725a tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal new 2807cd55b tcwg-benchmark-bare.sh: New script to run benchmarks on bare-metal 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 (7063d725a) \ N -- N -- N refs/changes/15/36115/1 (2807cd55b) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/34015/1 updated (31272ab9a -> 190adca10)

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/15/34015/1 in repository toolchain/jenkins-scripts. discards 31272ab9a tcwg_bmk-build.sh: Update display tag of benchmark jobs adds 190adca10 tcwg_bmk-build.sh: Update display tag of benchmark jobs 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 (31272ab9a) \ N -- N -- N refs/changes/15/34015/1 (190adca10) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/33515/3 updated (b21add9f4 -> 38927876b)

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/15/33515/3 in repository toolchain/jenkins-scripts. discards b21add9f4 tcwg_kernel-build.sh: Implement rr[breakup_updated_components] hook adds 38927876b tcwg_kernel-build.sh: Implement rr[breakup_updated_components] hook 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 (b21add9f4) \ N -- N -- N refs/changes/15/33515/3 (38927876b) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/33515/2 updated (5347ae2e4 -> d344b5df5)

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/15/33515/2 in repository toolchain/jenkins-scripts. discards 5347ae2e4 tcwg_kernel-build.sh: Implement rr[breakup_updated_components] hook new d344b5df5 tcwg_kernel-build.sh: Implement rr[breakup_updated_components] hook 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 (5347ae2e4) \ N -- N -- N refs/changes/15/33515/2 (d344b5df5) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024