Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/20/44620/1 updated (052a83b72 -> aa70ad638)

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/20/44620/1 in repository toolchain/jenkins-scripts. discards 052a83b72 tcwg_bmk-build.sh: Simplify compare_options handling new aa70ad638 tcwg_bmk-build.sh: Simplify compare_options handling 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 (052a83b72) \ N -- N -- N refs/changes/20/44620/1 (aa70ad638) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/44320/3 updated (eecd3f9c2 -> 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/20/44320/3 in repository toolchain/jenkins-scripts. 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 (eecd3f9c2) \ N -- N -- N refs/changes/20/44320/3 (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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/44320/2 updated (7f54a9183 -> e49149f7a)

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/20/44320/2 in repository toolchain/jenkins-scripts. discards 7f54a9183 round-robin-notify.sh: Make the report more 'positive' discards 14938f5c7 round-robin-notify.sh: Include component name, reduce 'short' [...] discards 4fcc9a5a5 generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] adds e49149f7a generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] 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 (7f54a9183) \ N -- N -- N refs/changes/20/44320/2 (e49149f7a) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/44320/1 updated (e116e927b -> e49149f7a)

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/20/44320/1 in repository toolchain/jenkins-scripts. discards e116e927b round-robin-notify.sh: Make the report more 'positive' discards c47ff7aca round-robin-notify.sh: Include component name, reduce 'short' [...] discards 4fcc9a5a5 generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] adds e49149f7a generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] 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 (e116e927b) \ N -- N -- N refs/changes/20/44320/1 (e49149f7a) 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 | 1231 ------------------------------------------------- 2 files changed, 1878 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/44220/1 updated (c17957aee -> 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/20/44220/1 in repository toolchain/jenkins-scripts. discards c17957aee round-robin-notify.sh: fix for mail of first detection discards 70f4f7f24 round-robin-notify.sh: Fix print_mail_recipients 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 (c17957aee) \ N -- N -- N refs/changes/20/44220/1 (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 | 1193 ------------------------------------------------- 2 files changed, 1826 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/43520/1 updated (a8a51f413 -> 114877dfe)

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/20/43520/1 in repository toolchain/jenkins-scripts. discards a8a51f413 tcwg_gnu-build.sh: Enable unittest.exp in fast_check_gdb adds 114877dfe tcwg_gnu-build.sh: Enable unittest.exp in fast_check_gdb 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 (a8a51f413) \ N -- N -- N refs/changes/20/43520/1 (114877dfe) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/42420/2 updated (64402101d -> ca120ffc7)

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/20/42420/2 in repository toolchain/jenkins-scripts. discards 64402101d tcwg-update-llvmbot: Move aarch64 full 2 stage and armv8 lld [...] adds ca120ffc7 tcwg-update-llvmbot: Move aarch64 full 2 stage and armv8 lld [...] 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 (64402101d) \ N -- N -- N refs/changes/20/42420/2 (ca120ffc7) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/42420/1 updated (154a71c03 -> 3b1fc070a)

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/20/42420/1 in repository toolchain/jenkins-scripts. discards 154a71c03 tcwg-update-llvmbot: Move aarch64 full 2 stage and armv8 lld [...] adds 3b1fc070a tcwg-update-llvmbot: Move aarch64 full 2 stage and armv8 lld [...] 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 (154a71c03) \ N -- N -- N refs/changes/20/42420/1 (3b1fc070a) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/42120/3 updated (41e0e60e9 -> b920af463)

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/20/42120/3 in repository toolchain/jenkins-scripts. discards 41e0e60e9 tcwg-llvm-release.sh: Use LLVM unwinder on armv7 adds b920af463 tcwg-llvm-release.sh: Use LLVM unwinder on armv7 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 (41e0e60e9) \ N -- N -- N refs/changes/20/42120/3 (b920af463) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/20/42120/2 updated (3e3b6f455 -> 1f85ed2a0)

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/20/42120/2 in repository toolchain/jenkins-scripts. discards 3e3b6f455 tcwg-llvm-release.sh: Use LLVM unwinder on armv7 new 1f85ed2a0 tcwg-llvm-release.sh: Use LLVM unwinder on armv7 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 (3e3b6f455) \ N -- N -- N refs/changes/20/42120/2 (1f85ed2a0) 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, 1 week

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024