Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/12/44712/2 updated (c0de5afed -> 56fe41d14)

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/12/44712/2 in repository toolchain/jenkins-scripts. discards c0de5afed tcwg_bmk-build.sh: Fix place where to store the bmk results new 56fe41d14 tcwg_bmk-build.sh: Fix place where to store the bmk 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 (c0de5afed) \ N -- N -- N refs/changes/12/44712/2 (56fe41d14) 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/12/44712/1 updated (5153fa0d8 -> 70b3d0549)

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/12/44712/1 in repository toolchain/jenkins-scripts. discards 5153fa0d8 tcwg_bmk-build.sh: Fix place where to store the bmk results new 70b3d0549 tcwg_bmk-build.sh: Fix place where to store the bmk 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 (5153fa0d8) \ N -- N -- N refs/changes/12/44712/1 (70b3d0549) 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/12/44512/2 updated (c76999db4 -> 827f0bcba)

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/12/44512/2 in repository toolchain/jenkins-scripts. discards c76999db4 pw-report.sh: Remove workaround for glibc testsuite testing adds 827f0bcba pw-report.sh: Remove workaround for glibc testsuite testing 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 (c76999db4) \ N -- N -- N refs/changes/12/44512/2 (827f0bcba) 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/12/44512/1 updated (89014036e -> f3e957102)

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/12/44512/1 in repository toolchain/jenkins-scripts. discards 89014036e pw-report.sh: Remove workaround for glibc testsuite testing new f3e957102 pw-report.sh: Remove workaround for glibc testsuite testing 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 (89014036e) \ N -- N -- N refs/changes/12/44512/1 (f3e957102) 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/12/44212/3 updated (104000423 -> f314e5045)

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/12/44212/3 in repository toolchain/jenkins-scripts. discards 104000423 tcwg_*-build.sh: remove rr[start_date], as it is now useless adds f314e5045 tcwg_*-build.sh: remove rr[start_date], as it is now useless 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 (104000423) \ N -- N -- N refs/changes/12/44212/3 (f314e5045) 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/12/44212/2 updated (99665f3cd -> 3507b2119)

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/12/44212/2 in repository toolchain/jenkins-scripts. discards 99665f3cd tcwg_*-build.sh: remove rr[start_date], as it is now useless new 3507b2119 tcwg_*-build.sh: remove rr[start_date], as it is now useless 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 (99665f3cd) \ N -- N -- N refs/changes/12/44212/2 (3507b2119) 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/12/44212/1 updated (a930c7639 -> 6aa501078)

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/12/44212/1 in repository toolchain/jenkins-scripts. discards a930c7639 tcwg_*-build.sh: remove rr[start_date], as it is now useless new 6aa501078 tcwg_*-build.sh: remove rr[start_date], as it is now useless 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 (a930c7639) \ N -- N -- N refs/changes/12/44212/1 (6aa501078) 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/12/44112/1 updated (f0046ade3 -> bd61eb059)

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/12/44112/1 in repository toolchain/jenkins-scripts. discards f0046ade3 round-robin-notify.sh: First version with unitary requests discards 7dcd237be round-robin.sh: Add results_date to manifest.sh new bd61eb059 round-robin.sh: Add results_date to manifest.sh 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 (f0046ade3) \ N -- N -- N refs/changes/12/44112/1 (bd61eb059) 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: round-robin-bisect.sh | 627 ------------------------- round-robin-notify.sh | 1254 ------------------------------------------------- 2 files changed, 1881 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- 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/12/41812/2 updated (27ec3d01e -> c32f45b5a)

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/12/41812/2 in repository toolchain/jenkins-scripts. discards 27ec3d01e round-robin.sh: Rework handling of base-artifacts history adds c32f45b5a round-robin.sh: Rework handling of base-artifacts history 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 (27ec3d01e) \ N -- N -- N refs/changes/12/41812/2 (c32f45b5a) 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/12/41812/1 updated (713e59797 -> 89d4188dc)

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/12/41812/1 in repository toolchain/jenkins-scripts. discards 713e59797 round-robin.sh: Rework handling of base-artifacts history new 89d4188dc round-robin.sh: Rework handling of base-artifacts history 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 (713e59797) \ N -- N -- N refs/changes/12/41812/1 (89d4188dc) 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024