Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/27/31227/2 updated (7b30ff45b -> 2f38ad1ef)

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/27/31227/2 in repository toolchain/jenkins-scripts. discards 7b30ff45b tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops adds 2f38ad1ef tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops 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 (7b30ff45b) \ N -- N -- N refs/changes/27/31227/2 (2f38ad1ef) 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/27/31227/1 updated (4c3af25d6 -> 1940f66b7)

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/27/31227/1 in repository toolchain/jenkins-scripts. discards 4c3af25d6 tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops new 1940f66b7 tcwg_bmk-build.sh: Make benchmark() resilient to ssh drops 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 (4c3af25d6) \ N -- N -- N refs/changes/27/31227/1 (1940f66b7) 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/27/30527/2 updated (acd4dfe5c -> 54c1456aa)

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/27/30527/2 in repository toolchain/jenkins-scripts. discards acd4dfe5c start-container-docker.sh, docker-run.sh: Rework --ssh_info support adds 54c1456aa start-container-docker.sh, docker-run.sh: Rework --ssh_info support 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 (acd4dfe5c) \ N -- N -- N refs/changes/27/30527/2 (54c1456aa) 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/27/30527/1 updated (d7f7e2fd2 -> ea042e4c1)

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/27/30527/1 in repository toolchain/jenkins-scripts. discards d7f7e2fd2 start-container-docker.sh, docker-run.sh: Rework --ssh_info support adds ea042e4c1 start-container-docker.sh, docker-run.sh: Rework --ssh_info support 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 (d7f7e2fd2) \ N -- N -- N refs/changes/27/30527/1 (ea042e4c1) 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/26/47226/1 updated (681cf77bf -> 461d62baf)

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/26/47226/1 in repository toolchain/jenkins-scripts. discards 681cf77bf tcwg-config.sh: handle all gnu projects in config file adds 461d62baf tcwg-config.sh: handle all gnu projects in config 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 (681cf77bf) \ N -- N -- N refs/changes/26/47226/1 (461d62baf) 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/26/46726/3 updated (7d4f3bc35 -> adfcdc6d8)

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/26/46726/3 in repository toolchain/jenkins-scripts. discards 7d4f3bc35 tcwg_bmk-build.sh: Include current compare-results.csv to com [...] adds adfcdc6d8 tcwg_bmk-build.sh: Include current compare-results.csv to com [...] 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 (7d4f3bc35) \ N -- N -- N refs/changes/26/46726/3 (adfcdc6d8) 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/26/46726/2 updated (1fd86f152 -> ca4ed0730)

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/26/46726/2 in repository toolchain/jenkins-scripts. discards 1fd86f152 tcwg_bmk-build.sh: Include current compare-results.csv to com [...] adds ca4ed0730 tcwg_bmk-build.sh: Include current compare-results.csv to com [...] 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 (1fd86f152) \ N -- N -- N refs/changes/26/46726/2 (ca4ed0730) 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/26/46726/1 updated (1fac15a73 -> 24230eac3)

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/26/46726/1 in repository toolchain/jenkins-scripts. discards 1fac15a73 tcwg_bmk-build.sh: Include current compare-results.csv to com [...] adds 24230eac3 tcwg_bmk-build.sh: Include current compare-results.csv to com [...] 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 (1fac15a73) \ N -- N -- N refs/changes/26/46726/1 (24230eac3) 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/26/45826/1 updated (8a60c06a3 -> a564342fe)

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/26/45826/1 in repository toolchain/jenkins-scripts. discards 8a60c06a3 pw-apply.sh: Fix corner-case adds a564342fe pw-apply.sh: Fix corner-case 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 (8a60c06a3) \ N -- N -- N refs/changes/26/45826/1 (a564342fe) 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/26/45726/2 updated (07929171c -> b44eafa1f)

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/26/45726/2 in repository toolchain/jenkins-scripts. discards 07929171c tcwg-report-stale-rr-jobs.sh: formatting changes adds b44eafa1f tcwg-report-stale-rr-jobs.sh: formatting changes 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 (07929171c) \ N -- N -- N refs/changes/26/45726/2 (b44eafa1f) 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