Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/48/46448/1 updated (f5a944768 -> b42dd9df2)

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/48/46448/1 in repository toolchain/jenkins-scripts. discards f5a944768 jenkins-helpers.sh (git_annex_upload): Optimize re-upload of [...] adds b42dd9df2 jenkins-helpers.sh (git_annex_upload): Optimize re-upload of [...] 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 (f5a944768) \ N -- N -- N refs/changes/48/46448/1 (b42dd9df2) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/46148/1 updated (b4867e813 -> 55e8864d8)

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/48/46148/1 in repository toolchain/jenkins-scripts. discards b4867e813 tcwg-lnt: fix temp workaround for running lnt on jammy adds 55e8864d8 tcwg-lnt: fix temp workaround for running lnt on jammy 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 (b4867e813) \ N -- N -- N refs/changes/48/46148/1 (55e8864d8) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/45648/2 updated (0985806cc -> ecc96ac0b)

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/48/45648/2 in repository toolchain/jenkins-scripts. discards 0985806cc round-robin-notify.sh (print_commits): Restructure adds ecc96ac0b round-robin-notify.sh (print_commits): Restructure 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 (0985806cc) \ N -- N -- N refs/changes/48/45648/2 (ecc96ac0b) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/45648/1 updated (eb1a881c9 -> 1eb4f97f1)

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/48/45648/1 in repository toolchain/jenkins-scripts. discards eb1a881c9 round-robin-notify.sh (print_commits): Restructure adds 1eb4f97f1 round-robin-notify.sh (print_commits): Restructure 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 (eb1a881c9) \ N -- N -- N refs/changes/48/45648/1 (1eb4f97f1) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/44548/2 updated (b91638893 -> 74aba9eab)

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/48/44548/2 in repository toolchain/jenkins-scripts. discards b91638893 tcwg-benchmark-results.sh: Compare against compare-results-in [...] adds 74aba9eab tcwg-benchmark-results.sh: Compare against compare-results-in [...] 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 (b91638893) \ N -- N -- N refs/changes/48/44548/2 (74aba9eab) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/44548/1 updated (773a67281 -> 841bfc0f0)

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/48/44548/1 in repository toolchain/jenkins-scripts. discards 773a67281 tcwg-benchmark-results.sh: Compare against compare-results-in [...] new 841bfc0f0 tcwg-benchmark-results.sh: Compare against compare-results-in [...] 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 (773a67281) \ N -- N -- N refs/changes/48/44548/1 (841bfc0f0) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/44248/2 updated (fdb7c6488 -> 8e7884822)

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/48/44248/2 in repository toolchain/jenkins-scripts. discards fdb7c6488 tcwg_gnu-build.sh: Update handling of tcwg_gcc_* configurations adds 8e7884822 tcwg_gnu-build.sh: Update handling of tcwg_gcc_* 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 (fdb7c6488) \ N -- N -- N refs/changes/48/44248/2 (8e7884822) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/44248/1 updated (0b1ee1f64 -> 2f3b3cb32)

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/48/44248/1 in repository toolchain/jenkins-scripts. discards 0b1ee1f64 tcwg_gnu-build.sh: Update handling of tcwg_gcc_* configurations adds 2f3b3cb32 tcwg_gnu-build.sh: Update handling of tcwg_gcc_* 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 (0b1ee1f64) \ N -- N -- N refs/changes/48/44248/1 (2f3b3cb32) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/43548/2 updated (09265fffe -> 81fd361d7)

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/48/43548/2 in repository toolchain/jenkins-scripts. discards 09265fffe tcwg_bmk-build.sh: move call to diff-bmk-results after symbol [...] adds 81fd361d7 tcwg_bmk-build.sh: move call to diff-bmk-results after symbol [...] 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 (09265fffe) \ N -- N -- N refs/changes/48/43548/2 (81fd361d7) 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.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/48/43548/1 updated (6c0e81819 -> b4aa5aa44)

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/48/43548/1 in repository toolchain/jenkins-scripts. discards 6c0e81819 tcwg_bmk-build.sh: move call to diff-bmk-results after symbol [...] adds b4aa5aa44 tcwg_bmk-build.sh: move call to diff-bmk-results after symbol [...] 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 (6c0e81819) \ N -- N -- N refs/changes/48/43548/1 (b4aa5aa44) 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.

11 months, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024