Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/67/43167/1 updated (5a3d4948a -> 508659446)

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/67/43167/1 in repository toolchain/jenkins-scripts. discards 5a3d4948a Switch default distro from Ubuntu 20.04 Focal to Ubuntu 22.04 Jammy adds 508659446 Switch default distro from Ubuntu 20.04 Focal to Ubuntu 22.04 Jammy 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 (5a3d4948a) \ N -- N -- N refs/changes/67/43167/1 (508659446) 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/67/42267/2 updated (229670b3e -> 2d8df9da4)

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/67/42267/2 in repository toolchain/jenkins-scripts. discards 229670b3e round-robin.sh,tcwg_bmk-build.sh: Can build llvm for flang adds 2d8df9da4 round-robin.sh,tcwg_bmk-build.sh: Can build llvm for flang 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 (229670b3e) \ N -- N -- N refs/changes/67/42267/2 (2d8df9da4) 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/67/42267/1 updated (060f00c4f -> af4d2ec81)

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/67/42267/1 in repository toolchain/jenkins-scripts. discards 060f00c4f round-robin.sh,tcwg_bmk-build.sh: Can build llvm for flang new af4d2ec81 round-robin.sh,tcwg_bmk-build.sh: Can build llvm for flang 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 (060f00c4f) \ N -- N -- N refs/changes/67/42267/1 (af4d2ec81) 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/67/42167/2 updated (0fbbe2bf1 -> 0ea5be86c)

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/67/42167/2 in repository toolchain/jenkins-scripts. discards 0fbbe2bf1 tcwg-report-stale-rr-jobs.sh: Use a reference-if-able for bas [...] adds 0ea5be86c tcwg-report-stale-rr-jobs.sh: Use a reference-if-able for bas [...] 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 (0fbbe2bf1) \ N -- N -- N refs/changes/67/42167/2 (0ea5be86c) 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/67/42167/1 updated (0a760fbe3 -> d2db04e8f)

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/67/42167/1 in repository toolchain/jenkins-scripts. discards 0a760fbe3 tcwg-report-stale-rr-jobs.sh: Use a reference-if-able for bas [...] new d2db04e8f tcwg-report-stale-rr-jobs.sh: Use a reference-if-able for bas [...] 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 (0a760fbe3) \ N -- N -- N refs/changes/67/42167/1 (d2db04e8f) 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/67/42067/1 updated (fc543972b -> 76364a696)

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/67/42067/1 in repository toolchain/jenkins-scripts. discards fc543972b round-robin.sh: update_baseline=ignore uses base-artifact emp [...] adds 76364a696 round-robin.sh: update_baseline=ignore uses base-artifact emp [...] 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 (fc543972b) \ N -- N -- N refs/changes/67/42067/1 (76364a696) 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/67/41967/2 updated (62d9f122c -> 0dfaba932)

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/67/41967/2 in repository toolchain/jenkins-scripts. discards 62d9f122c dashboard-generate-squad.sh: handle empty SQUAD_GRP adds 0dfaba932 dashboard-generate-squad.sh: handle empty SQUAD_GRP 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 (62d9f122c) \ N -- N -- N refs/changes/67/41967/2 (0dfaba932) 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/67/41967/1 updated (4dd7ba4e0 -> 7e295eda4)

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/67/41967/1 in repository toolchain/jenkins-scripts. discards 4dd7ba4e0 dashboard-generate-squad.sh: handle empty SQUAD_GRP new 7e295eda4 dashboard-generate-squad.sh: handle empty SQUAD_GRP 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 (4dd7ba4e0) \ N -- N -- N refs/changes/67/41967/1 (7e295eda4) 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/67/41367/1 updated (03b40f85c -> 8a6f2d1d0)

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/67/41367/1 in repository toolchain/jenkins-scripts. discards 03b40f85c tcwg_bmk-build.sh: Parse jenkins console logs to detect failure mode adds 8a6f2d1d0 tcwg_bmk-build.sh: Parse jenkins console logs to detect failure mode 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 (03b40f85c) \ N -- N -- N refs/changes/67/41367/1 (8a6f2d1d0) 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/67/40167/2 updated (e34fdfc3b -> 19b3dac66)

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/67/40167/2 in repository toolchain/jenkins-scripts. discards e34fdfc3b tcwg-llvmbots: Move armv7 worker tk1-08 to silent buildmaster adds 19b3dac66 tcwg-llvmbots: Move armv7 worker tk1-08 to silent buildmaster 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 (e34fdfc3b) \ N -- N -- N refs/changes/67/40167/2 (19b3dac66) 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