Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/09/46609/1 updated (ed5d52d5d -> 1e5637853)

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/09/46609/1 in repository toolchain/jenkins-scripts. discards ed5d52d5d Revert "round-robin-notify.sh (print_mail_recipients): Enable [...] discards bb1217e55 tcwg-report-stale-rr-jobs.sh: remove useless fetch adds 1e5637853 tcwg-report-stale-rr-jobs.sh: remove useless fetch 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 (ed5d52d5d) \ N -- N -- N refs/changes/09/46609/1 (1e5637853) 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 | 624 ------------- round-robin-bisect.sh | 686 -------------- round-robin-notify.sh | 2370 ----------------------------------------------- 3 files changed, 3680 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46409/5 updated (46183b459 -> ea040fcbb)

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/09/46409/5 in repository toolchain/jenkins-scripts. discards 46183b459 lnt-utils.sh: Adjust git information adds ea040fcbb lnt-utils.sh: Adjust git information 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 (46183b459) \ N -- N -- N refs/changes/09/46409/5 (ea040fcbb) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46409/4 updated (5c20df79d -> 93fdcd4e5)

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/09/46409/4 in repository toolchain/jenkins-scripts. discards 5c20df79d lnt-utils.sh: Adjust git information adds 93fdcd4e5 lnt-utils.sh: Adjust git information 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 (5c20df79d) \ N -- N -- N refs/changes/09/46409/4 (93fdcd4e5) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46409/3 updated (41eea930a -> ec03276c1)

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/09/46409/3 in repository toolchain/jenkins-scripts. discards 41eea930a lnt-utils.sh: Adjust git information adds ec03276c1 lnt-utils.sh: Adjust git information 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 (41eea930a) \ N -- N -- N refs/changes/09/46409/3 (ec03276c1) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46409/2 updated (6a5fcdb80 -> ce6686357)

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/09/46409/2 in repository toolchain/jenkins-scripts. discards 6a5fcdb80 lnt-utils.sh: Adjust git information new ce6686357 lnt-utils.sh: Adjust git information 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 (6a5fcdb80) \ N -- N -- N refs/changes/09/46409/2 (ce6686357) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46409/1 updated (ca3f96094 -> f7cd061dc)

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/09/46409/1 in repository toolchain/jenkins-scripts. discards ca3f96094 lnt-utils.sh: Adjust git information new f7cd061dc lnt-utils.sh: Adjust git information 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 (ca3f96094) \ N -- N -- N refs/changes/09/46409/1 (f7cd061dc) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46209/3 updated (288817258 -> 538568980)

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/09/46209/3 in repository toolchain/jenkins-scripts. discards 288817258 tcwg_bmk-build.sh: Upgrade major revision for some of the bmk [...] adds 538568980 tcwg_bmk-build.sh: Upgrade major revision for some of the bmk [...] 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 (288817258) \ N -- N -- N refs/changes/09/46209/3 (538568980) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46209/2 updated (f4f54d120 -> f50aa3d51)

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/09/46209/2 in repository toolchain/jenkins-scripts. discards f4f54d120 tcwg_bmk-build.sh: Upgrade major revision for some of the bmk [...] new f50aa3d51 tcwg_bmk-build.sh: Upgrade major revision for some of the bmk [...] 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 (f4f54d120) \ N -- N -- N refs/changes/09/46209/2 (f50aa3d51) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/46209/1 updated (58af51c82 -> fcff5c1a7)

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/09/46209/1 in repository toolchain/jenkins-scripts. discards 58af51c82 tcwg_bmk-build.sh: Upgrade major revision new fcff5c1a7 tcwg_bmk-build.sh: Upgrade major revision 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 (58af51c82) \ N -- N -- N refs/changes/09/46209/1 (fcff5c1a7) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/09/45909/5 updated (b5355a38a -> e18ba4741)

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/09/45909/5 in repository toolchain/jenkins-scripts. discards b5355a38a tcwg-cleanup-stale-results.sh: Adapt script for new location [...] adds e18ba4741 tcwg-cleanup-stale-results.sh: Adapt script for new location [...] 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 (b5355a38a) \ N -- N -- N refs/changes/09/45909/5 (e18ba4741) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024