Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/86/46686/2 updated (266a49231 -> ed5042a9f)

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/86/46686/2 in repository toolchain/jenkins-scripts. discards 266a49231 tcwg_gnu-build.sh (no_regression_p): Print 'Known failures' h [...] adds ed5042a9f tcwg_gnu-build.sh (no_regression_p): Print 'Known failures' h [...] 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 (266a49231) \ N -- N -- N refs/changes/86/46686/2 (ed5042a9f) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/46686/1 updated (057409c3b -> 72ca72091)

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/86/46686/1 in repository toolchain/jenkins-scripts. discards 057409c3b tcwg_gnu-build.sh (no_regression_p): Print 'Known failures' h [...] adds 72ca72091 tcwg_gnu-build.sh (no_regression_p): Print 'Known failures' h [...] 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 (057409c3b) \ N -- N -- N refs/changes/86/46686/1 (72ca72091) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/46486/2 updated (b79bd855d -> 5ffe5345f)

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/86/46486/2 in repository toolchain/jenkins-scripts. discards b79bd855d lnt-check.sh: script for running lnt checks adds 5ffe5345f lnt-check.sh: script for running lnt checks 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 (b79bd855d) \ N -- N -- N refs/changes/86/46486/2 (5ffe5345f) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/46486/1 updated (6c975069e -> baae94e09)

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/86/46486/1 in repository toolchain/jenkins-scripts. discards 6c975069e lnt-check.sh: script for running lnt checks new baae94e09 lnt-check.sh: script for running lnt checks 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 (6c975069e) \ N -- N -- N refs/changes/86/46486/1 (baae94e09) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/46286/2 updated (d023c76cc -> fec33dfba)

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/86/46286/2 in repository toolchain/jenkins-scripts. discards d023c76cc tcwg-lnt/schemas: change type of status fields adds fec33dfba tcwg-lnt/schemas: change type of status fields 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 (d023c76cc) \ N -- N -- N refs/changes/86/46286/2 (fec33dfba) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/46286/1 updated (fab597a53 -> 883e2d845)

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/86/46286/1 in repository toolchain/jenkins-scripts. discards fab597a53 tcwg-lnt/schemas: change type of status fields new 883e2d845 tcwg-lnt/schemas: change type of status fields 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 (fab597a53) \ N -- N -- N refs/changes/86/46286/1 (883e2d845) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/46186/1 updated (e66588736 -> 950943710)

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/86/46186/1 in repository toolchain/jenkins-scripts. discards e66588736 tcwg-update-lnt-results.sh: add execution rights adds 950943710 tcwg-update-lnt-results.sh: add execution rights 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 (e66588736) \ N -- N -- N refs/changes/86/46186/1 (950943710) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/44786/2 updated (2d7713d85 -> 031b50cc1)

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/86/44786/2 in repository toolchain/jenkins-scripts. discards 2d7713d85 tcwg-update-llvmbot-containers: Remove native armv7-a lnt perf adds 031b50cc1 tcwg-update-llvmbot-containers: Remove native armv7-a lnt perf 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 (2d7713d85) \ N -- N -- N refs/changes/86/44786/2 (031b50cc1) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/44786/1 updated (5053ed010 -> c563f8e07)

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/86/44786/1 in repository toolchain/jenkins-scripts. discards 5053ed010 tcwg-update-llvmbot-containers: Remove native armv7-a lnt perf new c563f8e07 tcwg-update-llvmbot-containers: Remove native armv7-a lnt perf 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 (5053ed010) \ N -- N -- N refs/changes/86/44786/1 (c563f8e07) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/86/44686/7 updated (a1b4b7b34 -> 20fa2a93b)

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/86/44686/7 in repository toolchain/jenkins-scripts. discards a1b4b7b34 jenkins-helpers.sh (convert_args_to_variables): Do not record [...] adds 20fa2a93b jenkins-helpers.sh (convert_args_to_variables): Do not record [...] 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 (a1b4b7b34) \ N -- N -- N refs/changes/86/44686/7 (20fa2a93b) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024