Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/22/46222/3 updated (6e6341211 -> 26f1deef6)

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/22/46222/3 in repository toolchain/jenkins-scripts. discards 6e6341211 round-robin-notify.sh,lnt-utils.sh: Add bmk status in lnt results adds 26f1deef6 round-robin-notify.sh,lnt-utils.sh: Add bmk status in lnt 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 (6e6341211) \ N -- N -- N refs/changes/22/46222/3 (26f1deef6) 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/22/46222/2 updated (f26372bb7 -> 40562a340)

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/22/46222/2 in repository toolchain/jenkins-scripts. discards f26372bb7 round-robin-notify.sh,lnt-utils.sh: Add bmk status in lnt results adds 40562a340 round-robin-notify.sh,lnt-utils.sh: Add bmk status in lnt 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 (f26372bb7) \ N -- N -- N refs/changes/22/46222/2 (40562a340) 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/22/46222/1 updated (140490ff2 -> 1fa31cca9)

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/22/46222/1 in repository toolchain/jenkins-scripts. discards 140490ff2 round-robin-notify.sh,lnt-utils.sh: Add bmk status in lnt results adds 1fa31cca9 round-robin-notify.sh,lnt-utils.sh: Add bmk status in lnt 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 (140490ff2) \ N -- N -- N refs/changes/22/46222/1 (1fa31cca9) 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

[binutils-gdb] branch master updated (88141209e25 -> 75ece951b54)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 88141209e25 BFD: Add .relro_padding to list of special sections new de272a5e905 [gdb/exp] Allow internal function to indicate return type new 75ece951b54 [gdb/exp] Fix ptype $_creal/$_cimag The 2 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: gdb/ada-lang.c | 9 +--- gdb/eval.c | 9 ++-- gdb/python/py-value.c | 3 +- gdb/testsuite/gdb.base/complex-parts.exp | 24 ++++++--- gdb/value.c | 84 ++++++++++++++++++++++++++++---- gdb/value.h | 35 ++++++++++--- 6 files changed, 125 insertions(+), 39 deletions(-) -- 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/22/45822/1 updated (45ba72cc5 -> 8d3910ecc)

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/22/45822/1 in repository toolchain/jenkins-scripts. discards 45ba72cc5 tcwg_bmk-build.sh: Rewrite all benchmarking history adds 8d3910ecc tcwg_bmk-build.sh: Rewrite all benchmarking history 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 (45ba72cc5) \ N -- N -- N refs/changes/22/45822/1 (8d3910ecc) 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/22/45722/4 updated (5317741ac -> 79b22576a)

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/22/45722/4 in repository toolchain/jenkins-scripts. discards 5317741ac tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] adds 79b22576a tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] 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 (5317741ac) \ N -- N -- N refs/changes/22/45722/4 (79b22576a) 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/22/45722/3 updated (e41c4e878 -> dd52ff9f8)

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/22/45722/3 in repository toolchain/jenkins-scripts. discards e41c4e878 tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] new dd52ff9f8 tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] 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 (e41c4e878) \ N -- N -- N refs/changes/22/45722/3 (dd52ff9f8) 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/22/45722/2 updated (92b6c2986 -> 6511e4356)

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/22/45722/2 in repository toolchain/jenkins-scripts. discards 92b6c2986 tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] new 6511e4356 tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] 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 (92b6c2986) \ N -- N -- N refs/changes/22/45722/2 (6511e4356) 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/22/45722/1 updated (7f9373c0d -> 7aa65df80)

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/22/45722/1 in repository toolchain/jenkins-scripts. discards 7f9373c0d tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] new 7aa65df80 tcwg-report-stale-rr-jobs.sh: adapt for the new location of b [...] 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 (7f9373c0d) \ N -- N -- N refs/changes/22/45722/1 (7aa65df80) 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/22/45622/4 updated (6736ae8ac -> 347340a2c)

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/22/45622/4 in repository toolchain/jenkins-scripts. discards 6736ae8ac round-robin-notify.sh (print_commits): Improve handling of pr [...] discards 047232cc7 tcwg_bmk-build.sh (benchmark): Improve wait cycle adds 347340a2c tcwg_bmk-build.sh (benchmark): Improve wait cycle 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 (6736ae8ac) \ N -- N -- N refs/changes/22/45622/4 (347340a2c) 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 | 455 ------------- round-robin-bisect.sh | 655 ------------------- round-robin-notify.sh | 1628 ----------------------------------------------- 3 files changed, 2738 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024