Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/14/45614/2 updated (f9ca877da -> 519d70762)

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/45614/2 in repository toolchain/jenkins-scripts. discards f9ca877da round-robin-baseline.sh (rewrite_single_revision): Fix corner-case discards ec386d638 start-container-docker.sh: Fix releasing of board lock file b [...] adds 519d70762 start-container-docker.sh: Fix releasing of board lock file b [...] 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 (f9ca877da) \ N -- N -- N refs/changes/14/45614/2 (519d70762) 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 | 455 ------------- round-robin-bisect.sh | 655 ------------------- round-robin-notify.sh | 1620 ----------------------------------------------- 3 files changed, 2730 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

[toolchain/jenkins-scripts] reference refs/changes/14/45614/1 updated (6148ab601 -> 4a952f710)

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/45614/1 in repository toolchain/jenkins-scripts. discards 6148ab601 round-robin-baseline.sh (rewrite_single_revision): Fix corner-case discards 8ad1fe486 tcwg_bmk-build.sh (benchmark): Improve wait cycle new 4a952f710 tcwg_bmk-build.sh (benchmark): Improve wait cycle 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 (6148ab601) \ N -- N -- N refs/changes/14/45614/1 (4a952f710) 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: round-robin-baseline.sh | 455 ------------- round-robin-bisect.sh | 655 ------------------- round-robin-notify.sh | 1620 ----------------------------------------------- 3 files changed, 2730 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

[toolchain/jenkins-scripts] reference refs/changes/14/45514/1 updated (fdb0d1cc7 -> 97d17c9ea)

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/45514/1 in repository toolchain/jenkins-scripts. discards fdb0d1cc7 round-robin-notify.sh: Remove duplication in mail-body.txt discards 68e7a8255 round-robin-notify.sh (print_mail_recipients): Rework discards f665b453e round-robin-bisect.sh: Remove unneeded override discards a0f52b969 round-robin-bisect.sh: Improve trigger for subsequent builds adds 97d17c9ea round-robin-bisect.sh: Improve trigger for subsequent builds 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 (fdb0d1cc7) \ N -- N -- N refs/changes/14/45514/1 (97d17c9ea) 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 | 413 ------------ round-robin-bisect.sh | 655 ------------------- round-robin-notify.sh | 1587 ----------------------------------------------- 3 files changed, 2655 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

[toolchain/jenkins-scripts] reference refs/changes/14/44614/2 updated (408335870 -> 9bd462725)

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/44614/2 in repository toolchain/jenkins-scripts. discards 408335870 generate-cimonitor-dashboard.py: Fix file descriptors leak adds 9bd462725 generate-cimonitor-dashboard.py: Fix file descriptors leak 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 (408335870) \ N -- N -- N refs/changes/14/44614/2 (9bd462725) 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/44614/1 updated (1f8892798 -> c630d8027)

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/44614/1 in repository toolchain/jenkins-scripts. discards 1f8892798 generate-cimonitor-dashboard.py: Fix file descriptors leak new c630d8027 generate-cimonitor-dashboard.py: Fix file descriptors leak 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 (1f8892798) \ N -- N -- N refs/changes/14/44614/1 (c630d8027) 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/44214/3 updated (31b3e9239 -> f314e5045)

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/44214/3 in repository toolchain/jenkins-scripts. discards 31b3e9239 round-robin-notify.sh: Rework on global flow discards 104000423 tcwg_*-build.sh: remove rr[start_date], as it is now useless adds f314e5045 tcwg_*-build.sh: remove rr[start_date], as it is now useless 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 (31b3e9239) \ N -- N -- N refs/changes/14/44214/3 (f314e5045) 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-bisect.sh | 633 --------------------------- round-robin-notify.sh | 1167 ------------------------------------------------- 2 files changed, 1800 deletions(-) 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

[toolchain/jenkins-scripts] reference refs/changes/14/44214/2 updated (02ac66d32 -> 3507b2119)

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/44214/2 in repository toolchain/jenkins-scripts. discards 02ac66d32 round-robin-notify.sh: Rework on global flow discards 99665f3cd tcwg_*-build.sh: remove rr[start_date], as it is now useless new 3507b2119 tcwg_*-build.sh: remove rr[start_date], as it is now useless 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 (02ac66d32) \ N -- N -- N refs/changes/14/44214/2 (3507b2119) 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: round-robin-bisect.sh | 633 --------------------------- round-robin-notify.sh | 1167 ------------------------------------------------- 2 files changed, 1800 deletions(-) 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

[toolchain/jenkins-scripts] reference refs/changes/14/44214/1 updated (faa165266 -> 3507b2119)

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/44214/1 in repository toolchain/jenkins-scripts. discards faa165266 round-robin-notify.sh: Rework on global flow discards 99665f3cd tcwg_*-build.sh: remove rr[start_date], as it is now useless new 3507b2119 tcwg_*-build.sh: remove rr[start_date], as it is now useless 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 (faa165266) \ N -- N -- N refs/changes/14/44214/1 (3507b2119) 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: round-robin-bisect.sh | 633 ------------------------- round-robin-notify.sh | 1227 ------------------------------------------------- 2 files changed, 1860 deletions(-) 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

[toolchain/jenkins-scripts] reference refs/changes/14/43814/1 updated (0f63cc83a -> fe7c3a361)

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/43814/1 in repository toolchain/jenkins-scripts. discards 0f63cc83a round-robin-notify.sh, *-notify.sh: dispatch notification fil [...] new fe7c3a361 round-robin-notify.sh, *-notify.sh: dispatch notification fil [...] 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 (0f63cc83a) \ N -- N -- N refs/changes/14/43814/1 (fe7c3a361) 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/43714/1 updated (9d63030d7 -> da87ff9f9)

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/43714/1 in repository toolchain/jenkins-scripts. discards 9d63030d7 tcwg_{aosp,bmk}-build.sh: Fix usage of readarray adds da87ff9f9 tcwg_{aosp,bmk}-build.sh: Fix usage of readarray 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 (9d63030d7) \ N -- N -- N refs/changes/14/43714/1 (da87ff9f9) 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024