Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/22/39922/1 updated (0d3d7a021 -> f35376e7d)

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/22/39922/1 in repository toolchain/jenkins-scripts. discards 0d3d7a021 start-container-docker.sh: Add workaround for armhf focal con [...] new f35376e7d start-container-docker.sh: Add workaround for armhf focal con [...] 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 (0d3d7a021) \ N -- N -- N refs/changes/22/39922/1 (f35376e7d) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/39722/1 updated (1af2c6048 -> 5d0f2b410)

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/22/39722/1 in repository toolchain/jenkins-scripts. discards 1af2c6048 tcwg_bmk-build.sh: Add absolute numbers for regressions to em [...] adds 5d0f2b410 tcwg_bmk-build.sh: Add absolute numbers for regressions to em [...] 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 (1af2c6048) \ N -- N -- N refs/changes/22/39722/1 (5d0f2b410) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/39622/2 updated (ac5a51460 -> 0d1fa1d41)

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/22/39622/2 in repository toolchain/jenkins-scripts. discards ac5a51460 tcwg-llvm-release.bat: Fix copy to artifacts/ adds 0d1fa1d41 tcwg-llvm-release.bat: Fix copy to artifacts/ 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 (ac5a51460) \ N -- N -- N refs/changes/22/39622/2 (0d1fa1d41) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/39622/1 updated (c8fba4f50 -> 1528e6027)

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/22/39622/1 in repository toolchain/jenkins-scripts. discards c8fba4f50 tcwg-llvm-release.bat: Fix copy to artifacts/ new 1528e6027 tcwg-llvm-release.bat: Fix copy to artifacts/ 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 (c8fba4f50) \ N -- N -- N refs/changes/22/39622/1 (1528e6027) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/39222/1 updated (cef6a0dfb -> 1168b7134)

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/22/39222/1 in repository toolchain/jenkins-scripts. discards cef6a0dfb jenkins-helpers.sh: Update only requested remote adds 1168b7134 jenkins-helpers.sh: Update only requested remote 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 (cef6a0dfb) \ N -- N -- N refs/changes/22/39222/1 (1168b7134) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/36022/2 updated (845cfd043 -> ef2c41de1)

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/22/36022/2 in repository toolchain/jenkins-scripts. discards 845cfd043 MakeRelease.job: Fix use of port 22 to upload binary tarballs [...] adds ef2c41de1 MakeRelease.job: Fix use of port 22 to upload binary tarballs [...] 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 (845cfd043) \ N -- N -- N refs/changes/22/36022/2 (ef2c41de1) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/36022/1 updated (2bc57bc5f -> 7a36fe318)

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/22/36022/1 in repository toolchain/jenkins-scripts. discards 2bc57bc5f MakeRelease.job: Fix use of port 22 to upload binary tarballs [...] new 7a36fe318 MakeRelease.job: Fix use of port 22 to upload binary tarballs [...] 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 (2bc57bc5f) \ N -- N -- N refs/changes/22/36022/1 (7a36fe318) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/35422/2 updated (db1c5bf29 -> 80c1ae3ca)

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/22/35422/2 in repository toolchain/jenkins-scripts. discards db1c5bf29 tcwg_bmk-build.sh: Add compatibility with older baseline results adds 80c1ae3ca tcwg_bmk-build.sh: Add compatibility with older baseline 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 (db1c5bf29) \ N -- N -- N refs/changes/22/35422/2 (80c1ae3ca) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/35422/1 updated (28efff9ad -> e25ab9143)

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/22/35422/1 in repository toolchain/jenkins-scripts. discards 28efff9ad tcwg_bmk-build.sh: Add compatibility with older baseline results new e25ab9143 tcwg_bmk-build.sh: Add compatibility with older baseline 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 (28efff9ad) \ N -- N -- N refs/changes/22/35422/1 (e25ab9143) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/22/34522/1 updated (170d72fbc -> 10d67bcf2)

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/22/34522/1 in repository toolchain/jenkins-scripts. discards 170d72fbc tcwg_gnu-build.sh: Fix URL for GCC repo adds 10d67bcf2 tcwg_gnu-build.sh: Fix URL for GCC repo 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 (170d72fbc) \ N -- N -- N refs/changes/22/34522/1 (10d67bcf2) 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, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024