Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/21/45821/1 updated (6396647f2 -> ba12dec68)

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/21/45821/1 in repository toolchain/jenkins-scripts. discards 6396647f2 round-robin-notify.sh (update_interesting_commits): Stabilize [...] discards 4d2ab5b34 gnu-config.sh (settings_for_ci_project_and_config): Move code [...] adds ba12dec68 gnu-config.sh (settings_for_ci_project_and_config): Move code [...] 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 (6396647f2) \ N -- N -- N refs/changes/21/45821/1 (ba12dec68) 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 | 553 -------------- round-robin-bisect.sh | 681 ----------------- round-robin-notify.sh | 1844 ----------------------------------------------- 3 files changed, 3078 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/21/43621/2 updated (9c98927f3 -> 45559177c)

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/21/43621/2 in repository toolchain/jenkins-scripts. discards 9c98927f3 tcwg_bmk-build.sh: Install armhf perf workaround if one is available adds 45559177c tcwg_bmk-build.sh: Install armhf perf workaround if one is available 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 (9c98927f3) \ N -- N -- N refs/changes/21/43621/2 (45559177c) 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/21/43621/1 updated (e72493fb0 -> a1fadadf5)

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/21/43621/1 in repository toolchain/jenkins-scripts. discards e72493fb0 tcwg_bmk-build.sh: Install armhf perf workaround if one is available new a1fadadf5 tcwg_bmk-build.sh: Install armhf perf workaround if one is available 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 (e72493fb0) \ N -- N -- N refs/changes/21/43621/1 (a1fadadf5) 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/21/43521/3 updated (62430776a -> cb493fc92)

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/21/43521/3 in repository toolchain/jenkins-scripts. discards 62430776a tcwg_gnu-build.sh: Enable bisections for check_gdb jobs adds cb493fc92 tcwg_gnu-build.sh: Enable bisections for check_gdb 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 (62430776a) \ N -- N -- N refs/changes/21/43521/3 (cb493fc92) 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/21/43521/2 updated (4801ed3e1 -> b9e64215a)

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/21/43521/2 in repository toolchain/jenkins-scripts. discards 4801ed3e1 tcwg_gnu-build.sh: Enable bisections for check_gdb jobs new b9e64215a tcwg_gnu-build.sh: Enable bisections for check_gdb 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 (4801ed3e1) \ N -- N -- N refs/changes/21/43521/2 (b9e64215a) 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/21/43521/1 updated (8353f6354 -> eeffc67d5)

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/21/43521/1 in repository toolchain/jenkins-scripts. discards 8353f6354 tcwg_gnu-build.sh: Enable bisections for check_gdb jobs new eeffc67d5 tcwg_gnu-build.sh: Enable bisections for check_gdb 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 (8353f6354) \ N -- N -- N refs/changes/21/43521/1 (eeffc67d5) 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/21/42121/1 updated (66a3b0b9e -> aad3903b1)

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/21/42121/1 in repository toolchain/jenkins-scripts. discards 66a3b0b9e dashboard-generate-squad.sh: Fix again adds aad3903b1 dashboard-generate-squad.sh: Fix again 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 (66a3b0b9e) \ N -- N -- N refs/changes/21/42121/1 (aad3903b1) 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/21/41921/2 updated (133ebb860 -> 81c0d8741)

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/21/41921/2 in repository toolchain/jenkins-scripts. discards 133ebb860 tcwg_dummy-build.sh: Make useful for non-bisect builds adds 81c0d8741 tcwg_dummy-build.sh: Make useful for non-bisect builds 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 (133ebb860) \ N -- N -- N refs/changes/21/41921/2 (81c0d8741) 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/21/41921/1 updated (ef64d7d9e -> 20d575081)

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/21/41921/1 in repository toolchain/jenkins-scripts. discards ef64d7d9e tcwg_dummy-build.sh: Make useful for non-bisect builds adds 20d575081 tcwg_dummy-build.sh: Make useful for non-bisect builds 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 (ef64d7d9e) \ N -- N -- N refs/changes/21/41921/1 (20d575081) 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/21/41321/1 updated (1aa099156 -> 0033f1298)

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/21/41321/1 in repository toolchain/jenkins-scripts. discards 1aa099156 tcwg-benchmark.sh: Use port specified in .ssh/config adds 0033f1298 tcwg-benchmark.sh: Use port specified in .ssh/config 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 (1aa099156) \ N -- N -- N refs/changes/21/41321/1 (0033f1298) 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