Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/23/32623/2 updated (0c66afd4a -> 08655c675)

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/23/32623/2 in repository toolchain/jenkins-scripts. discards 0c66afd4a start-container-docker.sh: More dry-run friendly adds 08655c675 start-container-docker.sh: More dry-run friendly 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 (0c66afd4a) \ N -- N -- N refs/changes/23/32623/2 (08655c675) 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/23/32623/1 updated (bad28a4e3 -> 78d93191e)

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/23/32623/1 in repository toolchain/jenkins-scripts. discards bad28a4e3 start-container-docker.sh: More dry-run friendly new 78d93191e start-container-docker.sh: More dry-run friendly 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 (bad28a4e3) \ N -- N -- N refs/changes/23/32623/1 (78d93191e) 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/23/30423/1 updated (b1a1dd00d -> 823226c91)

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/23/30423/1 in repository toolchain/jenkins-scripts. discards b1a1dd00d Merge branch 'master' into tcwg_bmk adds 823226c91 Merge branch 'master' into tcwg_bmk 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 (b1a1dd00d) \ N -- N -- N refs/changes/23/30423/1 (823226c91) 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/23/29723/4 updated (9bb3a33d9 -> 81b830c9b)

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/23/29723/4 in repository toolchain/jenkins-scripts. discards 9bb3a33d9 tcwg_kernel-bisect.sh: Add support to reproduce bisects. adds 81b830c9b tcwg_kernel-bisect.sh: Add support to reproduce bisects. 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 (9bb3a33d9) \ N -- N -- N refs/changes/23/29723/4 (81b830c9b) 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/23/29723/3 updated (15d6ee051 -> 4aac3d310)

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/23/29723/3 in repository toolchain/jenkins-scripts. discards 15d6ee051 tcwg_kernel-bisect.sh: Add support to reproduce bisects. new 4aac3d310 tcwg_kernel-bisect.sh: Add support to reproduce bisects. 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 (15d6ee051) \ N -- N -- N refs/changes/23/29723/3 (4aac3d310) 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/23/29723/2 updated (cae1f9360 -> 0473d9e8f)

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/23/29723/2 in repository toolchain/jenkins-scripts. discards cae1f9360 tcwg_kernel-bisect.sh: Add support to reproduce bisects. new 0473d9e8f tcwg_kernel-bisect.sh: Add support to reproduce bisects. 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 (cae1f9360) \ N -- N -- N refs/changes/23/29723/2 (0473d9e8f) 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/23/29723/1 updated (60d138622 -> 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/23/29723/1 in repository toolchain/jenkins-scripts. discards 60d138622 tcwg_kernel-bisect.sh: Add support to reproduce bisects. discards 1f4200537 tcwg_kernel-bisect.sh: Try harder to bisect linux-next failures discards 46c2519e1 tcwg_kernel-bisect.sh: Cleanup. 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 (60d138622) \ N -- N -- N refs/changes/23/29723/1 (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 | 341 -------------------------------------------------- 1 file changed, 341 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/23/29623/2 updated (46c2519e1 -> 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/23/29623/2 in repository toolchain/jenkins-scripts. discards 46c2519e1 tcwg_kernel-bisect.sh: Cleanup. 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 (46c2519e1) \ N -- N -- N refs/changes/23/29623/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 | 321 -------------------------------------------------- 1 file changed, 321 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/23/29623/1 updated (f294c203e -> 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/23/29623/1 in repository toolchain/jenkins-scripts. discards f294c203e tcwg_kernel-bisect.sh: Cleanup. 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 (f294c203e) \ N -- N -- N refs/changes/23/29623/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 | 321 -------------------------------------------------- 1 file changed, 321 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/46922/2 updated (fced5f16b -> 11851e1b9)

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/46922/2 in repository toolchain/jenkins-scripts. discards fced5f16b tcwg_chromium-build.sh,ci-autotest.sh: Externalize ci autotest adds 11851e1b9 tcwg_chromium-build.sh,ci-autotest.sh: Externalize ci autotest 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 (fced5f16b) \ N -- N -- N refs/changes/22/46922/2 (11851e1b9) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024