Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/29/41829/1 updated (0a758afff -> f654c24e6)

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/29/41829/1 in repository toolchain/jenkins-scripts. discards 0a758afff tcwg-report-stale-rr-jobs.sh: temporary fix adds f654c24e6 tcwg-report-stale-rr-jobs.sh: temporary fix 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 (0a758afff) \ N -- N -- N refs/changes/29/41829/1 (f654c24e6) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/40229/1 updated (e46975c45 -> 09f57eea5)

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/29/40229/1 in repository toolchain/jenkins-scripts. discards e46975c45 tcwg_bmk-build.sh: Workaround tcwg_bmk_stm32 failing adds 09f57eea5 tcwg_bmk-build.sh: Workaround tcwg_bmk_stm32 failing 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 (e46975c45) \ N -- N -- N refs/changes/29/40229/1 (09f57eea5) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39929/2 updated (270b40a92 -> f8b285000)

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/29/39929/2 in repository toolchain/jenkins-scripts. discards 270b40a92 tcwg_bmk-build.sh: Update logic that waits for jenkins job co [...] adds f8b285000 tcwg_bmk-build.sh: Update logic that waits for jenkins job co [...] 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 (270b40a92) \ N -- N -- N refs/changes/29/39929/2 (f8b285000) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39929/1 updated (876141167 -> 98b1e6a26)

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/29/39929/1 in repository toolchain/jenkins-scripts. discards 876141167 tcwg_bmk-build.sh: Update logic that waits for jenkins job co [...] new 98b1e6a26 tcwg_bmk-build.sh: Update logic that waits for jenkins job co [...] 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 (876141167) \ N -- N -- N refs/changes/29/39929/1 (98b1e6a26) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39629/2 updated (18e73813f -> 8ba95aef4)

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/29/39629/2 in repository toolchain/jenkins-scripts. discards 18e73813f round-robin-bisect.sh: Switch to llvm(a)lists.linux.dev discards c55fbed24 tcwg-llvm-release.bat: Fix calculation of package name adds 8ba95aef4 tcwg-llvm-release.bat: Fix calculation of package name 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 (18e73813f) \ N -- N -- N refs/changes/29/39629/2 (8ba95aef4) 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 | 903 -------------------------------------------------- 1 file changed, 903 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39629/1 updated (6508100c1 -> 0d1fa1d41)

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/29/39629/1 in repository toolchain/jenkins-scripts. discards 6508100c1 round-robin-bisect.sh: Switch to llvm(a)lists.linux.dev discards ac5a51460 tcwg-llvm-release.bat: Fix copy to artifacts/ adds 0d1fa1d41 tcwg-llvm-release.bat: Fix copy to 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 (6508100c1) \ N -- N -- N refs/changes/29/39629/1 (0d1fa1d41) 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 | 903 -------------------------------------------------- 1 file changed, 903 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39129/5 updated (ab58f075e -> f88d5cbd6)

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/29/39129/5 in repository toolchain/jenkins-scripts. discards ab58f075e tcwg_gnu-build.sh: Bisect by running only testsuites with new [...] adds f88d5cbd6 tcwg_gnu-build.sh: Bisect by running only testsuites with 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 (ab58f075e) \ N -- N -- N refs/changes/29/39129/5 (f88d5cbd6) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39129/4 updated (4b7a18d46 -> 163b029e4)

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/29/39129/4 in repository toolchain/jenkins-scripts. discards 4b7a18d46 tcwg_gnu-build.sh: Bisect by running only testsuites with new [...] new 163b029e4 tcwg_gnu-build.sh: Bisect by running only testsuites with 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 (4b7a18d46) \ N -- N -- N refs/changes/29/39129/4 (163b029e4) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39129/3 updated (f7abe573a -> 0cf480fd6)

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/29/39129/3 in repository toolchain/jenkins-scripts. discards f7abe573a tcwg_gnu-build.sh: Bisect by running only testsuites with new [...] new 0cf480fd6 tcwg_gnu-build.sh: Bisect by running only testsuites with 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 (f7abe573a) \ N -- N -- N refs/changes/29/39129/3 (0cf480fd6) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/39129/2 updated (9925da9ba -> 8f1a31114)

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/29/39129/2 in repository toolchain/jenkins-scripts. discards 9925da9ba tcwg_gnu-build.sh: Bisect by running only testsuites with new [...] new 8f1a31114 tcwg_gnu-build.sh: Bisect by running only testsuites with 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 (9925da9ba) \ N -- N -- N refs/changes/29/39129/2 (8f1a31114) 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, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024