Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/45/29745/2 updated (18ccb2ae9 -> 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/45/29745/2 in repository toolchain/jenkins-scripts. discards 18ccb2ae9 tcwg_kernel-bisect.sh: Update handling of build-name discards dee30002a tcwg_kernel-bisect.sh: Fix handling of manifest files 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 (18ccb2ae9) \ N -- N -- N refs/changes/45/29745/2 (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: tcwg_kernel-bisect.sh | 377 -------------------------------------------------- 1 file changed, 377 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/29745/1 updated (c738cd59e -> 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/45/29745/1 in repository toolchain/jenkins-scripts. discards c738cd59e tcwg_kernel-bisect.sh: Update handling of build-name discards dee30002a tcwg_kernel-bisect.sh: Fix handling of manifest files 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 (c738cd59e) \ N -- N -- N refs/changes/45/29745/1 (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: tcwg_kernel-bisect.sh | 377 -------------------------------------------------- 1 file changed, 377 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/45/29445/1 updated (ff8464263 -> 784ddf170)

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/45/29445/1 in repository toolchain/jenkins-scripts. discards ff8464263 tcwg_kernel-build.sh: Fix typo. adds 784ddf170 tcwg_kernel-build.sh: Fix typo. 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 (ff8464263) \ N -- N -- N refs/changes/45/29445/1 (784ddf170) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/47044/2 updated (959772c50 -> cf1ac666b)

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/44/47044/2 in repository toolchain/jenkins-scripts. discards 959772c50 tcwg-update-lnt-results.sh: Detect inconsistent history and s [...] adds cf1ac666b tcwg-update-lnt-results.sh: Detect inconsistent history and s [...] 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 (959772c50) \ N -- N -- N refs/changes/44/47044/2 (cf1ac666b) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/47044/1 updated (a831b1f67 -> 5b01cbbb4)

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/44/47044/1 in repository toolchain/jenkins-scripts. discards a831b1f67 tcwg-update-lnt-results.sh: Detect inconsistent history and s [...] new 5b01cbbb4 tcwg-update-lnt-results.sh: Detect inconsistent history and s [...] 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 (a831b1f67) \ N -- N -- N refs/changes/44/47044/1 (5b01cbbb4) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/46944/5 updated (e88365fed -> 4d7da6638)

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/44/46944/5 in repository toolchain/jenkins-scripts. discards e88365fed jenkins-helpers.sh: Add get_component_dir adds 4d7da6638 jenkins-helpers.sh: Add get_component_dir 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 (e88365fed) \ N -- N -- N refs/changes/44/46944/5 (4d7da6638) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/46944/4 updated (8a4a00d25 -> 3b0af72f4)

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/44/46944/4 in repository toolchain/jenkins-scripts. discards 8a4a00d25 jenkins-helpers.sh: Add get_current_git_dir new 3b0af72f4 jenkins-helpers.sh: Add get_current_git_dir 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 (8a4a00d25) \ N -- N -- N refs/changes/44/46944/4 (3b0af72f4) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/46944/3 updated (53899ddd2 -> fcba75244)

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/44/46944/3 in repository toolchain/jenkins-scripts. discards 53899ddd2 jenkins-helpers.sh: Add get_current_git_dir adds fcba75244 jenkins-helpers.sh: Add get_current_git_dir 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 (53899ddd2) \ N -- N -- N refs/changes/44/46944/3 (fcba75244) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/46944/2 updated (d31bbb1b1 -> 2fb63fa18)

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/44/46944/2 in repository toolchain/jenkins-scripts. discards d31bbb1b1 jenkins-helpers.sh: Add get_current_git_dir adds 2fb63fa18 jenkins-helpers.sh: Add get_current_git_dir 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 (d31bbb1b1) \ N -- N -- N refs/changes/44/46944/2 (2fb63fa18) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/44/46944/1 updated (1cf28ba04 -> 1eb3149e9)

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/44/46944/1 in repository toolchain/jenkins-scripts. discards 1cf28ba04 (WIP) jenkins-helpers.sh: Add artifacts/git/<dep>_dir file adds 1eb3149e9 (WIP) jenkins-helpers.sh: Add artifacts/git/<dep>_dir file 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 (1cf28ba04) \ N -- N -- N refs/changes/44/46944/1 (1eb3149e9) 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, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024