Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/57/41957/1 updated (fc5d4228b -> bcb7134ce)

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/57/41957/1 in repository toolchain/jenkins-scripts. discards fc5d4228b tcwg_bmk-build.sh: Fix reporting for code-size metric new bcb7134ce tcwg_bmk-build.sh: Fix reporting for code-size metric 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 (fc5d4228b) \ N -- N -- N refs/changes/57/41957/1 (bcb7134ce) 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/57/41857/3 updated (3c3ee38c8 -> 3ef03b635)

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/57/41857/3 in repository toolchain/jenkins-scripts. discards 3c3ee38c8 round-robin.sh (check_regression): Fix generation of trigger-build-* adds 3ef03b635 round-robin.sh (check_regression): Fix generation of trigger-build-* 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 (3c3ee38c8) \ N -- N -- N refs/changes/57/41857/3 (3ef03b635) 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/57/41857/2 updated (dcb34ffcc -> eb6c2df64)

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/57/41857/2 in repository toolchain/jenkins-scripts. discards dcb34ffcc round-robin.sh (check_regression): Fix generation of trigger-build-* new eb6c2df64 round-robin.sh (check_regression): Fix generation of trigger-build-* 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 (dcb34ffcc) \ N -- N -- N refs/changes/57/41857/2 (eb6c2df64) 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/57/41857/1 updated (5e961b65d -> 31f4f120d)

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/57/41857/1 in repository toolchain/jenkins-scripts. discards 5e961b65d round-robin.sh (check_regression): Fix generation of trigger-build-* new 31f4f120d round-robin.sh (check_regression): Fix generation of trigger-build-* 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 (5e961b65d) \ N -- N -- N refs/changes/57/41857/1 (31f4f120d) 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/57/41057/3 updated (a8e0f9fc0 -> 60cb37c02)

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/57/41057/3 in repository toolchain/jenkins-scripts. discards a8e0f9fc0 Keep a copy of results.csv, for containing mangled symbol names. adds 60cb37c02 Keep a copy of results.csv, for containing mangled symbol names. 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 (a8e0f9fc0) \ N -- N -- N refs/changes/57/41057/3 (60cb37c02) 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/57/41057/2 updated (4fb747920 -> 7f160f63a)

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/57/41057/2 in repository toolchain/jenkins-scripts. discards 4fb747920 Keep a copy of results.csv, for containing mangled symbol names. new 7f160f63a Keep a copy of results.csv, for containing mangled symbol names. 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 (4fb747920) \ N -- N -- N refs/changes/57/41057/2 (7f160f63a) 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/57/41057/1 updated (075c92138 -> a55a41600)

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/57/41057/1 in repository toolchain/jenkins-scripts. discards 075c92138 Keep a copy of results.csv, for containing mangled symbol names. new a55a41600 Keep a copy of results.csv, for containing mangled symbol names. 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 (075c92138) \ N -- N -- N refs/changes/57/41057/1 (a55a41600) 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/57/39657/1 updated (424153a8d -> c7171726c)

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/57/39657/1 in repository toolchain/jenkins-scripts. discards 424153a8d round-robin-bisect.sh: Update email settings discards 22dc1c712 round-robin.sh: Remove obsolete workarounds adds c7171726c round-robin.sh: Remove obsolete workarounds 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 (424153a8d) \ N -- N -- N refs/changes/57/39657/1 (c7171726c) 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-bisect.sh | 866 -------------------------------------------------- 1 file changed, 866 deletions(-) delete mode 100755 round-robin-bisect.sh -- 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/57/39257/4 updated (85c1c90af -> 7b1e98c6e)

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/57/39257/4 in repository toolchain/jenkins-scripts. discards 85c1c90af [NFC] round-robin.sh: Cleanup reset_artifacts() adds 7b1e98c6e [NFC] round-robin.sh: Cleanup reset_artifacts() 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 (85c1c90af) \ N -- N -- N refs/changes/57/39257/4 (7b1e98c6e) 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/57/39257/3 updated (f5dff5e9e -> 663763f3d)

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/57/39257/3 in repository toolchain/jenkins-scripts. discards f5dff5e9e [NFC] round-robin.sh: Cleanup reset_artifacts() adds 663763f3d [NFC] round-robin.sh: Cleanup reset_artifacts() 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 (f5dff5e9e) \ N -- N -- N refs/changes/57/39257/3 (663763f3d) 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