Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/25/32425/1 updated (20e2926aa -> d65faafcb)

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/25/32425/1 in repository toolchain/jenkins-scripts. discards 20e2926aa tcwg_bmk-build.sh: Don't restric number of DSOs adds d65faafcb tcwg_bmk-build.sh: Don't restric number of DSOs 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 (20e2926aa) \ N -- N -- N refs/changes/25/32425/1 (d65faafcb) 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/25/31925/1 updated (c8bb8d32e -> 102178445)

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/25/31925/1 in repository toolchain/jenkins-scripts. discards c8bb8d32e start-container-docker.sh: Add more debug traces adds 102178445 start-container-docker.sh: Add more debug traces 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 (c8bb8d32e) \ N -- N -- N refs/changes/25/31925/1 (102178445) 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/25/29725/2 updated (72d44507b -> debe4d11b)

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/25/29725/2 in repository toolchain/jenkins-scripts. discards 72d44507b jenkins-helpers.sh: New helper fresh_dir adds debe4d11b jenkins-helpers.sh: New helper fresh_dir 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 (72d44507b) \ N -- N -- N refs/changes/25/29725/2 (debe4d11b) 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/25/29725/1 updated (7acf397da -> 9b012fc78)

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/25/29725/1 in repository toolchain/jenkins-scripts. discards 7acf397da jenkins-helpers.sh: New helper fresh_dir adds 9b012fc78 jenkins-helpers.sh: New helper fresh_dir 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 (7acf397da) \ N -- N -- N refs/changes/25/29725/1 (9b012fc78) 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/25/29425/3 updated (72cc72574 -> 219994ea8)

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/25/29425/3 in repository toolchain/jenkins-scripts. discards 72cc72574 tcwg_kernel-build.sh: Rename reset_artifacts depend only on ${rr[]} adds 219994ea8 tcwg_kernel-build.sh: Rename reset_artifacts depend only on ${rr[]} 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 (72cc72574) \ N -- N -- N refs/changes/25/29425/3 (219994ea8) 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/25/29425/2 updated (304ba1333 -> 0e85bf0d5)

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/25/29425/2 in repository toolchain/jenkins-scripts. discards 304ba1333 tcwg_kernel-build.sh: Make reset_artifacts depend only on ${rr[]} new 0e85bf0d5 tcwg_kernel-build.sh: Make reset_artifacts depend only on ${rr[]} 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 (304ba1333) \ N -- N -- N refs/changes/25/29425/2 (0e85bf0d5) 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/25/29425/1 updated (46e4d0a4a -> bf2b2cb11)

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/25/29425/1 in repository toolchain/jenkins-scripts. discards 46e4d0a4a tcwg_kernel-build.sh: Rename reset_artifacts depend only on ${rr[]} adds bf2b2cb11 tcwg_kernel-build.sh: Rename reset_artifacts depend only on ${rr[]} 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 (46e4d0a4a) \ N -- N -- N refs/changes/25/29425/1 (bf2b2cb11) 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/24/46924/2 updated (5dc27bf2e -> c98513796)

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/24/46924/2 in repository toolchain/jenkins-scripts. discards 5dc27bf2e round-robin.sh: extend create_trigger_files for dynamic compo [...] adds c98513796 round-robin.sh: extend create_trigger_files for dynamic compo [...] 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 (5dc27bf2e) \ N -- N -- N refs/changes/24/46924/2 (c98513796) 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/24/46924/1 updated (fc61f8615 -> 9fe12a218)

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/24/46924/1 in repository toolchain/jenkins-scripts. discards fc61f8615 round-robin.sh: extend create_trigger_files for dynamic compo [...] new 9fe12a218 round-robin.sh: extend create_trigger_files for dynamic compo [...] 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 (fc61f8615) \ N -- N -- N refs/changes/24/46924/1 (9fe12a218) 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/24/46724/3 updated (f2b7f3842 -> 2ebde3688)

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/24/46724/3 in repository toolchain/jenkins-scripts. discards f2b7f3842 lnt-utils.sh,tcwg-lnt/schema: rename variation field into exe [...] adds 2ebde3688 lnt-utils.sh,tcwg-lnt/schema: rename variation field into exe [...] 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 (f2b7f3842) \ N -- N -- N refs/changes/24/46724/3 (2ebde3688) 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