Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/66/43366/3 updated (ec76c8327 -> 808380e76)

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/66/43366/3 in repository toolchain/jenkins-scripts. discards ec76c8327 tcwg_bmk-build.sh: Change stored results directory for CI coherency adds 808380e76 tcwg_bmk-build.sh: Change stored results directory for CI coherency 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 (ec76c8327) \ N -- N -- N refs/changes/66/43366/3 (808380e76) 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/66/43366/2 updated (e03f16ae4 -> 013d963f9)

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/66/43366/2 in repository toolchain/jenkins-scripts. discards e03f16ae4 tcwg_bmk-build.sh: Change stored results directory for CI coherency new 013d963f9 tcwg_bmk-build.sh: Change stored results directory for CI coherency 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 (e03f16ae4) \ N -- N -- N refs/changes/66/43366/2 (013d963f9) 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/66/43366/1 updated (ed19be39f -> 33fa5863c)

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/66/43366/1 in repository toolchain/jenkins-scripts. discards ed19be39f tcwg_bmk-build.sh: Change stored results directory for CI coherency new 33fa5863c tcwg_bmk-build.sh: Change stored results directory for CI coherency 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 (ed19be39f) \ N -- N -- N refs/changes/66/43366/1 (33fa5863c) 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/66/43266/3 updated (2a429f56c -> 7b25f2a69)

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/66/43266/3 in repository toolchain/jenkins-scripts. discards 2a429f56c tcwg-benchmark-results.sh: Use compare-results.py. adds 7b25f2a69 tcwg-benchmark-results.sh: Use compare-results.py. 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 (2a429f56c) \ N -- N -- N refs/changes/66/43266/3 (7b25f2a69) 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/66/43266/2 updated (4f301d884 -> b5f85e7ca)

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/66/43266/2 in repository toolchain/jenkins-scripts. discards 4f301d884 tcwg-benchmark-results.sh: Use compare-results.py. new b5f85e7ca tcwg-benchmark-results.sh: Use compare-results.py. 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 (4f301d884) \ N -- N -- N refs/changes/66/43266/2 (b5f85e7ca) 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/66/43266/1 updated (795431596 -> b075a9d99)

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/66/43266/1 in repository toolchain/jenkins-scripts. discards 795431596 tcwg-benchmark-results.sh: Use compare-results.py. new b075a9d99 tcwg-benchmark-results.sh: Use compare-results.py. 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 (795431596) \ N -- N -- N refs/changes/66/43266/1 (b075a9d99) 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/66/43066/2 updated (591b01d77 -> 4d45a9a1a)

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/66/43066/2 in repository toolchain/jenkins-scripts. discards 591b01d77 tcwg_kernel-build.sh: Handle a corner-case when linux commit [...] adds 4d45a9a1a tcwg_kernel-build.sh: Handle a corner-case when linux commit [...] 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 (591b01d77) \ N -- N -- N refs/changes/66/43066/2 (4d45a9a1a) 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/66/43066/1 updated (b9fab419b -> 759a20695)

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/66/43066/1 in repository toolchain/jenkins-scripts. discards b9fab419b tcwg_kernel-build.sh: Handle a corner-case when linux commit [...] new 759a20695 tcwg_kernel-build.sh: Handle a corner-case when linux commit [...] 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 (b9fab419b) \ N -- N -- N refs/changes/66/43066/1 (759a20695) 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/66/42966/1 updated (3fc522758 -> d53278ee0)

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/66/42966/1 in repository toolchain/jenkins-scripts. discards 3fc522758 tcwg-report-stale-rr-jobs.sh,tcwg-report-ci-status.sh: Adapt [...] adds d53278ee0 tcwg-report-stale-rr-jobs.sh,tcwg-report-ci-status.sh: Adapt [...] 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 (3fc522758) \ N -- N -- N refs/changes/66/42966/1 (d53278ee0) 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/66/42166/2 updated (d2f672799 -> 470b04ed3)

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/66/42166/2 in repository toolchain/jenkins-scripts. discards d2f672799 tcwg_bmk-build.sh: use parallel for cpu2017rate adds 470b04ed3 tcwg_bmk-build.sh: use parallel for cpu2017rate 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 (d2f672799) \ N -- N -- N refs/changes/66/42166/2 (470b04ed3) 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