Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/38/46138/2 updated (83f6b98e1 -> ca70aa0df)

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/38/46138/2 in repository toolchain/jenkins-scripts. discards 83f6b98e1 tcwg_bmk-config.sh: Handle tcwg_bmk-qc_speed-cpu2017rate--gnu [...] adds ca70aa0df tcwg_bmk-config.sh: Handle tcwg_bmk-qc_speed-cpu2017rate--gnu [...] 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 (83f6b98e1) \ N -- N -- N refs/changes/38/46138/2 (ca70aa0df) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/46138/1 updated (6c94b6c6e -> b6e6e6e88)

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/38/46138/1 in repository toolchain/jenkins-scripts. discards 6c94b6c6e tcwg_bmk-config.sh: Handle tcwg_bmk-qc_speed-cpu2017rate--gnu [...] new b6e6e6e88 tcwg_bmk-config.sh: Handle tcwg_bmk-qc_speed-cpu2017rate--gnu [...] 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 (6c94b6c6e) \ N -- N -- N refs/changes/38/46138/1 (b6e6e6e88) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/45238/1 updated (7d616c035 -> 7efdc03f4)

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/38/45238/1 in repository toolchain/jenkins-scripts. discards 7d616c035 round-robin-notify.sh (print_mail_body): Make the regression [...] discards 934531cfc round-robin.sh: Start bisection from top of branch, rather th [...] adds 7efdc03f4 round-robin.sh: Start bisection from top of branch, rather th [...] 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 (7d616c035) \ N -- N -- N refs/changes/38/45238/1 (7efdc03f4) 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 | 410 ------------- round-robin-bisect.sh | 653 -------------------- round-robin-notify.sh | 1510 ----------------------------------------------- 3 files changed, 2573 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/44538/1 updated (b6d337e6b -> 639bc5a21)

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/38/44538/1 in repository toolchain/jenkins-scripts. discards b6d337e6b tcwg-update-llvmbot-containers.sh: Reshuffle tk1 containers adds 639bc5a21 tcwg-update-llvmbot-containers.sh: Reshuffle tk1 containers 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 (b6d337e6b) \ N -- N -- N refs/changes/38/44538/1 (639bc5a21) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/44338/4 updated (c1f85ef2b -> 079343338)

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/38/44338/4 in repository toolchain/jenkins-scripts. discards c1f85ef2b round-robin-notify.sh: small cp rewrite discards 6b9aa7f24 start-container-docker.sh: Add "--task precommit" adds 079343338 start-container-docker.sh: Add "--task precommit" 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 (c1f85ef2b) \ N -- N -- N refs/changes/38/44338/4 (079343338) 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 | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/44338/3 updated (48ffc2625 -> 4414265a4)

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/38/44338/3 in repository toolchain/jenkins-scripts. discards 48ffc2625 round-robin-notify.sh: small cp rewrite discards 157084fe8 tcwg_bmk-build.sh: diff-bmk-results.py calls all outputs in a [...] adds 4414265a4 tcwg_bmk-build.sh: diff-bmk-results.py calls all outputs in a [...] 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 (48ffc2625) \ N -- N -- N refs/changes/38/44338/3 (4414265a4) 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 | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/44338/2 updated (ed54c46da -> 4d206e398)

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/38/44338/2 in repository toolchain/jenkins-scripts. discards ed54c46da round-robin-notify.sh: small cp rewrite discards 083901d23 jenkins-helper.sh (run_step*): Support starting after a speci [...] adds 4d206e398 jenkins-helper.sh (run_step*): Support starting after a speci [...] 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 (ed54c46da) \ N -- N -- N refs/changes/38/44338/2 (4d206e398) 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 | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/44338/1 updated (b6eda970c -> 1a49440a0)

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/38/44338/1 in repository toolchain/jenkins-scripts. discards b6eda970c round-robin-notify.sh: small cp rewrite discards eecd3f9c2 round-robin-notify.sh: Make the report more 'positive' discards 75ea11516 round-robin-notify.sh: Include component name, reduce 'short' [...] discards 70d80c710 tcwg_bmk-build.sh: Add symlink to ease navigation in jenkins [...] adds 1a49440a0 tcwg_bmk-build.sh: Add symlink to ease navigation in jenkins [...] 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 (b6eda970c) \ N -- N -- N refs/changes/38/44338/1 (1a49440a0) 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 | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/43738/1 updated (b529ef86b -> 9c33860e7)

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/38/43738/1 in repository toolchain/jenkins-scripts. discards b529ef86b tcwg_gnu-build.sh: Enable checking testsuite results for tcwg [...] adds 9c33860e7 tcwg_gnu-build.sh: Enable checking testsuite results for tcwg [...] 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 (b529ef86b) \ N -- N -- N refs/changes/38/43738/1 (9c33860e7) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/42938/1 updated (b5a15d90d -> 178303a43)

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/38/42938/1 in repository toolchain/jenkins-scripts. discards b5a15d90d tcwg_bmk-build.sh: Fix old_format_baseline_branch adds 178303a43 tcwg_bmk-build.sh: Fix old_format_baseline_branch 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 (b5a15d90d) \ N -- N -- N refs/changes/38/42938/1 (178303a43) 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, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024