Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/53/32753/1 updated (54c70b206 -> 62967f9ec)

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/53/32753/1 in repository toolchain/jenkins-scripts. discards 54c70b206 tcwg_bmk-build.sh: Increase tolerance for speed benchmarking adds 62967f9ec tcwg_bmk-build.sh: Increase tolerance for speed benchmarking 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 (54c70b206) \ N -- N -- N refs/changes/53/32753/1 (62967f9ec) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/32453/2 updated (ce73fcdf4 -> 5248dfdb9)

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/53/32453/2 in repository toolchain/jenkins-scripts. discards ce73fcdf4 start-container-docker.sh: Make ssh verbose in more cases adds 5248dfdb9 start-container-docker.sh: Make ssh verbose in more cases 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 (ce73fcdf4) \ N -- N -- N refs/changes/53/32453/2 (5248dfdb9) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/32453/1 updated (962ef3bc7 -> b35017a9b)

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/53/32453/1 in repository toolchain/jenkins-scripts. discards 962ef3bc7 start-container-docker.sh: Make ssh verbose in more cases new b35017a9b start-container-docker.sh: Make ssh verbose in more cases 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 (962ef3bc7) \ N -- N -- N refs/changes/53/32453/1 (b35017a9b) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/30053/4 updated (742e147d4 -> 25ff7117a)

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/53/30053/4 in repository toolchain/jenkins-scripts. discards 742e147d4 tcwg-benchmark.sh: Ssh directly to the benchmark board. adds 25ff7117a tcwg-benchmark.sh: Ssh directly to the benchmark board. 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 (742e147d4) \ N -- N -- N refs/changes/53/30053/4 (25ff7117a) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/30053/3 updated (d5b1296d5 -> f7c6d30ec)

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/53/30053/3 in repository toolchain/jenkins-scripts. discards d5b1296d5 tcwg-benchmark.sh: Ssh directly to the benchmark board. new f7c6d30ec tcwg-benchmark.sh: Ssh directly to the benchmark board. 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 (d5b1296d5) \ N -- N -- N refs/changes/53/30053/3 (f7c6d30ec) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/30053/2 updated (28ddc0622 -> 39b3cf2a0)

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/53/30053/2 in repository toolchain/jenkins-scripts. discards 28ddc0622 tcwg-benchmark.sh: Ssh directly to the benchmark board. new 39b3cf2a0 tcwg-benchmark.sh: Ssh directly to the benchmark board. 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 (28ddc0622) \ N -- N -- N refs/changes/53/30053/2 (39b3cf2a0) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/30053/1 updated (c5c924908 -> 7e4bbc372)

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/53/30053/1 in repository toolchain/jenkins-scripts. discards c5c924908 tcwg-benchmark.sh: Ssh directly to the benchmark board. new 7e4bbc372 tcwg-benchmark.sh: Ssh directly to the benchmark board. 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 (c5c924908) \ N -- N -- N refs/changes/53/30053/1 (7e4bbc372) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/29353/2 updated (eedf431a5 -> 4be80ada2)

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/53/29353/2 in repository toolchain/jenkins-scripts. discards eedf431a5 tcwg_kernel-bisect.sh: Add useful suffixes to artifacts/build [...] discards 5c0fc7c61 tcwg_kernel-bisect.sh: Make sure artifacts contain "bad" logs discards 828a6b581 tcwg_kernel-bisect.sh: Tidy up artifacts discards 85425e8c4 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml discards e333a4e3d tcwg-update-llvmbot-containers.sh: New job script adds 4be80ada2 tcwg-update-llvmbot-containers.sh: New job script 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 (eedf431a5) \ N -- N -- N refs/changes/53/29353/2 (4be80ada2) 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 | 262 -------------------------------------------------- 1 file changed, 262 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/53/29353/1 updated (88c1ee7cc -> ce794b80b)

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/53/29353/1 in repository toolchain/jenkins-scripts. discards 88c1ee7cc tcwg_kernel-bisect.sh: Add useful suffixes to artifacts/build [...] discards ba317a795 tcwg_kernel-bisect.sh: Make sure artifacts contain "bad" logs discards 2ac388259 tcwg_kernel-bisect.sh: Tidy up artifacts discards 3cb94b357 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml discards a5c2d2aa0 tcwg_kernel-bisect.sh: Send emails only on successful bisects. discards 148291018 tcwg-update-llvmbot-containers.sh: New job script adds ce794b80b tcwg-update-llvmbot-containers.sh: New job script 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 (88c1ee7cc) \ N -- N -- N refs/changes/53/29353/1 (ce794b80b) 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 | 262 -------------------------------------------------- 1 file changed, 262 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/47152/1 updated (16224dc0f -> 14efb7fed)

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/52/47152/1 in repository toolchain/jenkins-scripts. discards 16224dc0f tcwg_chromium-build.sh: do not fetch with --no-history adds 14efb7fed tcwg_chromium-build.sh: do not fetch with --no-history 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 (16224dc0f) \ N -- N -- N refs/changes/52/47152/1 (14efb7fed) 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.

11 months, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024