Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/17/41817/1 updated (7b89ce148 -> e2809344c)

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/17/41817/1 in repository toolchain/jenkins-scripts. discards 7b89ce148 round-robin.sh: Rework handling of manifests adds e2809344c round-robin.sh: Rework handling of manifests 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 (7b89ce148) \ N -- N -- N refs/changes/17/41817/1 (e2809344c) 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/17/41117/2 updated (d7bfa18ac -> 08725315f)

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/17/41117/2 in repository toolchain/jenkins-scripts. discards d7bfa18ac tcwg-benchmark-results: specify path of results-internal.csv adds 08725315f tcwg-benchmark-results: specify path of results-internal.csv 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 (d7bfa18ac) \ N -- N -- N refs/changes/17/41117/2 (08725315f) 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/17/41117/1 updated (1541e2f77 -> 0d462d353)

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/17/41117/1 in repository toolchain/jenkins-scripts. discards 1541e2f77 tcwg-benchmark-results: specify path of results-internal.csv new 0d462d353 tcwg-benchmark-results: specify path of results-internal.csv 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 (1541e2f77) \ N -- N -- N refs/changes/17/41117/1 (0d462d353) 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/17/40617/2 updated (9d7623803 -> 1fcc26bbc)

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/17/40617/2 in repository toolchain/jenkins-scripts. discards 9d7623803 tcwg-benchmark-results.sh: Replace perf CSV header for bare m [...] adds 1fcc26bbc tcwg-benchmark-results.sh: Replace perf CSV header for bare m [...] 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 (9d7623803) \ N -- N -- N refs/changes/17/40617/2 (1fcc26bbc) 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/17/40617/1 updated (e52d904b1 -> 19c65a24c)

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/17/40617/1 in repository toolchain/jenkins-scripts. discards e52d904b1 tcwg-benchmark-results.sh: Replace perf CSV header for bare m [...] new 19c65a24c tcwg-benchmark-results.sh: Replace perf CSV header for bare m [...] 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 (e52d904b1) \ N -- N -- N refs/changes/17/40617/1 (19c65a24c) 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/17/40517/1 updated (06d280dc7 -> d6b3344e4)

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/17/40517/1 in repository toolchain/jenkins-scripts. discards 06d280dc7 tcwg_bmk-build.sh: Workaround instabilities of 433.milc and 4 [...] adds d6b3344e4 tcwg_bmk-build.sh: Workaround instabilities of 433.milc and 4 [...] 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 (06d280dc7) \ N -- N -- N refs/changes/17/40517/1 (d6b3344e4) 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/17/40217/1 updated (6382cc45b -> 3357a0f17)

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/17/40217/1 in repository toolchain/jenkins-scripts. discards 6382cc45b Use -fdump-statistics for all gnu benchmarking configs. adds 3357a0f17 Use -fdump-statistics for all gnu benchmarking 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 (6382cc45b) \ N -- N -- N refs/changes/17/40217/1 (3357a0f17) 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/17/39717/2 updated (4786a4785 -> 2a4c7671a)

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/17/39717/2 in repository toolchain/jenkins-scripts. discards 4786a4785 tcwg_bmk-build.sh: Fix email subject for symbol regressions adds 2a4c7671a tcwg_bmk-build.sh: Fix email subject for symbol regressions 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 (4786a4785) \ N -- N -- N refs/changes/17/39717/2 (2a4c7671a) 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/17/39717/1 updated (b1f456d32 -> 4f8e0da86)

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/17/39717/1 in repository toolchain/jenkins-scripts. discards b1f456d32 tcwg_bmk-build.sh: Fix email subject for symbol regressions adds 4f8e0da86 tcwg_bmk-build.sh: Fix email subject for symbol regressions 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 (b1f456d32) \ N -- N -- N refs/changes/17/39717/1 (4f8e0da86) 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/17/39317/1 updated (3414b084c -> 4aa2f35d5)

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/17/39317/1 in repository toolchain/jenkins-scripts. discards 3414b084c tcwg-benchmark-results.sh: Revert part of 7a4337884559d7427a2 [...] adds 4aa2f35d5 tcwg-benchmark-results.sh: Revert part of 7a4337884559d7427a2 [...] 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 (3414b084c) \ N -- N -- N refs/changes/17/39317/1 (4aa2f35d5) 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