Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/08/29908/1 updated (496d0d8cf -> 4f8d0638d)

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/08/29908/1 in repository toolchain/jenkins-scripts. discards 496d0d8cf tcwg_kernel-bisect.sh: Don't force $reproduce_bisect==true in [...] discards 564022aa3 tcwg_kernel-bisect.sh: Better handle regressions in merge commits discards 6de8c98b4 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests adds 4f8d0638d tcwg_kernel-bisect.sh: Avoid absolute paths in manifests 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 (496d0d8cf) \ N -- N -- N refs/changes/08/29908/1 (4f8d0638d) 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 | 397 -------------------------------------------------- 1 file changed, 397 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/08/29408/1 updated (7ab55d812 -> 18532311f)

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/08/29408/1 in repository toolchain/jenkins-scripts. discards 7ab55d812 tcwg_kernel-bisect.sh: Update to use new format of "@@" inclu [...] discards 508e1a638 jenkins-helpers.sh, tcwg-update-snapshots_ref.sh: Add tcwg-sq [...] adds 18532311f jenkins-helpers.sh, tcwg-update-snapshots_ref.sh: Add tcwg-sq [...] 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 (7ab55d812) \ N -- N -- N refs/changes/08/29408/1 (18532311f) 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 | 271 -------------------------------------------------- 1 file changed, 271 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/07/47107/6 updated (65f0e8256 -> 9053fc39e)

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/07/47107/6 in repository toolchain/jenkins-scripts. discards 65f0e8256 tcwg-update-lnt-results.sh: Update to import inside LNT container adds 9053fc39e tcwg-update-lnt-results.sh: Update to import inside LNT 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 (65f0e8256) \ N -- N -- N refs/changes/07/47107/6 (9053fc39e) 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/07/47107/5 updated (40ee2934b -> 0c5a8b0d7)

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/07/47107/5 in repository toolchain/jenkins-scripts. discards 40ee2934b tcwg-update-lnt-results.sh: Update to import inside LNT container adds 0c5a8b0d7 tcwg-update-lnt-results.sh: Update to import inside LNT 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 (40ee2934b) \ N -- N -- N refs/changes/07/47107/5 (0c5a8b0d7) 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/07/47107/4 updated (b27ad5914 -> 92c40b769)

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/07/47107/4 in repository toolchain/jenkins-scripts. discards b27ad5914 tcwg-update-lnt-results.sh: Update to import inside LNT container new 92c40b769 tcwg-update-lnt-results.sh: Update to import inside LNT 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 (b27ad5914) \ N -- N -- N refs/changes/07/47107/4 (92c40b769) 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/07/47107/3 updated (843a864a7 -> 2078b218b)

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/07/47107/3 in repository toolchain/jenkins-scripts. discards 843a864a7 tcwg-update-lnt-results.sh: Update to import inside LNT container new 2078b218b tcwg-update-lnt-results.sh: Update to import inside LNT 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 (843a864a7) \ N -- N -- N refs/changes/07/47107/3 (2078b218b) 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/07/47107/2 updated (c53069dce -> b427be762)

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/07/47107/2 in repository toolchain/jenkins-scripts. discards c53069dce tcwg-update-lnt-results.sh: Update to import inside LNT container new b427be762 tcwg-update-lnt-results.sh: Update to import inside LNT 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 (c53069dce) \ N -- N -- N refs/changes/07/47107/2 (b427be762) 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/07/47107/1 updated (df4515b98 -> a667cec74)

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/07/47107/1 in repository toolchain/jenkins-scripts. discards df4515b98 tcwg-update-lnt-results.sh: Update to import inside LNT container new a667cec74 tcwg-update-lnt-results.sh: Update to import inside LNT 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 (df4515b98) \ N -- N -- N refs/changes/07/47107/1 (a667cec74) 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/07/46907/2 updated (1353b16c6 -> b4f68c2c6)

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/07/46907/2 in repository toolchain/jenkins-scripts. discards 1353b16c6 update_components_revs.sh: Rename deps_bra into deps_branch adds b4f68c2c6 update_components_revs.sh: Rename deps_bra into deps_branch 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 (1353b16c6) \ N -- N -- N refs/changes/07/46907/2 (b4f68c2c6) 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/07/46907/1 updated (0af28e3ac -> 30c9b3ee9)

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/07/46907/1 in repository toolchain/jenkins-scripts. discards 0af28e3ac update_components_revs.sh: Rename deps_bra into deps_branch new 30c9b3ee9 update_components_revs.sh: Rename deps_bra into deps_branch 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 (0af28e3ac) \ N -- N -- N refs/changes/07/46907/1 (30c9b3ee9) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024