Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/51/42151/1 updated (71b034a71 -> 910e5f52c)

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/51/42151/1 in repository toolchain/jenkins-scripts. discards 71b034a71 tcwg-report-stale-rr-jobs.sh: Add day per component, output file new 910e5f52c tcwg-report-stale-rr-jobs.sh: Add day per component, output file 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 (71b034a71) \ N -- N -- N refs/changes/51/42151/1 (910e5f52c) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/42051/1 updated (e20e5a5fc -> d8389d726)

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/51/42051/1 in repository toolchain/jenkins-scripts. discards e20e5a5fc round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...] adds d8389d726 round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...] 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 (e20e5a5fc) \ N -- N -- N refs/changes/51/42051/1 (d8389d726) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41851/1 updated (59018635e -> 20424373e)

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/51/41851/1 in repository toolchain/jenkins-scripts. discards 59018635e round-robin.sh: Rename base-artifacts/baseline to base-artifacts/git adds 20424373e round-robin.sh: Rename base-artifacts/baseline to base-artifacts/git 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 (59018635e) \ N -- N -- N refs/changes/51/41851/1 (20424373e) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41351/3 updated (5332ae28c -> 5e61789c4)

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/51/41351/3 in repository toolchain/jenkins-scripts. discards 5332ae28c tcwg-start-container.sh: Move logic to test and recover docke [...] adds 5e61789c4 tcwg-start-container.sh: Move logic to test and recover docke [...] 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 (5332ae28c) \ N -- N -- N refs/changes/51/41351/3 (5e61789c4) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41351/2 updated (d4acdeb77 -> 3b869789d)

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/51/41351/2 in repository toolchain/jenkins-scripts. discards d4acdeb77 tcwg-start-container.sh: Move logic to test and recover docke [...] adds 3b869789d tcwg-start-container.sh: Move logic to test and recover docke [...] 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 (d4acdeb77) \ N -- N -- N refs/changes/51/41351/2 (3b869789d) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41351/1 updated (a8c317051 -> c1d6f5af0)

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/51/41351/1 in repository toolchain/jenkins-scripts. discards a8c317051 tcwg-start-container.sh: Move logic to test and recover docke [...] adds c1d6f5af0 tcwg-start-container.sh: Move logic to test and recover docke [...] 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 (a8c317051) \ N -- N -- N refs/changes/51/41351/1 (c1d6f5af0) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41251/2 updated (0f0375615 -> 7eb33b18a)

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/51/41251/2 in repository toolchain/jenkins-scripts. discards 0f0375615 Revert "tcwg-benchmark.sh: Enable bmk host for tk1 and tx1" adds 7eb33b18a Revert "tcwg-benchmark.sh: Enable bmk host for tk1 and tx1" 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 (0f0375615) \ N -- N -- N refs/changes/51/41251/2 (7eb33b18a) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41251/1 updated (7fd68df73 -> f081d63fc)

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/51/41251/1 in repository toolchain/jenkins-scripts. discards 7fd68df73 Revert "tcwg-benchmark.sh: Enable bmk host for tk1 and tx1" new f081d63fc Revert "tcwg-benchmark.sh: Enable bmk host for tk1 and tx1" 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 (7fd68df73) \ N -- N -- N refs/changes/51/41251/1 (f081d63fc) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/41051/1 updated (a56a601cd -> b657ffc4d)

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/51/41051/1 in repository toolchain/jenkins-scripts. discards a56a601cd tcwg-benchmark: Use host container for fx and apm new b657ffc4d tcwg-benchmark: Use host container for fx and apm 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 (a56a601cd) \ N -- N -- N refs/changes/51/41051/1 (b657ffc4d) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/51/39251/2 updated (37e69ce38 -> f049fa7c0)

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/51/39251/2 in repository toolchain/jenkins-scripts. discards 37e69ce38 round-robin-bisect.sh: Handle flaky tests for more check_* ci [...] discards 176aed6ba round-robin-bisect.sh: Update formatting discards 742f2a623 tcwg_gnu-build.sh: Update after adding binutils to bootstrap configs adds f049fa7c0 tcwg_gnu-build.sh: Update after adding binutils to bootstrap configs 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 (37e69ce38) \ N -- N -- N refs/changes/51/39251/2 (f049fa7c0) 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 | 823 -------------------------------------------------- 1 file changed, 823 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, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024