Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/64/45864/3 updated (97176bee7 -> 7e00cb07a)

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/64/45864/3 in repository toolchain/jenkins-scripts. discards 97176bee7 tcwg_gnu-build.sh: Define pretty_project and pretty_config adds 7e00cb07a tcwg_gnu-build.sh: Define pretty_project and pretty_config 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 (97176bee7) \ N -- N -- N refs/changes/64/45864/3 (7e00cb07a) 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/64/45864/2 updated (57fa071c0 -> c6451ba9b)

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/64/45864/2 in repository toolchain/jenkins-scripts. discards 57fa071c0 tcwg_gnu-build.sh: Define pretty_project and pretty_config new c6451ba9b tcwg_gnu-build.sh: Define pretty_project and pretty_config 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 (57fa071c0) \ N -- N -- N refs/changes/64/45864/2 (c6451ba9b) 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/64/45864/1 updated (71bb99499 -> 4c6099b81)

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/64/45864/1 in repository toolchain/jenkins-scripts. discards 71bb99499 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Don' [...] new 4c6099b81 tcwg_gnu-config.sh (settings_for_ci_project_and_config): Don' [...] 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 (71bb99499) \ N -- N -- N refs/changes/64/45864/1 (4c6099b81) 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/64/44164/1 updated (b60fc3c1a -> 9709523ee)

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/64/44164/1 in repository toolchain/jenkins-scripts. discards b60fc3c1a tcwg_gnu-build.sh: Improve robustness of testsuite configurations adds 9709523ee tcwg_gnu-build.sh: Improve robustness of testsuite configurations 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 (b60fc3c1a) \ N -- N -- N refs/changes/64/44164/1 (9709523ee) 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/64/43264/1 updated (fae8d1c54 -> 3619cfd0d)

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/64/43264/1 in repository toolchain/jenkins-scripts. discards fae8d1c54 tcwg_gnu-build.sh: Refactor loop that reads fails.sum adds 3619cfd0d tcwg_gnu-build.sh: Refactor loop that reads fails.sum 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 (fae8d1c54) \ N -- N -- N refs/changes/64/43264/1 (3619cfd0d) 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/64/41864/3 updated (786408882 -> 276dc1388)

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/64/41864/3 in repository toolchain/jenkins-scripts. discards 786408882 round-robin.sh (check_regression): Move parts of code to new [...] adds 276dc1388 round-robin.sh (check_regression): Move parts of code to new [...] 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 (786408882) \ N -- N -- N refs/changes/64/41864/3 (276dc1388) 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/64/41864/2 updated (aa8a88e73 -> 9aa6e56e6)

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/64/41864/2 in repository toolchain/jenkins-scripts. discards aa8a88e73 round-robin.sh (check_regression): Move parts of code to new [...] new 9aa6e56e6 round-robin.sh (check_regression): Move parts of code to new [...] 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 (aa8a88e73) \ N -- N -- N refs/changes/64/41864/2 (9aa6e56e6) 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/64/41864/1 updated (be83c6a59 -> dc8cb6257)

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/64/41864/1 in repository toolchain/jenkins-scripts. discards be83c6a59 round-robin.sh (check_regression): Move parts of code to new [...] new dc8cb6257 round-robin.sh (check_regression): Move parts of code to new [...] 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 (be83c6a59) \ N -- N -- N refs/changes/64/41864/1 (dc8cb6257) 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/64/41564/1 updated (3f2c2ee8b -> f079d7524)

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/64/41564/1 in repository toolchain/jenkins-scripts. discards 3f2c2ee8b tcwg-report-stale-rr-jobs.sh: Fix shellcheck adds f079d7524 tcwg-report-stale-rr-jobs.sh: Fix shellcheck 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 (3f2c2ee8b) \ N -- N -- N refs/changes/64/41564/1 (f079d7524) 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/64/40164/3 updated (aabb29bd5 -> b6f60dcec)

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/64/40164/3 in repository toolchain/jenkins-scripts. discards aabb29bd5 Merge vect and perf metric data. adds b6f60dcec Merge vect and perf metric data. 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 (aabb29bd5) \ N -- N -- N refs/changes/64/40164/3 (b6f60dcec) 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