Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/51/45651/3 updated (7eacfd71e -> 9485a171d)

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/51/45651/3 in repository toolchain/jenkins-scripts. discards 7eacfd71e round-robin-notify.sh (update_interesting_commits): Add detai [...] discards 11c2ca8e2 tcwg_bmk-build.sh: rename samples-variabilty.py script adds 9485a171d tcwg_bmk-build.sh: rename samples-variabilty.py script 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 (7eacfd71e) \ N -- N -- N refs/changes/51/45651/3 (9485a171d) 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 | 1704 ----------------------------------------------- 3 files changed, 2814 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/45651/2 updated (359c8e061 -> ecc96ac0b)

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/51/45651/2 in repository toolchain/jenkins-scripts. discards 359c8e061 round-robin-notify.sh (update_interesting_commits): Add detai [...] discards f20216f12 round-robin-notify.sh: Cleanup generation of email files discards d67583abd round-robin-notify.sh (print_commits): Improve precommit output discards 0985806cc round-robin-notify.sh (print_commits): Restructure adds ecc96ac0b round-robin-notify.sh (print_commits): Restructure 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 (359c8e061) \ N -- N -- N refs/changes/51/45651/2 (ecc96ac0b) 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 | 1704 ----------------------------------------------- 3 files changed, 2814 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/45651/1 updated (e21bb4d34 -> 1eb4f97f1)

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/51/45651/1 in repository toolchain/jenkins-scripts. discards e21bb4d34 round-robin-notify.sh (update_interesting_commits): Add detai [...] discards 65eb88848 round-robin-notify.sh: Cleanup generation of email files discards d356c61c8 round-robin-notify.sh (print_commits): Improve precommit output discards eb1a881c9 round-robin-notify.sh (print_commits): Restructure adds 1eb4f97f1 round-robin-notify.sh (print_commits): Restructure 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 (e21bb4d34) \ N -- N -- N refs/changes/51/45651/1 (1eb4f97f1) 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 | 1722 ----------------------------------------------- 3 files changed, 2832 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/45351/1 updated (dfc7a13dd -> c2ffb4d9f)

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/51/45351/1 in repository toolchain/jenkins-scripts. discards dfc7a13dd round-robin.sh: finalize manifest even in infrastructure problems new c2ffb4d9f round-robin.sh: finalize manifest even in infrastructure problems 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 (dfc7a13dd) \ N -- N -- N refs/changes/51/45351/1 (c2ffb4d9f) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/44951/1 updated (7dd96c25c -> a9ab048eb)

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/51/44951/1 in repository toolchain/jenkins-scripts. discards 7dd96c25c tcwg_bmk-build.sh: redirect output-bmk-results output to a log file adds a9ab048eb tcwg_bmk-build.sh: redirect output-bmk-results output to a log file 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 (7dd96c25c) \ N -- N -- N refs/changes/51/44951/1 (a9ab048eb) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/44851/1 updated (b03d0bd76 -> d3604638c)

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/51/44851/1 in repository toolchain/jenkins-scripts. discards b03d0bd76 tcwg-benchmark-results.sh: new results taken from artifacts adds d3604638c tcwg-benchmark-results.sh: new results taken from artifacts 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 (b03d0bd76) \ N -- N -- N refs/changes/51/44851/1 (d3604638c) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/44751/1 updated (df200a861 -> 4dc073720)

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/51/44751/1 in repository toolchain/jenkins-scripts. discards df200a861 tcwg_bmk-build.sh: Fix git-annex commands to get the results adds 4dc073720 tcwg_bmk-build.sh: Fix git-annex commands to get the 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 (df200a861) \ N -- N -- N refs/changes/51/44751/1 (4dc073720) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/44651/2 updated (ae0777e8d -> 802ebec98)

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/51/44651/2 in repository toolchain/jenkins-scripts. discards ae0777e8d Revert "generate-cimonitor-dashboard.py: Fix file descriptors leak" adds 802ebec98 Revert "generate-cimonitor-dashboard.py: Fix file descriptors leak" 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 (ae0777e8d) \ N -- N -- N refs/changes/51/44651/2 (802ebec98) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/44651/1 updated (f5790cb28 -> bd83b6481)

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/51/44651/1 in repository toolchain/jenkins-scripts. discards f5790cb28 Revert "generate-cimonitor-dashboard.py: Fix file descriptors leak" new bd83b6481 Revert "generate-cimonitor-dashboard.py: Fix file descriptors leak" 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 (f5790cb28) \ N -- N -- N refs/changes/51/44651/1 (bd83b6481) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/43751/2 updated (5c732a768 -> 3bcb1a426)

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/51/43751/2 in repository toolchain/jenkins-scripts. discards 5c732a768 Revert "jenkins-helpers.sh: Also reduce size of base-artifact [...] adds 3bcb1a426 Revert "jenkins-helpers.sh: Also reduce size of base-artifact [...] 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 (5c732a768) \ N -- N -- N refs/changes/51/43751/2 (3bcb1a426) 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, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024