Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/43/47043/3 updated (43f41511c -> d5b597b8b)

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/43/47043/3 in repository toolchain/jenkins-scripts. discards 43f41511c jenkins-helpers.sh (get_git_history): Add handling of remote repos adds d5b597b8b jenkins-helpers.sh (get_git_history): Add handling of remote repos 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 (43f41511c) \ N -- N -- N refs/changes/43/47043/3 (d5b597b8b) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/47043/2 updated (fcaf59d41 -> c38939fae)

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/43/47043/2 in repository toolchain/jenkins-scripts. discards fcaf59d41 jenkins-helpers.sh (get_git_history): Add handling of remote repos adds c38939fae jenkins-helpers.sh (get_git_history): Add handling of remote repos 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 (fcaf59d41) \ N -- N -- N refs/changes/43/47043/2 (c38939fae) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/47043/1 updated (561017961 -> e7cf1384d)

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/43/47043/1 in repository toolchain/jenkins-scripts. discards 561017961 jenkins-helpers.sh (get_git_history): Add handling of remote repos new e7cf1384d jenkins-helpers.sh (get_git_history): Add handling of remote repos 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 (561017961) \ N -- N -- N refs/changes/43/47043/1 (e7cf1384d) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/46443/3 updated (57c9f5439 -> a92e4e076)

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/43/46443/3 in repository toolchain/jenkins-scripts. discards 57c9f5439 lnt-utils.sh: Use link for jira card adds a92e4e076 lnt-utils.sh: Use link for jira card 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 (57c9f5439) \ N -- N -- N refs/changes/43/46443/3 (a92e4e076) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/46443/2 updated (a72044d71 -> fb52bf770)

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/43/46443/2 in repository toolchain/jenkins-scripts. discards a72044d71 lnt-utils.sh: Use link for jira card adds fb52bf770 lnt-utils.sh: Use link for jira card 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 (a72044d71) \ N -- N -- N refs/changes/43/46443/2 (fb52bf770) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/46443/1 updated (69b865229 -> 7e65de8cd)

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/43/46443/1 in repository toolchain/jenkins-scripts. discards 69b865229 lnt-utils.sh: Use link for jira card adds 7e65de8cd lnt-utils.sh: Use link for jira card 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 (69b865229) \ N -- N -- N refs/changes/43/46443/1 (7e65de8cd) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/45643/3 updated (ce8e6457e -> 4ad1aa4b4)

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/43/45643/3 in repository toolchain/jenkins-scripts. discards ce8e6457e tcwg_bmk-build.sh: use a smaller curl request to wait for ben [...] adds 4ad1aa4b4 tcwg_bmk-build.sh: use a smaller curl request to wait for ben [...] 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 (ce8e6457e) \ N -- N -- N refs/changes/43/45643/3 (4ad1aa4b4) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/45643/2 updated (0e0df80c1 -> 8ecfd8bb7)

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/43/45643/2 in repository toolchain/jenkins-scripts. discards 0e0df80c1 tcwg_bmk-build.sh: use a smaller curl request to wait for ben [...] new 8ecfd8bb7 tcwg_bmk-build.sh: use a smaller curl request to wait for ben [...] 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 (0e0df80c1) \ N -- N -- N refs/changes/43/45643/2 (8ecfd8bb7) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/45643/1 updated (7eea1b76e -> b5e7f7440)

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/43/45643/1 in repository toolchain/jenkins-scripts. discards 7eea1b76e tcwg_bmk-build.sh: use a smaller curl request to wait for ben [...] new b5e7f7440 tcwg_bmk-build.sh: use a smaller curl request to wait for ben [...] 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 (7eea1b76e) \ N -- N -- N refs/changes/43/45643/1 (b5e7f7440) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/44643/2 updated (3d512624e -> d2228b323)

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/43/44643/2 in repository toolchain/jenkins-scripts. discards 3d512624e generate-cimonitor-dashboard.py: Fix file descriptors leak (2) adds d2228b323 generate-cimonitor-dashboard.py: Fix file descriptors leak (2) 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 (3d512624e) \ N -- N -- N refs/changes/43/44643/2 (d2228b323) 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, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024