Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/99/30099/1 updated (79cadc41a -> f27a53e5a)

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/99/30099/1 in repository toolchain/jenkins-scripts. discards 79cadc41a tcwg_bmk-build: Skip results with "n/a" adds f27a53e5a tcwg_bmk-build: Skip results with "n/a" 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 (79cadc41a) \ N -- N -- N refs/changes/99/30099/1 (f27a53e5a) 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/99/29999/1 updated (70d5cf11c -> 30f796fc6)

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/99/29999/1 in repository toolchain/jenkins-scripts. discards 70d5cf11c tcwg_bmk-build: Skip header line when parsing results new 30f796fc6 tcwg_bmk-build: Skip header line when parsing 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 (70d5cf11c) \ N -- N -- N refs/changes/99/29999/1 (30f796fc6) 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/98/47298/1 updated (effb57ad8 -> 911a58512)

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/98/47298/1 in repository toolchain/jenkins-scripts. discards effb57ad8 tcwg-update-llvmbot-containers: Move Arm lldb bot to silent adds 911a58512 tcwg-update-llvmbot-containers: Move Arm lldb bot to silent 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 (effb57ad8) \ N -- N -- N refs/changes/98/47298/1 (911a58512) 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/98/46998/1 updated (4c89fdc88 -> 86f4b2d75)

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/98/46998/1 in repository toolchain/jenkins-scripts. discards 4c89fdc88 round-robin-notify.sh,lnt-utils.sh: Graph the difference for [...] adds 86f4b2d75 round-robin-notify.sh,lnt-utils.sh: Graph the difference for [...] 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 (4c89fdc88) \ N -- N -- N refs/changes/98/46998/1 (86f4b2d75) 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/98/46898/1 updated (79aa3d875 -> 5aec02679)

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/98/46898/1 in repository toolchain/jenkins-scripts. discards 79aa3d875 update_deps.sh: Handle update_only parameter adds 5aec02679 update_deps.sh: Handle update_only parameter 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 (79aa3d875) \ N -- N -- N refs/changes/98/46898/1 (5aec02679) 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/98/45898/1 updated (fe8b77cd8 -> 26b33830a)

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/98/45898/1 in repository toolchain/jenkins-scripts. discards fe8b77cd8 lnt-utils.sh: do not generate empty lnt reports adds 26b33830a lnt-utils.sh: do not generate empty lnt reports 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 (fe8b77cd8) \ N -- N -- N refs/changes/98/45898/1 (26b33830a) 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/98/45598/3 updated (937166563 -> eb845b53f)

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/98/45598/3 in repository toolchain/jenkins-scripts. discards 937166563 tcwg_gnu-build.sh: Test history rewrite logic on all GNU conf [...] adds eb845b53f tcwg_gnu-build.sh: Test history rewrite logic on all GNU conf [...] 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 (937166563) \ N -- N -- N refs/changes/98/45598/3 (eb845b53f) 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/98/45598/2 updated (2921a38dc -> ad194f258)

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/98/45598/2 in repository toolchain/jenkins-scripts. discards 2921a38dc tcwg_gnu-build.sh: Test history rewrite logic on all GNU conf [...] new ad194f258 tcwg_gnu-build.sh: Test history rewrite logic on all GNU conf [...] 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 (2921a38dc) \ N -- N -- N refs/changes/98/45598/2 (ad194f258) 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/98/45598/1 updated (9f7bccc75 -> 7138f286f)

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/98/45598/1 in repository toolchain/jenkins-scripts. discards 9f7bccc75 tcwg_gnu-build.sh: Test history rewrite logic on all GNU conf [...] new 7138f286f tcwg_gnu-build.sh: Test history rewrite logic on all GNU conf [...] 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 (9f7bccc75) \ N -- N -- N refs/changes/98/45598/1 (7138f286f) 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/98/44298/1 updated (2ae113393 -> 686b3d4e5)

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/98/44298/1 in repository toolchain/jenkins-scripts. discards 2ae113393 tcwg_gnu-build.sh: Fix tcwg_glibc_* configurations adds 686b3d4e5 tcwg_gnu-build.sh: Fix tcwg_glibc_* configurations 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 (2ae113393) \ N -- N -- N refs/changes/98/44298/1 (686b3d4e5) 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