Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/04/43404/3 updated (dfa563636 -> 813c18e66)

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/04/43404/3 in repository toolchain/jenkins-scripts. discards dfa563636 tcwg_gnu-build.sh: Rerun failed tests on GDB check jobs new 813c18e66 tcwg_gnu-build.sh: Rerun failed tests on GDB check jobs 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 (dfa563636) \ N -- N -- N refs/changes/04/43404/3 (813c18e66) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/43404/2 updated (fe9658af1 -> f3219e725)

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/04/43404/2 in repository toolchain/jenkins-scripts. discards fe9658af1 tcwg_gnu-build.sh: Rerun failed tests on check GDB jobs new f3219e725 tcwg_gnu-build.sh: Rerun failed tests on check GDB jobs 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 (fe9658af1) \ N -- N -- N refs/changes/04/43404/2 (f3219e725) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/43404/1 updated (14c85184a -> 93c272ca3)

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/04/43404/1 in repository toolchain/jenkins-scripts. discards 14c85184a tcwg_gnu-build.sh: Rerun failed tests on check GDB jobs new 93c272ca3 tcwg_gnu-build.sh: Rerun failed tests on check GDB jobs 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 (14c85184a) \ N -- N -- N refs/changes/04/43404/1 (93c272ca3) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/41004/1 updated (0e9242aa1 -> e6b9fbf92)

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/04/41004/1 in repository toolchain/jenkins-scripts. discards 0e9242aa1 tcwg-update-llvmbot-containers.sh: Have tk1-03 pretend to be tk1-02 adds e6b9fbf92 tcwg-update-llvmbot-containers.sh: Have tk1-03 pretend to be tk1-02 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 (0e9242aa1) \ N -- N -- N refs/changes/04/41004/1 (e6b9fbf92) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/39304/3 updated (acc642521 -> ec4328979)

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/04/39304/3 in repository toolchain/jenkins-scripts. discards acc642521 tcwg-benchmark.sh: Swap toolchain preparation and board preparation adds ec4328979 tcwg-benchmark.sh: Swap toolchain preparation and board preparation 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 (acc642521) \ N -- N -- N refs/changes/04/39304/3 (ec4328979) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/39304/2 updated (538f01839 -> 813aad87d)

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/04/39304/2 in repository toolchain/jenkins-scripts. discards 538f01839 tcwg-benchmark.sh: Swap toolchain preparation and board preparation adds 813aad87d tcwg-benchmark.sh: Swap toolchain preparation and board preparation 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 (538f01839) \ N -- N -- N refs/changes/04/39304/2 (813aad87d) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/39304/1 updated (1c590080b -> 19bdb7afe)

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/04/39304/1 in repository toolchain/jenkins-scripts. discards 1c590080b tcwg-benchmark.sh: Swap toolchain preparation and board preparation adds 19bdb7afe tcwg-benchmark.sh: Swap toolchain preparation and board preparation 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 (1c590080b) \ N -- N -- N refs/changes/04/39304/1 (19bdb7afe) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/39204/2 updated (e2e53d0a2 -> ccf5fe35e)

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/04/39204/2 in repository toolchain/jenkins-scripts. discards e2e53d0a2 jenkins-helpers.sh (git_init_linaro_local_remote): Add specia [...] adds ccf5fe35e jenkins-helpers.sh (git_init_linaro_local_remote): Add specia [...] 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 (e2e53d0a2) \ N -- N -- N refs/changes/04/39204/2 (ccf5fe35e) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/39204/1 updated (459d12eb7 -> 39bfe09bc)

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/04/39204/1 in repository toolchain/jenkins-scripts. discards 459d12eb7 jenkins-helpers.sh (git_init_linaro_local_remote): Add specia [...] new 39bfe09bc jenkins-helpers.sh (git_init_linaro_local_remote): Add specia [...] 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 (459d12eb7) \ N -- N -- N refs/changes/04/39204/1 (39bfe09bc) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/04/37404/1 updated (36aa35cac -> e1b7cb695)

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/04/37404/1 in repository toolchain/jenkins-scripts. discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...] discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...] discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE 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 (36aa35cac) \ N -- N -- N refs/changes/04/37404/1 (e1b7cb695) 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 | 683 -------------------------------------------------- 1 file changed, 683 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024