Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/25/37325/1 updated (462caf11b -> 55283f70c)

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/25/37325/1 in repository toolchain/jenkins-scripts. discards 462caf11b tcwg_kernel-build.sh: Use LLD for all LLVM configs adds 55283f70c tcwg_kernel-build.sh: Use LLD for all LLVM configs 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 (462caf11b) \ N -- N -- N refs/changes/25/37325/1 (55283f70c) 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/25/35225/2 updated (d18e3be48 -> 00e0a22d9)

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/25/35225/2 in repository toolchain/jenkins-scripts. discards d18e3be48 jenkins-helpers.sh: Fix log_url unbound error adds 00e0a22d9 jenkins-helpers.sh: Fix log_url unbound error 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 (d18e3be48) \ N -- N -- N refs/changes/25/35225/2 (00e0a22d9) 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/25/35225/1 updated (205c729ed -> 796b49f68)

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/25/35225/1 in repository toolchain/jenkins-scripts. discards 205c729ed jenkins-helpers.sh: Fix log_url unbound error new 796b49f68 jenkins-helpers.sh: Fix log_url unbound error 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 (205c729ed) \ N -- N -- N refs/changes/25/35225/1 (796b49f68) 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/25/34925/2 updated (49aa56fa3 -> c275d311d)

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/25/34925/2 in repository toolchain/jenkins-scripts. discards 49aa56fa3 tcwg-benchmark*.sh: Update to pass --hw_tags to bmk-scripts/ adds c275d311d tcwg-benchmark*.sh: Update to pass --hw_tags to bmk-scripts/ 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 (49aa56fa3) \ N -- N -- N refs/changes/25/34925/2 (c275d311d) 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/25/34925/1 updated (1bb602774 -> 80ed9d939)

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/25/34925/1 in repository toolchain/jenkins-scripts. discards 1bb602774 tcwg-benchmark*.sh: Update to pass --hw_tags to bmk-scripts/ new 80ed9d939 tcwg-benchmark*.sh: Update to pass --hw_tags to bmk-scripts/ 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 (1bb602774) \ N -- N -- N refs/changes/25/34925/1 (80ed9d939) 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/25/34625/1 updated (79fff89c8 -> 8383d5c52)

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/25/34625/1 in repository toolchain/jenkins-scripts. discards 79fff89c8 round-robin-bisect.sh: Fail curl commands on HTTP errors discards 271be4317 tcwg_bmk-build.sh: Simplify no_regression_to_base_p adds 8383d5c52 tcwg_bmk-build.sh: Simplify no_regression_to_base_p 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 (79fff89c8) \ N -- N -- N refs/changes/25/34625/1 (8383d5c52) 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 | 616 -------------------------------------------------- 1 file changed, 616 deletions(-) delete mode 100755 round-robin-bisect.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/25/34025/2 updated (624956250 -> 190adca10)

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/25/34025/2 in repository toolchain/jenkins-scripts. discards 624956250 round-robin-bisect.sh: Better handle skipping of "bad" build discards 377eba35c round-robin-bisect.sh: Update after split of tcwg_bmk discards 31272ab9a tcwg_bmk-build.sh: Update display tag of benchmark jobs adds 190adca10 tcwg_bmk-build.sh: Update display tag of benchmark jobs 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 (624956250) \ N -- N -- N refs/changes/25/34025/2 (190adca10) 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 | 604 -------------------------------------------------- 1 file changed, 604 deletions(-) delete mode 100755 round-robin-bisect.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/25/34025/1 updated (89e905ed5 -> 190adca10)

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/25/34025/1 in repository toolchain/jenkins-scripts. discards 89e905ed5 round-robin-bisect.sh: Better handle skipping of "bad" build discards 31272ab9a tcwg_bmk-build.sh: Update display tag of benchmark jobs adds 190adca10 tcwg_bmk-build.sh: Update display tag of benchmark jobs 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 (89e905ed5) \ N -- N -- N refs/changes/25/34025/1 (190adca10) 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 | 604 -------------------------------------------------- 1 file changed, 604 deletions(-) delete mode 100755 round-robin-bisect.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/25/32925/1 updated (b912798df -> 894e7d75e)

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/25/32925/1 in repository toolchain/jenkins-scripts. discards b912798df round-robin-bisect.sh: Fix more problems with posting to Jira discards 6058e0a6a tcwg-update-llvmbot-containers.sh: Follow-up fix adds 894e7d75e tcwg-update-llvmbot-containers.sh: Follow-up fix 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 (b912798df) \ N -- N -- N refs/changes/25/32925/1 (894e7d75e) 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 | 552 -------------------------------------------------- 1 file changed, 552 deletions(-) delete mode 100755 round-robin-bisect.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/25/32725/1 updated (188abe571 -> 23d2400cc)

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/25/32725/1 in repository toolchain/jenkins-scripts. discards 188abe571 start-container-docker.sh: Make sure containers get all CPUs adds 23d2400cc start-container-docker.sh: Make sure containers get all CPUs 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 (188abe571) \ N -- N -- N refs/changes/25/32725/1 (23d2400cc) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024