Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/94/44194/1 updated (17733a917 -> 31ac4c7c3)

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/94/44194/1 in repository toolchain/jenkins-scripts. discards 17733a917 round-robin-notify.sh: remove finalize_mail discards b338e55ca round-robin-notify.sh: print_mail_body discards 1f817c66c round-robin-notify.sh: generate jira files directly instead o [...] discards 8f9b0b620 round-robin-notify.sh: Add print_result print_config and use [...] discards 87da6e4e0 round-robin-notify.sh: split update and post interesting_commits discards a13ad33ce round-robin-notify.sh: print_mail_recipients discards 24a3cfec6 round-robin-notify.sh: Add print_commits discards d3105f260 round-robin.sh: Add results_date to manifest.sh new 31ac4c7c3 round-robin.sh: Add results_date to manifest.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 (17733a917) \ N -- N -- N refs/changes/94/44194/1 (31ac4c7c3) 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 | 1158 ------------------------------------------------- 2 files changed, 1791 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/43694/2 updated (db9d4afda -> 58b223b99)

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/94/43694/2 in repository toolchain/jenkins-scripts. discards db9d4afda ound-robin-notify.sh: mainy improve debug traces discards e0eebcd59 round-robin-notify.sh,tcwg_gnu-build.sh: improve basic gnu reporting adds 58b223b99 round-robin-notify.sh,tcwg_gnu-build.sh: improve basic gnu reporting 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 (db9d4afda) \ N -- N -- N refs/changes/94/43694/2 (58b223b99) 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 | 662 ----------------------------- round-robin-notify.sh | 1118 ------------------------------------------------- 2 files changed, 1780 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/43694/1 updated (b61d0d80d -> 8b4b2584e)

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/94/43694/1 in repository toolchain/jenkins-scripts. discards b61d0d80d ound-robin-notify.sh: mainy improve debug traces discards b26fb237a round-robin-notify.sh,tcwg_gnu-build.sh: improve basic gnu reporting new 8b4b2584e round-robin-notify.sh,tcwg_gnu-build.sh: improve basic gnu reporting 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 (b61d0d80d) \ N -- N -- N refs/changes/94/43694/1 (8b4b2584e) 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 | 662 ----------------------------- round-robin-notify.sh | 1118 ------------------------------------------------- 2 files changed, 1780 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/43294/2 updated (9a1f6f176 -> f05d96284)

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/94/43294/2 in repository toolchain/jenkins-scripts. discards 9a1f6f176 tcwg_bmk-build.sh: Fix mail message adds f05d96284 tcwg_bmk-build.sh: Fix mail message 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 (9a1f6f176) \ N -- N -- N refs/changes/94/43294/2 (f05d96284) 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/94/43294/1 updated (0313b56ac -> cce4dab5c)

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/94/43294/1 in repository toolchain/jenkins-scripts. discards 0313b56ac tcwg_bmk-build.sh: Fix mail message new cce4dab5c tcwg_bmk-build.sh: Fix mail message 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 (0313b56ac) \ N -- N -- N refs/changes/94/43294/1 (cce4dab5c) 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/94/42394/3 updated (f076a6e57 -> 52ffe76fe)

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/94/42394/3 in repository toolchain/jenkins-scripts. discards f076a6e57 wrappers/count-wrapper-install.sh: Support installing shadow- [...] adds 52ffe76fe wrappers/count-wrapper-install.sh: Support installing shadow- [...] 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 (f076a6e57) \ N -- N -- N refs/changes/94/42394/3 (52ffe76fe) 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/94/42394/2 updated (c987e6ed1 -> da9f9a140)

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/94/42394/2 in repository toolchain/jenkins-scripts. discards c987e6ed1 wrappers/count-wrapper-install.sh: Support installing shadow- [...] adds da9f9a140 wrappers/count-wrapper-install.sh: Support installing shadow- [...] 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 (c987e6ed1) \ N -- N -- N refs/changes/94/42394/2 (da9f9a140) 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/94/42394/1 updated (4358161ff -> 5fc132345)

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/94/42394/1 in repository toolchain/jenkins-scripts. discards 4358161ff wrappers/count-wrapper-install.sh: Support installing shadow- [...] adds 5fc132345 wrappers/count-wrapper-install.sh: Support installing shadow- [...] 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 (4358161ff) \ N -- N -- N refs/changes/94/42394/1 (5fc132345) 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/94/42094/1 updated (c71ac4103 -> 40c4afda0)

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/94/42094/1 in repository toolchain/jenkins-scripts. discards c71ac4103 dashboard-generate-squad.sh: Accept Mean values adds 40c4afda0 dashboard-generate-squad.sh: Accept Mean values 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 (c71ac4103) \ N -- N -- N refs/changes/94/42094/1 (40c4afda0) 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/94/40694/4 updated (b69c9f7db -> 7b9578558)

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/94/40694/4 in repository toolchain/jenkins-scripts. discards b69c9f7db tcwg-benchmark-results.sh: Gather md5sum metric and skip comp [...] adds 7b9578558 tcwg-benchmark-results.sh: Gather md5sum metric and skip comp [...] 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 (b69c9f7db) \ N -- N -- N refs/changes/94/40694/4 (7b9578558) 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