Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/19/44519/1 updated (0f31537fd -> 5812e8b2c)

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/19/44519/1 in repository toolchain/jenkins-scripts. discards 0f31537fd jenkins-helpers.sh (clone_or_update_repo_no_checkout): Fix bi [...] adds 5812e8b2c jenkins-helpers.sh (clone_or_update_repo_no_checkout): Fix bi [...] 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 (0f31537fd) \ N -- N -- N refs/changes/19/44519/1 (5812e8b2c) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44419/5 updated (056986376 -> 01cf9bd03)

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/19/44419/5 in repository toolchain/jenkins-scripts. discards 056986376 start-container-docker.sh: Rework processing of bind-mounts adds 01cf9bd03 start-container-docker.sh: Rework processing of bind-mounts 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 (056986376) \ N -- N -- N refs/changes/19/44419/5 (01cf9bd03) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44419/4 updated (a52ceb132 -> 54664c955)

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/19/44419/4 in repository toolchain/jenkins-scripts. discards a52ceb132 start-container-docker.sh: Rework processing of bind-mounts adds 54664c955 start-container-docker.sh: Rework processing of bind-mounts 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 (a52ceb132) \ N -- N -- N refs/changes/19/44419/4 (54664c955) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44419/3 updated (8dd13f4ea -> 11a0c4578)

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/19/44419/3 in repository toolchain/jenkins-scripts. discards 8dd13f4ea start-container-docker.sh: Rework processing of bind-mounts adds 11a0c4578 start-container-docker.sh: Rework processing of bind-mounts 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 (8dd13f4ea) \ N -- N -- N refs/changes/19/44419/3 (11a0c4578) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44419/2 updated (9f78c79cc -> 748d2271e)

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/19/44419/2 in repository toolchain/jenkins-scripts. discards 9f78c79cc start-container-docker.sh: Rework processing of bind-mounts adds 748d2271e start-container-docker.sh: Rework processing of bind-mounts 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 (9f78c79cc) \ N -- N -- N refs/changes/19/44419/2 (748d2271e) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44419/1 updated (c45290cdf -> 69929be53)

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/19/44419/1 in repository toolchain/jenkins-scripts. discards c45290cdf start-container-docker.sh: Rework processing of bind-mounts adds 69929be53 start-container-docker.sh: Rework processing of bind-mounts 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 (c45290cdf) \ N -- N -- N refs/changes/19/44419/1 (69929be53) 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44319/3 updated (75ea11516 -> 1a49440a0)

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/19/44319/3 in repository toolchain/jenkins-scripts. discards 75ea11516 round-robin-notify.sh: Include component name, reduce 'short' [...] discards 70d80c710 tcwg_bmk-build.sh: Add symlink to ease navigation in jenkins [...] adds 1a49440a0 tcwg_bmk-build.sh: Add symlink to ease navigation in jenkins [...] 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 (75ea11516) \ N -- N -- N refs/changes/19/44319/3 (1a49440a0) 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 | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44319/2 updated (14938f5c7 -> e49149f7a)

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/19/44319/2 in repository toolchain/jenkins-scripts. discards 14938f5c7 round-robin-notify.sh: Include component name, reduce 'short' [...] discards 4fcc9a5a5 generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] adds e49149f7a generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] 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 (14938f5c7) \ N -- N -- N refs/changes/19/44319/2 (e49149f7a) 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 | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/44319/1 updated (c47ff7aca -> e49149f7a)

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/19/44319/1 in repository toolchain/jenkins-scripts. discards c47ff7aca round-robin-notify.sh: Include component name, reduce 'short' [...] discards 4fcc9a5a5 generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] adds e49149f7a generate-cimonitor-dashboard.py: integrate bmk_results in sta [...] 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 (c47ff7aca) \ N -- N -- N refs/changes/19/44319/1 (e49149f7a) 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 | 647 -------------------------- round-robin-notify.sh | 1231 ------------------------------------------------- 2 files changed, 1878 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, 1 week

[toolchain/jenkins-scripts] reference refs/changes/19/43419/2 updated (fcaefda99 -> 1e48e4c26)

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/19/43419/2 in repository toolchain/jenkins-scripts. discards fcaefda99 tcwg_bmk-build.sh: Use bmk-specific-threshold.csv for output- [...] adds 1e48e4c26 tcwg_bmk-build.sh: Use bmk-specific-threshold.csv for output- [...] 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 (fcaefda99) \ N -- N -- N refs/changes/19/43419/2 (1e48e4c26) 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, 1 week

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024