Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/64/40164/2 updated (b66bd8f54 -> 7086e23c4)

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/2 in repository toolchain/jenkins-scripts. discards b66bd8f54 Merge vect and perf metric data. new 7086e23c4 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 (b66bd8f54) \ N -- N -- N refs/changes/64/40164/2 (7086e23c4) 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/40164/1 updated (c1f0288ed -> 9adb88e0c)

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/1 in repository toolchain/jenkins-scripts. discards c1f0288ed Merge vect and perf metric data. new 9adb88e0c 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 (c1f0288ed) \ N -- N -- N refs/changes/64/40164/1 (9adb88e0c) 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/39364/2 updated (1579de7f8 -> d5a335796)

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/39364/2 in repository toolchain/jenkins-scripts. discards 1579de7f8 round-robin-bisect.sh: Move "rr" declaration earlier discards b05a0b4c0 tcwg_bmk-build.sh: Fix LTO benchmarking adds d5a335796 tcwg_bmk-build.sh: Fix LTO benchmarking 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 (1579de7f8) \ N -- N -- N refs/changes/64/39364/2 (d5a335796) 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 | 849 -------------------------------------------------- 1 file changed, 849 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/64/39364/1 updated (7fce65bd6 -> 8596f0327)

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/39364/1 in repository toolchain/jenkins-scripts. discards 7fce65bd6 round-robin-bisect.sh: Move "rr" declaration earlier discards f720cd469 tcwg_bmk-build.sh: Fix LTO benchmarking adds 8596f0327 tcwg_bmk-build.sh: Fix LTO benchmarking 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 (7fce65bd6) \ N -- N -- N refs/changes/64/39364/1 (8596f0327) 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 | 849 -------------------------------------------------- 1 file changed, 849 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/64/39164/2 updated (c9217545e -> 101f0ed56)

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/39164/2 in repository toolchain/jenkins-scripts. discards c9217545e docker-run.sh: Ignore container cleanup failures and preserve [...] adds 101f0ed56 docker-run.sh: Ignore container cleanup failures and preserve [...] 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 (c9217545e) \ N -- N -- N refs/changes/64/39164/2 (101f0ed56) 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/39164/1 updated (b1d2e8f3e -> 133342da6)

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/39164/1 in repository toolchain/jenkins-scripts. discards b1d2e8f3e docker-run.sh: Ignore container cleanup failures and preserve [...] new 133342da6 docker-run.sh: Ignore container cleanup failures and preserve [...] 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 (b1d2e8f3e) \ N -- N -- N refs/changes/64/39164/1 (133342da6) 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/38964/1 updated (b267c58d7 -> b2e994529)

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/38964/1 in repository toolchain/jenkins-scripts. discards b267c58d7 tcwg-benchmark.sh: Update adds b2e994529 tcwg-benchmark.sh: Update 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 (b267c58d7) \ N -- N -- N refs/changes/64/38964/1 (b2e994529) 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/35264/2 updated (ed174d49a -> 543b80d70)

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/35264/2 in repository toolchain/jenkins-scripts. discards ed174d49a jenkins-helpers.sh: Fix run_step starting step logic adds 543b80d70 jenkins-helpers.sh: Fix run_step starting step logic 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 (ed174d49a) \ N -- N -- N refs/changes/64/35264/2 (543b80d70) 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/35264/1 updated (af42b87e5 -> d4745644b)

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/35264/1 in repository toolchain/jenkins-scripts. discards af42b87e5 jenkins-helpers.sh: Fix run_step starting step logic new d4745644b jenkins-helpers.sh: Fix run_step starting step logic 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 (af42b87e5) \ N -- N -- N refs/changes/64/35264/1 (d4745644b) 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/33564/4 updated (a40448f56 -> 624ba2e9e)

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/33564/4 in repository toolchain/jenkins-scripts. discards a40448f56 tcwg_bmk-build.sh: Allow more cflags combinations adds 624ba2e9e tcwg_bmk-build.sh: Allow more cflags combinations 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 (a40448f56) \ N -- N -- N refs/changes/64/33564/4 (624ba2e9e) 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