Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/96/38496/3 updated (4635551e1 -> 22e99a1ae)

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/96/38496/3 in repository toolchain/jenkins-scripts. discards 4635551e1 tcwg-update-llvmbot-containers.sh: Document number of Buildkite bots adds 22e99a1ae tcwg-update-llvmbot-containers.sh: Document number of Buildkite bots 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 (4635551e1) \ N -- N -- N refs/changes/96/38496/3 (22e99a1ae) 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/96/38496/2 updated (cea22a889 -> e9bba970e)

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/96/38496/2 in repository toolchain/jenkins-scripts. discards cea22a889 tcwg-update-llvmbot-containers.sh: Document number of Buildkite bots new e9bba970e tcwg-update-llvmbot-containers.sh: Document number of Buildkite bots 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 (cea22a889) \ N -- N -- N refs/changes/96/38496/2 (e9bba970e) 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/96/38496/1 updated (bdda6aaf3 -> cd135e0ef)

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/96/38496/1 in repository toolchain/jenkins-scripts. discards bdda6aaf3 tcwg-update-llvmbot-containers.sh: Document number of Buildkite bots new cd135e0ef tcwg-update-llvmbot-containers.sh: Document number of Buildkite bots 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 (bdda6aaf3) \ N -- N -- N refs/changes/96/38496/1 (cd135e0ef) 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/96/32996/2 updated (6c08897ef -> d5b379766)

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/96/32996/2 in repository toolchain/jenkins-scripts. discards 6c08897ef tcwg-benchmark.sh: Run board setup outside of container adds d5b379766 tcwg-benchmark.sh: Run board setup outside of container 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 (6c08897ef) \ N -- N -- N refs/changes/96/32996/2 (d5b379766) 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/96/32996/1 updated (e66f9f7be -> e8310ab1e)

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/96/32996/1 in repository toolchain/jenkins-scripts. discards e66f9f7be tcwg-benchmark.sh: Run board setup outside of container new e8310ab1e tcwg-benchmark.sh: Run board setup outside of container 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 (e66f9f7be) \ N -- N -- N refs/changes/96/32996/1 (e8310ab1e) 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/96/31696/1 updated (dddda8e6d -> 2eb8276d8)

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/96/31696/1 in repository toolchain/jenkins-scripts. discards dddda8e6d tcwg-benchmark-results.sh: Call perfdatadir2csv.sh with --verbose adds 2eb8276d8 tcwg-benchmark-results.sh: Call perfdatadir2csv.sh with --verbose 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 (dddda8e6d) \ N -- N -- N refs/changes/96/31696/1 (2eb8276d8) 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/96/29996/1 updated (72ad765b6 -> 103d30bbb)

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/96/29996/1 in repository toolchain/jenkins-scripts. discards 72ad765b6 tcwg_bmk-build: Do not hardcode HW type in results_id new 103d30bbb tcwg_bmk-build: Do not hardcode HW type in results_id 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 (72ad765b6) \ N -- N -- N refs/changes/96/29996/1 (103d30bbb) 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/96/29496/3 updated (f8df5f942 -> ebacb5dec)

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/96/29496/3 in repository toolchain/jenkins-scripts. discards f8df5f942 tcwg_kernel-bisect.sh: Update email recepients. discards c296d92b3 tcwg_kernel-bisect.sh: Improve mail contents discards bcaedfc5d tcwg_kernel-build.sh: Add new --mode reproduce adds ebacb5dec tcwg_kernel-build.sh: Add new --mode reproduce 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 (f8df5f942) \ N -- N -- N refs/changes/96/29496/3 (ebacb5dec) 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: tcwg_kernel-bisect.sh | 281 -------------------------------------------------- 1 file changed, 281 deletions(-) delete mode 100755 tcwg_kernel-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/96/29496/2 updated (b3eede7b8 -> 26d81849a)

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/96/29496/2 in repository toolchain/jenkins-scripts. discards b3eede7b8 tcwg_kernel-bisect.sh: Update email recepients. discards 4e1379d56 tcwg_kernel-build.sh: Add new --mode reproduce new 26d81849a tcwg_kernel-build.sh: Add new --mode reproduce 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 (b3eede7b8) \ N -- N -- N refs/changes/96/29496/2 (26d81849a) 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: tcwg_kernel-bisect.sh | 277 -------------------------------------------------- 1 file changed, 277 deletions(-) delete mode 100755 tcwg_kernel-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/96/29496/1 updated (166da49f2 -> 0b77d2c65)

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/96/29496/1 in repository toolchain/jenkins-scripts. discards 166da49f2 tcwg_kernel-bisect.sh: Update email recepients. discards c6ae4ab69 tcwg_kernel-build.sh: Add new --mode reproduce new 0b77d2c65 tcwg_kernel-build.sh: Add new --mode reproduce 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 (166da49f2) \ N -- N -- N refs/changes/96/29496/1 (0b77d2c65) 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: tcwg_kernel-bisect.sh | 277 -------------------------------------------------- 1 file changed, 277 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- 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