Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/50/44350/1 updated (06570f54d -> dfea7dda2)

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/50/44350/1 in repository toolchain/jenkins-scripts. discards 06570f54d round-robin.sh (build_abe): Do not build fortran for bare-met [...] new dfea7dda2 round-robin.sh (build_abe): Do not build fortran for bare-met [...] 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 (06570f54d) \ N -- N -- N refs/changes/50/44350/1 (dfea7dda2) 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/50/43750/1 updated (67ff42392 -> 4fe547431)

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/50/43750/1 in repository toolchain/jenkins-scripts. discards 67ff42392 tcwg-llvmbot: Don't start Graviton 3 workers adds 4fe547431 tcwg-llvmbot: Don't start Graviton 3 workers 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 (67ff42392) \ N -- N -- N refs/changes/50/43750/1 (4fe547431) 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/50/43650/1 updated (67ef505a6 -> 60e91b98b)

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/50/43650/1 in repository toolchain/jenkins-scripts. discards 67ef505a6 generate-cimonitor-dashboard.py: Add hours in the time_since [...] adds 60e91b98b generate-cimonitor-dashboard.py: Add hours in the time_since [...] 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 (67ef505a6) \ N -- N -- N refs/changes/50/43650/1 (60e91b98b) 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/50/43250/2 updated (0d32efc0e -> 4e963655d)

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/50/43250/2 in repository toolchain/jenkins-scripts. discards 0d32efc0e tcwg-llvmbot: Move linaro-clang-aarch64-full-2stage to silent adds 4e963655d tcwg-llvmbot: Move linaro-clang-aarch64-full-2stage to silent 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 (0d32efc0e) \ N -- N -- N refs/changes/50/43250/2 (4e963655d) 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/50/43250/1 updated (01c38e94b -> c204bd9d4)

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/50/43250/1 in repository toolchain/jenkins-scripts. discards 01c38e94b tcwg-llvmbot: Move linaro-clang-aarch64-full-2stage to silent new c204bd9d4 tcwg-llvmbot: Move linaro-clang-aarch64-full-2stage to silent 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 (01c38e94b) \ N -- N -- N refs/changes/50/43250/1 (c204bd9d4) 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/50/39450/1 updated (84b46c4fd -> c2cd8f90e)

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/50/39450/1 in repository toolchain/jenkins-scripts. discards 84b46c4fd round-robin.sh (build_abe): Limit GDB testsuites to 16-thread [...] adds c2cd8f90e round-robin.sh (build_abe): Limit GDB testsuites to 16-thread [...] 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 (84b46c4fd) \ N -- N -- N refs/changes/50/39450/1 (c2cd8f90e) 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/50/39350/1 updated (24999566c -> 5677258c9)

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/50/39350/1 in repository toolchain/jenkins-scripts. discards 24999566c tcwg-benchmark.sh: Run coremark.sh in just-copied ~tcwg-bench [...] adds 5677258c9 tcwg-benchmark.sh: Run coremark.sh in just-copied ~tcwg-bench [...] 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 (24999566c) \ N -- N -- N refs/changes/50/39350/1 (5677258c9) 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/50/32850/3 updated (031d069a9 -> 531d00328)

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/50/32850/3 in repository toolchain/jenkins-scripts. discards 031d069a9 tcwg-benchmark.sh: Prepare board for benchmarking adds 531d00328 tcwg-benchmark.sh: Prepare board for benchmarking 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 (031d069a9) \ N -- N -- N refs/changes/50/32850/3 (531d00328) 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/50/32850/2 updated (ee25b39ed -> cb3d8064b)

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/50/32850/2 in repository toolchain/jenkins-scripts. discards ee25b39ed tcwg-benchmark.sh: Prepare board for benchmarking new cb3d8064b tcwg-benchmark.sh: Prepare board for benchmarking 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 (ee25b39ed) \ N -- N -- N refs/changes/50/32850/2 (cb3d8064b) 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/50/32850/1 updated (a4dac3e68 -> 052b66654)

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/50/32850/1 in repository toolchain/jenkins-scripts. discards a4dac3e68 tcwg-benchmark.sh: Prepare board for benchmarking adds 052b66654 tcwg-benchmark.sh: Prepare board for benchmarking 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 (a4dac3e68) \ N -- N -- N refs/changes/50/32850/1 (052b66654) 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