Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/15/33515/1 updated (e155a7592 -> 2c0fa0cc9)

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/15/33515/1 in repository toolchain/jenkins-scripts. discards e155a7592 tcwg_kernel-build.sh: Implement rr[breakup_updated_components] hook new 2c0fa0cc9 tcwg_kernel-build.sh: Implement rr[breakup_updated_components] hook 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 (e155a7592) \ N -- N -- N refs/changes/15/33515/1 (2c0fa0cc9) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/31015/2 updated (5d572aec9 -> 09e11e589)

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/15/31015/2 in repository toolchain/jenkins-scripts. discards 5d572aec9 tcwg-generate-source-cache.sh: Use run_with_timeout_and_retry [...] adds 09e11e589 tcwg-generate-source-cache.sh: Use run_with_timeout_and_retry [...] 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 (5d572aec9) \ N -- N -- N refs/changes/15/31015/2 (09e11e589) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/15/31015/1 updated (e51715a73 -> 8bf818f69)

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/15/31015/1 in repository toolchain/jenkins-scripts. discards e51715a73 tcwg-generate-source-cache.sh: Use run_with_timeout_and_retry [...] new 8bf818f69 tcwg-generate-source-cache.sh: Use run_with_timeout_and_retry [...] 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 (e51715a73) \ N -- N -- N refs/changes/15/31015/1 (8bf818f69) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/47314/1 updated (5a70191c0 -> f85564de1)

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/14/47314/1 in repository toolchain/jenkins-scripts. discards 5a70191c0 round-robin.sh,round-robin-bisect.sh: Change component_reques [...] adds f85564de1 round-robin.sh,round-robin-bisect.sh: Change component_reques [...] 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 (5a70191c0) \ N -- N -- N refs/changes/14/47314/1 (f85564de1) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/47014/3 updated (10c8b9c03 -> 8d366473c)

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/14/47014/3 in repository toolchain/jenkins-scripts. discards 10c8b9c03 pw-apply.sh: Support running with --pw_token "" adds 8d366473c pw-apply.sh: Support running with --pw_token "" 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 (10c8b9c03) \ N -- N -- N refs/changes/14/47014/3 (8d366473c) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/47014/2 updated (41271ecaa -> fc1e94536)

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/14/47014/2 in repository toolchain/jenkins-scripts. discards 41271ecaa pw-apply.sh: Support running with --pw_token "" adds fc1e94536 pw-apply.sh: Support running with --pw_token "" 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 (41271ecaa) \ N -- N -- N refs/changes/14/47014/2 (fc1e94536) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/47014/1 updated (c873bb614 -> 1016bd1a2)

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/14/47014/1 in repository toolchain/jenkins-scripts. discards c873bb614 pw-apply.sh: Support running with --pw_token "" adds 1016bd1a2 pw-apply.sh: Support running with --pw_token "" 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 (c873bb614) \ N -- N -- N refs/changes/14/47014/1 (1016bd1a2) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/46814/1 updated (5f297dada -> d5a82b9a0)

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/14/46814/1 in repository toolchain/jenkins-scripts. discards 5f297dada tcwg-cleanup-stale-results.sh: Sort the list for a working co [...] adds d5a82b9a0 tcwg-cleanup-stale-results.sh: Sort the list for a working co [...] 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 (5f297dada) \ N -- N -- N refs/changes/14/46814/1 (d5a82b9a0) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/46314/1 updated (53997f16a -> 3a373f284)

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/14/46314/1 in repository toolchain/jenkins-scripts. discards 53997f16a tcwg_bmk-build.sh: Increase version for fujitsu jobs adds 3a373f284 tcwg_bmk-build.sh: Increase version for fujitsu jobs 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 (53997f16a) \ N -- N -- N refs/changes/14/46314/1 (3a373f284) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/14/45714/1 updated (89876ce78 -> e498d7bff)

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/14/45714/1 in repository toolchain/jenkins-scripts. discards 89876ce78 round-robin-notify.sh (update_jira_card): Improve handling of [...] discards f51ae4d13 round-robin-notify.sh (jira cards): Do not update closed cards discards e764a676c round-robin-notify.sh (gnu_print_result): Add links to useful logs discards 60d3d8798 round-robin-notify.sh (gnu_print_result): Improve --long version discards 17d36081f round-robin-notify.sh (print_mail_body): Add more ways to con [...] discards 03877dae5 jenkins-helpers.sh (describe_sha1): Improve describes for bin [...] adds e498d7bff jenkins-helpers.sh (describe_sha1): Improve describes for bin [...] 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 (89876ce78) \ N -- N -- N refs/changes/14/45714/1 (e498d7bff) 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: round-robin-baseline.sh | 524 -------------- round-robin-bisect.sh | 678 ------------------ round-robin-notify.sh | 1789 ----------------------------------------------- 3 files changed, 2991 deletions(-) delete mode 100755 round-robin-baseline.sh delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024