Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/76/41876/7 updated (2104b9f52 -> a1f40149e)

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/76/41876/7 in repository toolchain/jenkins-scripts. discards 2104b9f52 tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] adds a1f40149e tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] 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 (2104b9f52) \ N -- N -- N refs/changes/76/41876/7 (a1f40149e) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41876/6 updated (21475ddd3 -> 240f0901d)

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/76/41876/6 in repository toolchain/jenkins-scripts. discards 21475ddd3 tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] new 240f0901d tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] 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 (21475ddd3) \ N -- N -- N refs/changes/76/41876/6 (240f0901d) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41876/5 updated (2755ff06c -> a53ea9403)

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/76/41876/5 in repository toolchain/jenkins-scripts. discards 2755ff06c tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] new a53ea9403 tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] 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 (2755ff06c) \ N -- N -- N refs/changes/76/41876/5 (a53ea9403) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41876/4 updated (8a90226b6 -> f1b8f00d6)

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/76/41876/4 in repository toolchain/jenkins-scripts. discards 8a90226b6 tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] new f1b8f00d6 tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] 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 (8a90226b6) \ N -- N -- N refs/changes/76/41876/4 (f1b8f00d6) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41876/3 updated (a7e5a2a0a -> 79dc8b5e8)

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/76/41876/3 in repository toolchain/jenkins-scripts. discards a7e5a2a0a tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] new 79dc8b5e8 tcwg-report-stale-rr-jobs.sh: use manifest to detect unupdate [...] 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 (a7e5a2a0a) \ N -- N -- N refs/changes/76/41876/3 (79dc8b5e8) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41876/2 updated (1e07f1676 -> c47cc51b6)

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/76/41876/2 in repository toolchain/jenkins-scripts. discards 1e07f1676 tcwg-report-stale-rr-jobs.sh: use git/*_rev to detect unupdat [...] new c47cc51b6 tcwg-report-stale-rr-jobs.sh: use git/*_rev to detect unupdat [...] 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 (1e07f1676) \ N -- N -- N refs/changes/76/41876/2 (c47cc51b6) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41876/1 updated (2f0dfa78f -> d712ccdc5)

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/76/41876/1 in repository toolchain/jenkins-scripts. discards 2f0dfa78f tcwg-report-stale-rr-jobs.sh: use git/*_rev to detect unupdat [...] new d712ccdc5 tcwg-report-stale-rr-jobs.sh: use git/*_rev to detect unupdat [...] 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 (2f0dfa78f) \ N -- N -- N refs/changes/76/41876/1 (d712ccdc5) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41676/2 updated (d63699b7a -> 928e990b1)

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/76/41676/2 in repository toolchain/jenkins-scripts. discards d63699b7a tcwg-llvm-release.sh: Force lit to 16 jobs on aarch64 adds 928e990b1 tcwg-llvm-release.sh: Force lit to 16 jobs on aarch64 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 (d63699b7a) \ N -- N -- N refs/changes/76/41676/2 (928e990b1) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/41676/1 updated (4e77c0b1b -> 9b1a6212e)

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/76/41676/1 in repository toolchain/jenkins-scripts. discards 4e77c0b1b tcwg-llvm-release.sh: Force lit to 16 jobs on aarch64 adds 9b1a6212e tcwg-llvm-release.sh: Force lit to 16 jobs on aarch64 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 (4e77c0b1b) \ N -- N -- N refs/changes/76/41676/1 (9b1a6212e) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/76/39576/1 updated (26d59817f -> 1e4a1e59f)

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/76/39576/1 in repository toolchain/jenkins-scripts. discards 26d59817f tcwg_gnu-build.sh: Handle failures to parse results adds 1e4a1e59f tcwg_gnu-build.sh: Handle failures to parse results 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 (26d59817f) \ N -- N -- N refs/changes/76/39576/1 (1e4a1e59f) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024