Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/10/39610/1 updated (fb0dd6f1c -> bbe12ed46)

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/10/39610/1 in repository toolchain/jenkins-scripts. discards fb0dd6f1c round-robin.sh: Run GDB testsuites single-threaded adds bbe12ed46 round-robin.sh: Run GDB testsuites single-threaded 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 (fb0dd6f1c) \ N -- N -- N refs/changes/10/39610/1 (bbe12ed46) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/38210/1 updated (ad4136621 -> b237fc107)

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/10/38210/1 in repository toolchain/jenkins-scripts. discards ad4136621 tcwg-report-stale-rr-jobs.sh: Fix human output adds b237fc107 tcwg-report-stale-rr-jobs.sh: Fix human output 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 (ad4136621) \ N -- N -- N refs/changes/10/38210/1 (b237fc107) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/38110/1 updated (4c8e3d3d3 -> 6e70483c7)

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/10/38110/1 in repository toolchain/jenkins-scripts. discards 4c8e3d3d3 Move some workers to llvm master staging. adds 6e70483c7 Move some workers to llvm master staging. 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 (4c8e3d3d3) \ N -- N -- N refs/changes/10/38110/1 (6e70483c7) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/37510/1 updated (e23f08ed8 -> e1b7cb695)

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/10/37510/1 in repository toolchain/jenkins-scripts. discards e23f08ed8 round-robin-bisect.sh: Use print_traceback discards e3dff5bb4 round-robin-bisect.sh: Remove obsolete marker discards 8b78dcbbb round-robin-bisect.sh: Generalize logic of handling "reset" commit discards 499beadee round-robin-bisect.sh: Make handling of unsuccessful bisects [...] discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...] discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...] discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE 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 (e23f08ed8) \ N -- N -- N refs/changes/10/37510/1 (e1b7cb695) 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 | 718 -------------------------------------------------- 1 file changed, 718 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/33110/1 updated (c4ef1c181 -> def1e3427)

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/10/33110/1 in repository toolchain/jenkins-scripts. discards c4ef1c181 tcwg-update-llvmbot-containers: Remove arm-full[-selfhost] adds def1e3427 tcwg-update-llvmbot-containers: Remove arm-full[-selfhost] 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 (c4ef1c181) \ N -- N -- N refs/changes/10/33110/1 (def1e3427) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/33010/1 updated (3d6ec47b2 -> ea22993d8)

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/10/33010/1 in repository toolchain/jenkins-scripts. discards 3d6ec47b2 round-robin-bisect.sh: Fix minor bugs around string processing discards 2dc4fca2b jenkins-helpers.sh: Add a timeout for "ssh $board true" in wa [...] adds ea22993d8 jenkins-helpers.sh: Add a timeout for "ssh $board true" in wa [...] 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 (3d6ec47b2) \ N -- N -- N refs/changes/10/33010/1 (ea22993d8) 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 | 571 -------------------------------------------------- 1 file changed, 571 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/32810/4 updated (d00945a29 -> 7f9838c71)

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/10/32810/4 in repository toolchain/jenkins-scripts. discards d00945a29 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] adds 7f9838c71 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] 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 (d00945a29) \ N -- N -- N refs/changes/10/32810/4 (7f9838c71) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/32810/3 updated (fb8020708 -> 4a98f84b2)

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/10/32810/3 in repository toolchain/jenkins-scripts. discards fb8020708 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] new 4a98f84b2 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] 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 (fb8020708) \ N -- N -- N refs/changes/10/32810/3 (4a98f84b2) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/32810/2 updated (1cc39b031 -> 3a45086f1)

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/10/32810/2 in repository toolchain/jenkins-scripts. discards 1cc39b031 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] new 3a45086f1 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] 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 (1cc39b031) \ N -- N -- N refs/changes/10/32810/2 (3a45086f1) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/10/32810/1 updated (c185347c4 -> b87729fc3)

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/10/32810/1 in repository toolchain/jenkins-scripts. discards c185347c4 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] new b87729fc3 tcwg_bmk-build.sh: Redirect verbose output of tcwg-benchmark- [...] 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 (c185347c4) \ N -- N -- N refs/changes/10/32810/1 (b87729fc3) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024