Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/55/45855/2 updated (a498c527c -> 965a1b3d4)

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/55/45855/2 in repository toolchain/jenkins-scripts. discards a498c527c round-robin-notify.sh: fix lnt report generation new 965a1b3d4 round-robin-notify.sh: fix lnt report generation 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 (a498c527c) \ N -- N -- N refs/changes/55/45855/2 (965a1b3d4) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45855/1 updated (233cef2b2 -> 7297fa94d)

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/55/45855/1 in repository toolchain/jenkins-scripts. discards 233cef2b2 round-robin-notify.sh: fix lnt report generation new 7297fa94d round-robin-notify.sh: fix lnt report generation 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 (233cef2b2) \ N -- N -- N refs/changes/55/45855/1 (7297fa94d) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45755/2 updated (2243da9f9 -> 79b22576a)

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/55/45755/2 in repository toolchain/jenkins-scripts. discards 2243da9f9 round-robin-bisect.sh (print_interesting_commit): Use better pattern discards ba77b290a round-robin-baseline.sh: Break rewriting process if too many [...] discards 5317741ac tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] adds 79b22576a tcwg-report-stale-rr-jobs.sh: adapt for the new location of 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 (2243da9f9) \ N -- N -- N refs/changes/55/45755/2 (79b22576a) 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 | 553 --------------- round-robin-bisect.sh | 681 ------------------ round-robin-notify.sh | 1806 ----------------------------------------------- 3 files changed, 3040 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45755/1 updated (6f9b06585 -> 79b22576a)

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/55/45755/1 in repository toolchain/jenkins-scripts. discards 6f9b06585 round-robin-bisect.sh (print_interesting_commit): Use better pattern discards 5317741ac tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] adds 79b22576a tcwg-report-stale-rr-jobs.sh: adapt for the new location of 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 (6f9b06585) \ N -- N -- N refs/changes/55/45755/1 (79b22576a) 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 | 525 -------------- round-robin-bisect.sh | 681 ------------------ round-robin-notify.sh | 1806 ----------------------------------------------- 3 files changed, 3012 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45655/2 updated (41f2ed493 -> 9485a171d)

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/55/45655/2 in repository toolchain/jenkins-scripts. discards 41f2ed493 round-robin-notify.sh (update_interesting_commits): Cleanup u [...] discards 80d12e5ff round-robin-notify.sh (update_interesting_commits): Rename su [...] discards 7eacfd71e round-robin-notify.sh (update_interesting_commits): Add detai [...] discards 11c2ca8e2 tcwg_bmk-build.sh: rename samples-variabilty.py script adds 9485a171d tcwg_bmk-build.sh: rename samples-variabilty.py script 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 (41f2ed493) \ N -- N -- N refs/changes/55/45655/2 (9485a171d) 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 | 1718 ----------------------------------------------- 3 files changed, 2828 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45655/1 updated (38d813d9e -> ecc96ac0b)

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/55/45655/1 in repository toolchain/jenkins-scripts. discards 38d813d9e round-robin-notify.sh (update_interesting_commits): Cleanup u [...] discards a91dd19f9 round-robin-notify.sh (update_interesting_commits): Rename su [...] discards 359c8e061 round-robin-notify.sh (update_interesting_commits): Add detai [...] discards f20216f12 round-robin-notify.sh: Cleanup generation of email files discards d67583abd round-robin-notify.sh (print_commits): Improve precommit output discards 0985806cc round-robin-notify.sh (print_commits): Restructure adds ecc96ac0b round-robin-notify.sh (print_commits): Restructure 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 (38d813d9e) \ N -- N -- N refs/changes/55/45655/1 (ecc96ac0b) 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 | 1713 ----------------------------------------------- 3 files changed, 2823 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45255/3 updated (5bbf0af8d -> 2f640bc45)

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/55/45255/3 in repository toolchain/jenkins-scripts. discards 5bbf0af8d docker-run.sh: Remove ++rsync_to/++rsync_from unused options adds 2f640bc45 docker-run.sh: Remove ++rsync_to/++rsync_from unused options 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 (5bbf0af8d) \ N -- N -- N refs/changes/55/45255/3 (2f640bc45) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45255/2 updated (f6229827c -> 7a42dd907)

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/55/45255/2 in repository toolchain/jenkins-scripts. discards f6229827c docker-run.sh: Remove ++rsync_to/++rsync_from unused options adds 7a42dd907 docker-run.sh: Remove ++rsync_to/++rsync_from unused options 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 (f6229827c) \ N -- N -- N refs/changes/55/45255/2 (7a42dd907) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45255/1 updated (e296e5d71 -> 8107d961b)

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/55/45255/1 in repository toolchain/jenkins-scripts. discards e296e5d71 docker-run.sh: Remove ++rsync_to/++rsync_from unused options new 8107d961b docker-run.sh: Remove ++rsync_to/++rsync_from unused options 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 (e296e5d71) \ N -- N -- N refs/changes/55/45255/1 (8107d961b) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/55/45055/1 updated (3698ff1e5 -> 31cd66402)

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/55/45055/1 in repository toolchain/jenkins-scripts. discards 3698ff1e5 pw-helpers.sh (pw_get_patch_from_series): Cleanup adds 31cd66402 pw-helpers.sh (pw_get_patch_from_series): Cleanup 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 (3698ff1e5) \ N -- N -- N refs/changes/55/45055/1 (31cd66402) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024