Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/39/42439/2 updated (33666bfe9 -> 3ca2fecd5)

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/39/42439/2 in repository toolchain/jenkins-scripts. discards 33666bfe9 dashboard-generate-squad.sh: more robust for reading csv results adds 3ca2fecd5 dashboard-generate-squad.sh: more robust for reading csv results 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 (33666bfe9) \ N -- N -- N refs/changes/39/42439/2 (3ca2fecd5) 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/39/42439/1 updated (2bb29bb7a -> f6b6c7126)

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/39/42439/1 in repository toolchain/jenkins-scripts. discards 2bb29bb7a dashboard-generate-squad.sh: more robust for reading csv results new f6b6c7126 dashboard-generate-squad.sh: more robust for reading csv results 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 (2bb29bb7a) \ N -- N -- N refs/changes/39/42439/1 (f6b6c7126) 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/39/42039/2 updated (5bd270bbb -> 138210297)

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/39/42039/2 in repository toolchain/jenkins-scripts. discards 5bd270bbb round-robin-bisect.sh: Simplify handling of commits_to_test discards 0b1ba4e21 Make "git reset --hard" quiet adds 138210297 Make "git reset --hard" quiet 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 (5bd270bbb) \ N -- N -- N refs/changes/39/42039/2 (138210297) 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 | 648 -------------------------------------------------- round-robin-notify.sh | 224 ----------------- 2 files changed, 872 deletions(-) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/39/42039/1 updated (7ce738a27 -> af94370cc)

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/39/42039/1 in repository toolchain/jenkins-scripts. discards 7ce738a27 round-robin-bisect.sh: Simplify handling of commits_to_test discards ba561d296 Make "git reset --hard" quiet adds af94370cc Make "git reset --hard" quiet 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 (7ce738a27) \ N -- N -- N refs/changes/39/42039/1 (af94370cc) 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 | 648 -------------------------------------------------- round-robin-notify.sh | 224 ----------------- 2 files changed, 872 deletions(-) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/39/41939/1 updated (50912f898 -> 452974261)

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/39/41939/1 in repository toolchain/jenkins-scripts. discards 50912f898 tcwg_bmk-build.sh, dashboard*: factorize dashboard routines for bmk adds 452974261 tcwg_bmk-build.sh, dashboard*: factorize dashboard routines for bmk 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 (50912f898) \ N -- N -- N refs/changes/39/41939/1 (452974261) 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/39/41739/1 updated (278e2de6b -> a54c9eba8)

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/39/41739/1 in repository toolchain/jenkins-scripts. discards 278e2de6b tcwg_bmk-build.sh: Pass -fdump-tree-vect-details to gather da [...] adds a54c9eba8 tcwg_bmk-build.sh: Pass -fdump-tree-vect-details to gather da [...] 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 (278e2de6b) \ N -- N -- N refs/changes/39/41739/1 (a54c9eba8) 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/39/39739/1 updated (0e38239e6 -> c7522ba6d)

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/39/39739/1 in repository toolchain/jenkins-scripts. discards 0e38239e6 tcwg_bmk-build.sh: Fix aliasing between $bmk variables adds c7522ba6d tcwg_bmk-build.sh: Fix aliasing between $bmk variables 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 (0e38239e6) \ N -- N -- N refs/changes/39/39739/1 (c7522ba6d) 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/39/39539/1 updated (410d3286a -> 3ced820de)

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/39/39539/1 in repository toolchain/jenkins-scripts. discards 410d3286a tcwg_gnu-build.sh: Fix ERRORs creeping into flaky XFAILs adds 3ced820de tcwg_gnu-build.sh: Fix ERRORs creeping into flaky XFAILs 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 (410d3286a) \ N -- N -- N refs/changes/39/39539/1 (3ced820de) 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/39/39339/2 updated (1d6565e7c -> a55715d10)

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/39/39339/2 in repository toolchain/jenkins-scripts. discards 1d6565e7c tcwg-benchmark.sh, tcwg_bmk-build.sh: Support benchmarking on APMs adds a55715d10 tcwg-benchmark.sh, tcwg_bmk-build.sh: Support benchmarking on APMs 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 (1d6565e7c) \ N -- N -- N refs/changes/39/39339/2 (a55715d10) 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/39/39339/1 updated (bef83d0d4 -> e1ae0ab5c)

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/39/39339/1 in repository toolchain/jenkins-scripts. discards bef83d0d4 tcwg-benchmark.sh, tcwg_bmk-build.sh: Support benchmarking on APMs adds e1ae0ab5c tcwg-benchmark.sh, tcwg_bmk-build.sh: Support benchmarking on APMs 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 (bef83d0d4) \ N -- N -- N refs/changes/39/39339/1 (e1ae0ab5c) 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