Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/22/32722/4 updated (98b2b577a -> 355e0aa91)

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/22/32722/4 in repository toolchain/jenkins-scripts. discards 98b2b577a start-container-docker.sh: Kill container of the previous [ab [...] adds 355e0aa91 start-container-docker.sh: Kill container of the previous [ab [...] 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 (98b2b577a) \ N -- N -- N refs/changes/22/32722/4 (355e0aa91) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/32722/3 updated (f849451ba -> 772d15e65)

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/22/32722/3 in repository toolchain/jenkins-scripts. discards f849451ba start-container-docker.sh: Kill container of the previous [ab [...] new 772d15e65 start-container-docker.sh: Kill container of the previous [ab [...] 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 (f849451ba) \ N -- N -- N refs/changes/22/32722/3 (772d15e65) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/32722/2 updated (be4e3dede -> 727b3ebc5)

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/22/32722/2 in repository toolchain/jenkins-scripts. discards be4e3dede start-container-docker.sh: Kill container of the previous [ab [...] new 727b3ebc5 start-container-docker.sh: Kill container of the previous [ab [...] 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 (be4e3dede) \ N -- N -- N refs/changes/22/32722/2 (727b3ebc5) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/32722/1 updated (87248ac61 -> 9b3a6dcab)

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/22/32722/1 in repository toolchain/jenkins-scripts. discards 87248ac61 start-container-docker.sh: Kill container of the previous [ab [...] new 9b3a6dcab start-container-docker.sh: Kill container of the previous [ab [...] 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 (87248ac61) \ N -- N -- N refs/changes/22/32722/1 (9b3a6dcab) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/31222/2 updated (bcaa24503 -> ed71fa478)

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/22/31222/2 in repository toolchain/jenkins-scripts. discards bcaa24503 tcwg_*-build.sh: Don't require repo urls when we don't need them adds ed71fa478 tcwg_*-build.sh: Don't require repo urls when we don't need them 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 (bcaa24503) \ N -- N -- N refs/changes/22/31222/2 (ed71fa478) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/31222/1 updated (5310ddef4 -> a854580f5)

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/22/31222/1 in repository toolchain/jenkins-scripts. discards 5310ddef4 tcwg_*-build.sh: Don't require repo urls when we don't need them adds a854580f5 tcwg_*-build.sh: Don't require repo urls when we don't need them 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 (5310ddef4) \ N -- N -- N refs/changes/22/31222/1 (a854580f5) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/29822/2 updated (3fc310049 -> a4061179b)

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/22/29822/2 in repository toolchain/jenkins-scripts. discards 3fc310049 tcwg-benchmark.sh: Add support for :parallelize parameter in [...] adds a4061179b tcwg-benchmark.sh: Add support for :parallelize parameter in [...] 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 (3fc310049) \ N -- N -- N refs/changes/22/29822/2 (a4061179b) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/29822/1 updated (959de3882 -> 5b65e6154)

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/22/29822/1 in repository toolchain/jenkins-scripts. discards 959de3882 tcwg-benchmark.sh: Add support for :parallelize parameter in [...] new 5b65e6154 tcwg-benchmark.sh: Add support for :parallelize parameter in [...] 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 (959de3882) \ N -- N -- N refs/changes/22/29822/1 (5b65e6154) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/29622/2 updated (fa931307a -> de5d2bdf3)

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/22/29622/2 in repository toolchain/jenkins-scripts. discards fa931307a tcwg_kernel-bisect.sh: Send emails with useful info when bise [...] discards f238c3d99 tcwg_kernel-build.sh: Make sure manifest declares variables i [...] adds de5d2bdf3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...] 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 (fa931307a) \ N -- N -- N refs/changes/22/29622/2 (de5d2bdf3) 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 | 317 -------------------------------------------------- 1 file changed, 317 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/29622/1 updated (801040254 -> 75c9233c3)

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/22/29622/1 in repository toolchain/jenkins-scripts. discards 801040254 tcwg_kernel-bisect.sh: Send emails with useful info when bise [...] discards 38a883d64 tcwg_kernel-build.sh: Make sure manifest declares variables i [...] adds 75c9233c3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...] 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 (801040254) \ N -- N -- N refs/changes/22/29622/1 (75c9233c3) 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 | 317 -------------------------------------------------- 1 file changed, 317 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, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024