Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/23/46923/1 updated (555eabe05 -> abb002044)

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/23/46923/1 in repository toolchain/jenkins-scripts. discards 555eabe05 tcwg_chromium-build.sh: Fix check_regression adds abb002044 tcwg_chromium-build.sh: Fix check_regression 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 (555eabe05) \ N -- N -- N refs/changes/23/46923/1 (abb002044) 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/23/46423/2 updated (ace6f530b -> a0efa3efe)

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/23/46423/2 in repository toolchain/jenkins-scripts. discards ace6f530b round-robin-notify.ah (print_readme_link): Add /*view*/ if needed discards 5b460638d jenkins-helpers.sh (git_clean): Remove corrupted index adds a0efa3efe jenkins-helpers.sh (git_clean): Remove corrupted index 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 (ace6f530b) \ N -- N -- N refs/changes/23/46423/2 (a0efa3efe) 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 | 584 ------------ round-robin-bisect.sh | 686 -------------- round-robin-notify.sh | 2315 ----------------------------------------------- 3 files changed, 3585 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/23/46423/1 updated (b620557c3 -> fa44b4de5)

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/23/46423/1 in repository toolchain/jenkins-scripts. discards b620557c3 round-robin-notify.ah (print_readme_link): Add /*view*/ if needed discards c75da0386 lnt-utils.sh: Disable debug traces in a too verbose function adds fa44b4de5 lnt-utils.sh: Disable debug traces in a too verbose function 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 (b620557c3) \ N -- N -- N refs/changes/23/46423/1 (fa44b4de5) 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 | 2326 ----------------------------------------------- 3 files changed, 3574 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/23/46323/2 updated (7b6922805 -> 6c2f13d32)

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/23/46323/2 in repository toolchain/jenkins-scripts. discards 7b6922805 tcwg-benchmark-results.sh: Pass --perf_csvs instead of --perf_csv. adds 6c2f13d32 tcwg-benchmark-results.sh: Pass --perf_csvs instead of --perf_csv. 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 (7b6922805) \ N -- N -- N refs/changes/23/46323/2 (6c2f13d32) 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/23/46323/1 updated (a0fd295f2 -> 6f33cf027)

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/23/46323/1 in repository toolchain/jenkins-scripts. discards a0fd295f2 tcwg-benchmark-results.sh: Pass --perf_csvs instead of --perf_csv. new 6f33cf027 tcwg-benchmark-results.sh: Pass --perf_csvs instead of --perf_csv. 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 (a0fd295f2) \ N -- N -- N refs/changes/23/46323/1 (6f33cf027) 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/23/46223/5 updated (94384c3cc -> e7515666e)

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/23/46223/5 in repository toolchain/jenkins-scripts. discards 94384c3cc lnt-utils.sh: Add git revision infos for the build adds e7515666e lnt-utils.sh: Add git revision infos for the build 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 (94384c3cc) \ N -- N -- N refs/changes/23/46223/5 (e7515666e) 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/23/46223/4 updated (744917218 -> 06b4f2d99)

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/23/46223/4 in repository toolchain/jenkins-scripts. discards 744917218 lnt-utils.sh: Add git revision infos for the build new 06b4f2d99 lnt-utils.sh: Add git revision infos for the build 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 (744917218) \ N -- N -- N refs/changes/23/46223/4 (06b4f2d99) 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/23/46223/3 updated (c5623e821 -> 7431b2c3b)

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/23/46223/3 in repository toolchain/jenkins-scripts. discards c5623e821 lnt-utils.sh: Add git revision infos for the build new 7431b2c3b lnt-utils.sh: Add git revision infos for the build 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 (c5623e821) \ N -- N -- N refs/changes/23/46223/3 (7431b2c3b) 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/23/46223/2 updated (1aac295f2 -> bd8a1fd74)

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/23/46223/2 in repository toolchain/jenkins-scripts. discards 1aac295f2 lnt-utils.sh: Add git revision infos for the build new bd8a1fd74 lnt-utils.sh: Add git revision infos for the build 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 (1aac295f2) \ N -- N -- N refs/changes/23/46223/2 (bd8a1fd74) 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/23/46223/1 updated (2b9d383e6 -> a95eb1ec2)

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/23/46223/1 in repository toolchain/jenkins-scripts. discards 2b9d383e6 lnt-utils.sh: Add git revision infos for the build new a95eb1ec2 lnt-utils.sh: Add git revision infos for the build 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 (2b9d383e6) \ N -- N -- N refs/changes/23/46223/1 (a95eb1ec2) 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