Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/48/30048/3 updated (20471672b -> 01a8fd750)

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/48/30048/3 in repository toolchain/jenkins-scripts. discards 20471672b jenkins-helpers.sh: Improve remote_exec adds 01a8fd750 jenkins-helpers.sh: Improve remote_exec 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 (20471672b) \ N -- N -- N refs/changes/48/30048/3 (01a8fd750) 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/48/30048/2 updated (c334bdc13 -> a85b02c56)

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/48/30048/2 in repository toolchain/jenkins-scripts. discards c334bdc13 jenkins-helpers.sh: Improve remote_exec adds a85b02c56 jenkins-helpers.sh: Improve remote_exec 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 (c334bdc13) \ N -- N -- N refs/changes/48/30048/2 (a85b02c56) 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/48/30048/1 updated (8be2369c7 -> ae457aeef)

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/48/30048/1 in repository toolchain/jenkins-scripts. discards 8be2369c7 jenkins-helpers.sh: Improve remote_exec adds ae457aeef jenkins-helpers.sh: Improve remote_exec 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 (8be2369c7) \ N -- N -- N refs/changes/48/30048/1 (ae457aeef) 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/48/29848/4 updated (c2e46ed53 -> 5ece393b1)

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/48/29848/4 in repository toolchain/jenkins-scripts. discards c2e46ed53 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop. discards de4067753 tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 4d14e7df1 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards 5df7279a1 tcwg_kernel-bisect.sh: Update reproduction instructions discards f08731e2a tcwg_kernel-bisect.sh: Re-arrange code. discards 0b630c5a8 tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards dd49fbf78 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 06f786a9a tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 73d563e61 tcwg_kernel-bisect.sh: Remove --confirm_failure option discards 22b7df0e9 round-robin.sh: Improve comment. adds 5ece393b1 round-robin.sh: Improve comment. 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 (c2e46ed53) \ N -- N -- N refs/changes/48/29848/4 (5ece393b1) 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 | 360 -------------------------------------------------- 1 file changed, 360 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/48/29848/3 updated (2c05acb7e -> 5ece393b1)

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/48/29848/3 in repository toolchain/jenkins-scripts. discards 2c05acb7e tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop. discards e7e9db0bc tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 1c7b10ca8 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards f6b6c0455 tcwg_kernel-bisect.sh: Update reproduction instructions discards 8c175bda7 tcwg_kernel-bisect.sh: Re-arrange code. discards 845244b56 tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards c29f90f4f tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 8a8898023 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 73d563e61 tcwg_kernel-bisect.sh: Remove --confirm_failure option discards 22b7df0e9 round-robin.sh: Improve comment. adds 5ece393b1 round-robin.sh: Improve comment. 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 (2c05acb7e) \ N -- N -- N refs/changes/48/29848/3 (5ece393b1) 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 | 360 -------------------------------------------------- 1 file changed, 360 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/48/29848/2 updated (4ec06d572 -> 964a669f3)

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/48/29848/2 in repository toolchain/jenkins-scripts. discards 4ec06d572 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop. discards 9af7bec1f tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 391f1ac72 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards c80275f2d tcwg_kernel-bisect.sh: Update reproduction instructions discards 8de2d5a52 tcwg_kernel-bisect.sh: Re-arrange code. discards 96da56ccf tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards bdae8b950 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards d772207c8 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 82ffe64ac tcwg_kernel-bisect.sh: Remove --confirm_failure option discards bedb5b13e round-robin.sh: Improve comment. adds 964a669f3 round-robin.sh: Improve comment. 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 (4ec06d572) \ N -- N -- N refs/changes/48/29848/2 (964a669f3) 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 | 360 -------------------------------------------------- 1 file changed, 360 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/48/29848/1 updated (b0d88f505 -> 1efd682eb)

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/48/29848/1 in repository toolchain/jenkins-scripts. discards b0d88f505 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop. discards 91096a80b tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 4f760ce34 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards b8866f36d tcwg_kernel-bisect.sh: Update reproduction instructions discards 10812bcaa tcwg_kernel-bisect.sh: Re-arrange code. discards 10370ddfa tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards 582dd8440 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 883bead54 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards f484163fb tcwg_kernel-bisect.sh: Remove --confirm_failure option discards c20e3014f round-robin.sh: Improve comment. adds 1efd682eb round-robin.sh: Improve comment. 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 (b0d88f505) \ N -- N -- N refs/changes/48/29848/1 (1efd682eb) 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 | 360 -------------------------------------------------- 1 file changed, 360 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/48/29748/2 updated (1ac7c43e3 -> b9f53f461)

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/48/29748/2 in repository toolchain/jenkins-scripts. discards 1ac7c43e3 round-robin.sh: Fix typo in reset_artifacts adds b9f53f461 round-robin.sh: Fix typo in reset_artifacts 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 (1ac7c43e3) \ N -- N -- N refs/changes/48/29748/2 (b9f53f461) 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/48/29748/1 updated (64c579631 -> 826349346)

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/48/29748/1 in repository toolchain/jenkins-scripts. discards 64c579631 round-robin.sh: Fix typo in reset_artifacts new 826349346 round-robin.sh: Fix typo in reset_artifacts 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 (64c579631) \ N -- N -- N refs/changes/48/29748/1 (826349346) 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/48/29448/2 updated (197d82d9d -> c09cf0bf7)

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/48/29448/2 in repository toolchain/jenkins-scripts. discards 197d82d9d tcwg_kernel-build.sh: Move round-robin helpers to round-robin.sh adds c09cf0bf7 tcwg_kernel-build.sh: Move round-robin helpers to round-robin.sh 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 (197d82d9d) \ N -- N -- N refs/changes/48/29448/2 (c09cf0bf7) 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