Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/01/30401/1 updated (5b5406a20 -> 0cd9a356c)

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/01/30401/1 in repository toolchain/jenkins-scripts. discards 5b5406a20 Trivial cleanups adds 0cd9a356c Trivial cleanups 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 (5b5406a20) \ N -- N -- N refs/changes/01/30401/1 (0cd9a356c) 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

[toolchain/jenkins-scripts] reference refs/changes/01/30301/3 updated (21cb97b04 -> 6be79ada6)

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/01/30301/3 in repository toolchain/jenkins-scripts. discards 21cb97b04 Set run_step_status to 0 before running step. adds 6be79ada6 Set run_step_status to 0 before running step. 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 (21cb97b04) \ N -- N -- N refs/changes/01/30301/3 (6be79ada6) 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

[toolchain/jenkins-scripts] reference refs/changes/01/30301/2 updated (cec105467 -> 568df6e84)

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/01/30301/2 in repository toolchain/jenkins-scripts. discards cec105467 Set run_step_status to 0 before running step. run_step_status [...] new 568df6e84 Set run_step_status to 0 before running step. run_step_status [...] 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 (cec105467) \ N -- N -- N refs/changes/01/30301/2 (568df6e84) 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

[toolchain/jenkins-scripts] reference refs/changes/01/30301/1 updated (4b07b8ce9 -> dfaec7c60)

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/01/30301/1 in repository toolchain/jenkins-scripts. discards 4b07b8ce9 Set run_step_status to 0 before running step. new dfaec7c60 Set run_step_status to 0 before running step. 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 (4b07b8ce9) \ N -- N -- N refs/changes/01/30301/1 (dfaec7c60) 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

[toolchain/jenkins-scripts] reference refs/changes/01/30101/1 updated (3943b4005 -> 2e2d22370)

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/01/30101/1 in repository toolchain/jenkins-scripts. discards 3943b4005 jenkins-helpers.sh: Use run_step_count as a 2-digit number adds 2e2d22370 jenkins-helpers.sh: Use run_step_count as a 2-digit number 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 (3943b4005) \ N -- N -- N refs/changes/01/30101/1 (2e2d22370) 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

[toolchain/jenkins-scripts] reference refs/changes/00/46800/3 updated (37424f167 -> ed127202d)

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/00/46800/3 in repository toolchain/jenkins-scripts. discards 37424f167 round-robin.sh (build_abe): Try to workaround race conditions [...] adds ed127202d round-robin.sh (build_abe): Try to workaround race conditions [...] 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 (37424f167) \ N -- N -- N refs/changes/00/46800/3 (ed127202d) 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

[toolchain/jenkins-scripts] reference refs/changes/00/46800/2 updated (ca5db1df1 -> 0f47d1fdb)

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/00/46800/2 in repository toolchain/jenkins-scripts. discards ca5db1df1 round-robin.sh (build_abe): Try to workaround race conditions [...] new 0f47d1fdb round-robin.sh (build_abe): Try to workaround race conditions [...] 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 (ca5db1df1) \ N -- N -- N refs/changes/00/46800/2 (0f47d1fdb) 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

[toolchain/jenkins-scripts] reference refs/changes/00/46800/1 updated (997aa9212 -> 4ab86dc77)

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/00/46800/1 in repository toolchain/jenkins-scripts. discards 997aa9212 round-robin.sh (build_abe): Try to workaround race conditions [...] new 4ab86dc77 round-robin.sh (build_abe): Try to workaround race conditions [...] 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 (997aa9212) \ N -- N -- N refs/changes/00/46800/1 (4ab86dc77) 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

[toolchain/jenkins-scripts] reference refs/changes/00/46600/1 updated (cb5afad79 -> 16cbf1222)

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/00/46600/1 in repository toolchain/jenkins-scripts. discards cb5afad79 round-robin.sh (build_abe): Check if $pw[] is defined before [...] new 16cbf1222 round-robin.sh (build_abe): Check if $pw[] is defined before [...] 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 (cb5afad79) \ N -- N -- N refs/changes/00/46600/1 (16cbf1222) 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

[toolchain/jenkins-scripts] reference refs/changes/00/46200/2 updated (a025119bd -> de98832e5)

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/00/46200/2 in repository toolchain/jenkins-scripts. discards a025119bd round-robin-notify.sh (print_mail_recipients): Consider *embe [...] discards 371ad98b7 tcwg-update-lnt-results.sh: cleaner use of lnt environment adds de98832e5 tcwg-update-lnt-results.sh: cleaner use of lnt environment 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 (a025119bd) \ N -- N -- N refs/changes/00/46200/2 (de98832e5) 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 | 567 -------------- round-robin-bisect.sh | 681 ---------------- round-robin-notify.sh | 1971 ----------------------------------------------- 3 files changed, 3219 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024