Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/38/41738/2 updated (f2f83ec74 -> 23997897b)

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/38/41738/2 in repository toolchain/jenkins-scripts. discards f2f83ec74 tcwg-report-stale-rr-jobs.sh: add no change in sources automa [...] new 23997897b tcwg-report-stale-rr-jobs.sh: add no change in sources automa [...] 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 (f2f83ec74) \ N -- N -- N refs/changes/38/41738/2 (23997897b) 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/38/41738/1 updated (d921cef5f -> b0fe36060)

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/38/41738/1 in repository toolchain/jenkins-scripts. discards d921cef5f tcwg-report-stale-rr-jobs.sh: add no change in sources automa [...] new b0fe36060 tcwg-report-stale-rr-jobs.sh: add no change in sources automa [...] 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 (d921cef5f) \ N -- N -- N refs/changes/38/41738/1 (b0fe36060) 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/38/39538/1 updated (627487ade -> c19473fed)

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/38/39538/1 in repository toolchain/jenkins-scripts. discards 627487ade round-robin-bisect.sh: Improve handling of uninteresting regressions discards 22c9d8219 round-robin-bisect.sh: Update component settings in special cases discards 6ba959831 round-robin.sh: Switch GDB CI loops back to using abe:tested adds c19473fed round-robin.sh: Switch GDB CI loops back to using abe:tested 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 (627487ade) \ N -- N -- N refs/changes/38/39538/1 (c19473fed) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/38/36238/3 updated (70b59f1a2 -> f7d5e8a56)

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/38/36238/3 in repository toolchain/jenkins-scripts. discards 70b59f1a2 tcwg-llvm-release: Deal with flang and mlir adds f7d5e8a56 tcwg-llvm-release: Deal with flang and mlir 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 (70b59f1a2) \ N -- N -- N refs/changes/38/36238/3 (f7d5e8a56) 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/38/36238/2 updated (49d6df4b8 -> b818e3307)

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/38/36238/2 in repository toolchain/jenkins-scripts. discards 49d6df4b8 tcwg-llvm-release: Deal with flang and mlir new b818e3307 tcwg-llvm-release: Deal with flang and mlir 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 (49d6df4b8) \ N -- N -- N refs/changes/38/36238/2 (b818e3307) 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/38/36238/1 updated (d4222615c -> 7a357fc30)

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/38/36238/1 in repository toolchain/jenkins-scripts. discards d4222615c tcwg-llvm-release: Deal with flang and mlir new 7a357fc30 tcwg-llvm-release: Deal with flang and mlir 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 (d4222615c) \ N -- N -- N refs/changes/38/36238/1 (7a357fc30) 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/38/32538/1 updated (9bcd0914f -> 2b443a1b9)

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/38/32538/1 in repository toolchain/jenkins-scripts. discards 9bcd0914f start-container-docker.sh: Remove most of ssh traces adds 2b443a1b9 start-container-docker.sh: Remove most of ssh traces 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 (9bcd0914f) \ N -- N -- N refs/changes/38/32538/1 (2b443a1b9) 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/38/32438/1 updated (60e683a28 -> 8f56be9d5)

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/38/32438/1 in repository toolchain/jenkins-scripts. discards 60e683a28 tcwg_gnu-build.sh: Improve no_regression_p() adds 8f56be9d5 tcwg_gnu-build.sh: Improve no_regression_p() 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 (60e683a28) \ N -- N -- N refs/changes/38/32438/1 (8f56be9d5) 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/38/32338/2 updated (0eae4c421 -> 43efc6062)

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/38/32338/2 in repository toolchain/jenkins-scripts. discards 0eae4c421 jenkins-helpers.sh: Add entries for tcwg-amp-* machines adds 43efc6062 jenkins-helpers.sh: Add entries for tcwg-amp-* machines 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 (0eae4c421) \ N -- N -- N refs/changes/38/32338/2 (43efc6062) 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/38/32338/1 updated (f75d5f9f7 -> e1ba66909)

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/38/32338/1 in repository toolchain/jenkins-scripts. discards f75d5f9f7 jenkins-helpers.sh: Add entries for tcwg-amp-* machines new e1ba66909 jenkins-helpers.sh: Add entries for tcwg-amp-* machines 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 (f75d5f9f7) \ N -- N -- N refs/changes/38/32338/1 (e1ba66909) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024