Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/01/44601/2 updated (5f6b078f6 -> 810278793)

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/01/44601/2 in repository toolchain/jenkins-scripts. discards 5f6b078f6 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation adds 810278793 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation 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 (5f6b078f6) \ N -- N -- N refs/changes/01/44601/2 (810278793) 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

[toolchain/jenkins-scripts] reference refs/changes/01/44601/1 updated (75f4bc123 -> dfe890b01)

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/01/44601/1 in repository toolchain/jenkins-scripts. discards 75f4bc123 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation new dfe890b01 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation 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 (75f4bc123) \ N -- N -- N refs/changes/01/44601/1 (dfe890b01) 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

[toolchain/jenkins-scripts] reference refs/changes/01/44501/1 updated (26127f212 -> 45b953330)

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/01/44501/1 in repository toolchain/jenkins-scripts. discards 26127f212 round-robin.sh,tcwg-benchmark-results.sh: Store results-xxx a [...] new 45b953330 round-robin.sh,tcwg-benchmark-results.sh: Store results-xxx 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 (26127f212) \ N -- N -- N refs/changes/01/44501/1 (45b953330) 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

[toolchain/jenkins-scripts] reference refs/changes/01/43501/3 updated (6b1c1c8ff -> b13f96e67)

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/01/43501/3 in repository toolchain/jenkins-scripts. discards 6b1c1c8ff tcwg_bmk-build.sh: Compute and use automatic threshold for ea [...] adds b13f96e67 tcwg_bmk-build.sh: Compute and use automatic threshold for ea [...] 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 (6b1c1c8ff) \ N -- N -- N refs/changes/01/43501/3 (b13f96e67) 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

[toolchain/jenkins-scripts] reference refs/changes/01/43501/2 updated (147b7d612 -> 772449c87)

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/01/43501/2 in repository toolchain/jenkins-scripts. discards 147b7d612 tcwg_bmk-build.sh: Compute and use automatic threshold for ea [...] new 772449c87 tcwg_bmk-build.sh: Compute and use automatic threshold for ea [...] 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 (147b7d612) \ N -- N -- N refs/changes/01/43501/2 (772449c87) 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

[toolchain/jenkins-scripts] reference refs/changes/01/43501/1 updated (2572439b0 -> d74ce66ed)

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/01/43501/1 in repository toolchain/jenkins-scripts. discards 2572439b0 tcwg_bmk-build.sh: Compute and use automatic threshold for ea [...] new d74ce66ed tcwg_bmk-build.sh: Compute and use automatic threshold for ea [...] 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 (2572439b0) \ N -- N -- N refs/changes/01/43501/1 (d74ce66ed) 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

[toolchain/jenkins-scripts] reference refs/changes/01/42401/1 updated (409b675e1 -> ce0abde64)

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/01/42401/1 in repository toolchain/jenkins-scripts. discards 409b675e1 tcwg-benchmark.sh: support-fortran option if flang is found adds ce0abde64 tcwg-benchmark.sh: support-fortran option if flang is found 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 (409b675e1) \ N -- N -- N refs/changes/01/42401/1 (ce0abde64) 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

[toolchain/jenkins-scripts] reference refs/changes/01/42101/1 updated (f9f90c803 -> 5d3d158cf)

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/01/42101/1 in repository toolchain/jenkins-scripts. discards f9f90c803 round-robin.sh: Add support for jobs that run fast checks new 5d3d158cf round-robin.sh: Add support for jobs that run fast checks 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 (f9f90c803) \ N -- N -- N refs/changes/01/42101/1 (5d3d158cf) 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

[toolchain/jenkins-scripts] reference refs/changes/01/39701/1 updated (6cc316eb9 -> 751d0f6ba)

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/01/39701/1 in repository toolchain/jenkins-scripts. discards 6cc316eb9 tcwg_bmk-build.sh: Minor fixups adds 751d0f6ba tcwg_bmk-build.sh: Minor fixups 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 (6cc316eb9) \ N -- N -- N refs/changes/01/39701/1 (751d0f6ba) 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

[toolchain/jenkins-scripts] reference refs/changes/01/39601/1 updated (4dccc6330 -> 105e2e62d)

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/01/39601/1 in repository toolchain/jenkins-scripts. discards 4dccc6330 tcwg-llvm-release.bat: New script adds 105e2e62d tcwg-llvm-release.bat: New script 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 (4dccc6330) \ N -- N -- N refs/changes/01/39601/1 (105e2e62d) 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024