Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/33/45533/10 updated (b9b8ec69a -> e47515cf2)

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/33/45533/10 in repository toolchain/jenkins-scripts. discards b9b8ec69a jenkins-helpers.sh (run_step): Make more robust and preserve [...] adds e47515cf2 jenkins-helpers.sh (run_step): Make more robust and preserve [...] 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 (b9b8ec69a) \ N -- N -- N refs/changes/33/45533/10 (e47515cf2) 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/33/45533/1 updated (b4718e2e1 -> ca57946c0)

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/33/45533/1 in repository toolchain/jenkins-scripts. discards b4718e2e1 jenkins-helpers.sh (run_step): Make more robust and preserve [...] new ca57946c0 jenkins-helpers.sh (run_step): Make more robust and preserve [...] 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 (b4718e2e1) \ N -- N -- N refs/changes/33/45533/1 (ca57946c0) 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/33/45333/1 updated (275d067c0 -> b6850e320)

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/33/45333/1 in repository toolchain/jenkins-scripts. discards 275d067c0 round-robin-notify.sh (print_jira_card_key): Fix discards b097c94dc pw-apply.sh,pw-report.sh: Improve feedback for failed-to-appl [...] adds b6850e320 pw-apply.sh,pw-report.sh: Improve feedback for failed-to-appl [...] 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 (275d067c0) \ N -- N -- N refs/changes/33/45333/1 (b6850e320) 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 | 410 ------------- round-robin-bisect.sh | 653 -------------------- round-robin-notify.sh | 1549 ----------------------------------------------- 3 files changed, 2612 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.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/33/44633/9 updated (5a5b272b1 -> 8f3799dd7)

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/33/44633/9 in repository toolchain/jenkins-scripts. discards 5a5b272b1 round-robin-rewrite.sh: Merge into round-robin-baseline.sh adds 8f3799dd7 round-robin-rewrite.sh: Merge into round-robin-baseline.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 (5a5b272b1) \ N -- N -- N refs/changes/33/44633/9 (8f3799dd7) 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/33/44633/8 updated (e3e5107ca -> 8f3799dd7)

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/33/44633/8 in repository toolchain/jenkins-scripts. discards e3e5107ca round-robin-rewrite.sh: Merge into round-robin-baseline.sh adds 8f3799dd7 round-robin-rewrite.sh: Merge into round-robin-baseline.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 (e3e5107ca) \ N -- N -- N refs/changes/33/44633/8 (8f3799dd7) 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/33/44633/7 updated (2b4633645 -> 8f3799dd7)

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/33/44633/7 in repository toolchain/jenkins-scripts. discards 2b4633645 round-robin-rewrite.sh: Merge into round-robin-baseline.sh adds 8f3799dd7 round-robin-rewrite.sh: Merge into round-robin-baseline.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 (2b4633645) \ N -- N -- N refs/changes/33/44633/7 (8f3799dd7) 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/33/44633/6 updated (2a2036f4a -> e4d6cd007)

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/33/44633/6 in repository toolchain/jenkins-scripts. discards 2a2036f4a round-robin-rewrite.sh: Merge into round-robin-baseline.sh adds e4d6cd007 round-robin-rewrite.sh: Merge into round-robin-baseline.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 (2a2036f4a) \ N -- N -- N refs/changes/33/44633/6 (e4d6cd007) 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/33/44633/5 updated (4fec41fbd -> 773380a16)

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/33/44633/5 in repository toolchain/jenkins-scripts. discards 4fec41fbd round-robin-rewrite.sh: Merge into round-robin-baseline.sh new 773380a16 round-robin-rewrite.sh: Merge into round-robin-baseline.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 (4fec41fbd) \ N -- N -- N refs/changes/33/44633/5 (773380a16) 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/33/44633/4 updated (a40a9c226 -> 6334c9cc6)

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/33/44633/4 in repository toolchain/jenkins-scripts. discards a40a9c226 round-robin-rewrite.sh: Merge into round-robin-baseline.sh new 6334c9cc6 round-robin-rewrite.sh: Merge into round-robin-baseline.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 (a40a9c226) \ N -- N -- N refs/changes/33/44633/4 (6334c9cc6) 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/33/44633/3 updated (1acd69ad4 -> dabb66cca)

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/33/44633/3 in repository toolchain/jenkins-scripts. discards 1acd69ad4 round-robin-rewrite.sh: Merge into round-robin-baseline.sh new dabb66cca round-robin-rewrite.sh: Merge into round-robin-baseline.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 (1acd69ad4) \ N -- N -- N refs/changes/33/44633/3 (dabb66cca) 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