Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/09/43409/2 updated (065b1e57a -> 25012fc40)

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/09/43409/2 in repository toolchain/jenkins-scripts. discards 065b1e57a tcwg_bmk-build.sh: Handle new code-size and code-vect configurations adds 25012fc40 tcwg_bmk-build.sh: Handle new code-size and code-vect configurations 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 (065b1e57a) \ N -- N -- N refs/changes/09/43409/2 (25012fc40) 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/09/43409/1 updated (5d4d6a12f -> 3d7a97324)

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/09/43409/1 in repository toolchain/jenkins-scripts. discards 5d4d6a12f tcwg_bmk-build.sh: Handle new code-size and code-vect configurations new 3d7a97324 tcwg_bmk-build.sh: Handle new code-size and code-vect configurations 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 (5d4d6a12f) \ N -- N -- N refs/changes/09/43409/1 (3d7a97324) 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/09/43309/1 updated (b9301c93d -> 74fa6b600)

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/09/43309/1 in repository toolchain/jenkins-scripts. discards b9301c93d tcwg_bmk-build.sh: Move assert now that output-bmk-results.py [...] adds 74fa6b600 tcwg_bmk-build.sh: Move assert now that output-bmk-results.py [...] 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 (b9301c93d) \ N -- N -- N refs/changes/09/43309/1 (74fa6b600) 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/09/43109/2 updated (4752cf5ce -> bbae4eed6)

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/09/43109/2 in repository toolchain/jenkins-scripts. discards 4752cf5ce Use spec2017_rate to speed up VECT and SVE jobs. adds bbae4eed6 Use spec2017_rate to speed up VECT and SVE 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 (4752cf5ce) \ N -- N -- N refs/changes/09/43109/2 (bbae4eed6) 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/09/43109/1 updated (7454a6c39 -> d8e38782c)

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/09/43109/1 in repository toolchain/jenkins-scripts. discards 7454a6c39 Use spec2017_rate to speed up VECT and SVE jobs. new d8e38782c Use spec2017_rate to speed up VECT and SVE 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 (7454a6c39) \ N -- N -- N refs/changes/09/43109/1 (d8e38782c) 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/09/42109/1 updated (c4afa2575 -> ca2bb5187)

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/09/42109/1 in repository toolchain/jenkins-scripts. discards c4afa2575 dashboard-generate-squad.sh: Quick workaround to see further adds ca2bb5187 dashboard-generate-squad.sh: Quick workaround to see further 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 (c4afa2575) \ N -- N -- N refs/changes/09/42109/1 (ca2bb5187) 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/09/39609/1 updated (13381e7b2 -> 7065835cf)

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/09/39609/1 in repository toolchain/jenkins-scripts. discards 13381e7b2 build_llvm_package.bat: Update cmake settings adds 7065835cf build_llvm_package.bat: Update cmake settings 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 (13381e7b2) \ N -- N -- N refs/changes/09/39609/1 (7065835cf) 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/09/38909/2 updated (d0384cef5 -> 8426e45c0)

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/09/38909/2 in repository toolchain/jenkins-scripts. discards d0384cef5 tcwg-update-llvmbot-containers.sh: Update bot worker names adds 8426e45c0 tcwg-update-llvmbot-containers.sh: Update bot worker names 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 (d0384cef5) \ N -- N -- N refs/changes/09/38909/2 (8426e45c0) 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/09/38909/1 updated (45004d888 -> 606e955c7)

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/09/38909/1 in repository toolchain/jenkins-scripts. discards 45004d888 tcwg-update-llvmbot-containers.sh: Update bot worker names new 606e955c7 tcwg-update-llvmbot-containers.sh: Update bot worker names 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 (45004d888) \ N -- N -- N refs/changes/09/38909/1 (606e955c7) 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/09/37909/1 updated (2ca586ae8 -> 29d744096)

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/09/37909/1 in repository toolchain/jenkins-scripts. discards 2ca586ae8 tcwg-benchmark-bare.sh: Add $USER user in container only if n [...] adds 29d744096 tcwg-benchmark-bare.sh: Add $USER user in container only if n [...] 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 (2ca586ae8) \ N -- N -- N refs/changes/09/37909/1 (29d744096) 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024