Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/91/46191/1 updated (06b1f60d8 -> 4f17b17fc)

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/91/46191/1 in repository toolchain/jenkins-scripts. discards 06b1f60d8 tcwg-lnt/create-server.sh: Fix schemas in lnt server adds 4f17b17fc tcwg-lnt/create-server.sh: Fix schemas in lnt server 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 (06b1f60d8) \ N -- N -- N refs/changes/91/46191/1 (4f17b17fc) 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/91/46091/1 updated (c5e448bd7 -> b9194e230)

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/91/46091/1 in repository toolchain/jenkins-scripts. discards c5e448bd7 round-robin-notify.sh (print_jira_template_card): Remove outd [...] discards 82a54ab83 tcwg_gnu-build.sh: Workaround rewrite artifact adds b9194e230 tcwg_gnu-build.sh: Workaround rewrite artifact 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 (c5e448bd7) \ N -- N -- N refs/changes/91/46091/1 (b9194e230) 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: round-robin-baseline.sh | 567 -------------- round-robin-bisect.sh | 681 ----------------- round-robin-notify.sh | 1947 ----------------------------------------------- 3 files changed, 3195 deletions(-) delete mode 100755 round-robin-baseline.sh 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/45591/4 updated (667d2a7cc -> eeb8e5335)

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/91/45591/4 in repository toolchain/jenkins-scripts. discards 667d2a7cc tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data adds eeb8e5335 tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data 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 (667d2a7cc) \ N -- N -- N refs/changes/91/45591/4 (eeb8e5335) 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/91/45591/3 updated (6ec7f6af7 -> 47d6e121e)

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/91/45591/3 in repository toolchain/jenkins-scripts. discards 6ec7f6af7 tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data new 47d6e121e tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data 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 (6ec7f6af7) \ N -- N -- N refs/changes/91/45591/3 (47d6e121e) 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/91/45591/2 updated (9fa25b653 -> a27b65f1b)

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/91/45591/2 in repository toolchain/jenkins-scripts. discards 9fa25b653 tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data new a27b65f1b tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data 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 (9fa25b653) \ N -- N -- N refs/changes/91/45591/2 (a27b65f1b) 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/91/45591/1 updated (2d34ae437 -> 513ab7013)

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/91/45591/1 in repository toolchain/jenkins-scripts. discards 2d34ae437 tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data new 513ab7013 tcwg_bmk-build.sh: Rework handling of base-artifacts/annex/bmk-data 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 (2d34ae437) \ N -- N -- N refs/changes/91/45591/1 (513ab7013) 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/91/44791/1 updated (43770a786 -> e0f627637)

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/91/44791/1 in repository toolchain/jenkins-scripts. discards 43770a786 tcwg_bmk-build.sh: Add clear assert if the bmk results cannot [...] adds e0f627637 tcwg_bmk-build.sh: Add clear assert if the bmk results cannot [...] 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 (43770a786) \ N -- N -- N refs/changes/91/44791/1 (e0f627637) 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/91/44491/4 updated (8aab251e3 -> 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/91/44491/4 in repository toolchain/jenkins-scripts. discards 8aab251e3 round-robin-notify.sh: Remove unnecessary info from jira reports discards d1e427d6b round-robin-notify.sh: Simplify single_commit_p() and add a s [...] 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 (8aab251e3) \ N -- N -- N refs/changes/91/44491/4 (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: round-robin-bisect.sh | 647 ------------------------- round-robin-notify.sh | 1255 ------------------------------------------------- 2 files changed, 1902 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/44491/3 updated (899e9d950 -> bb1cb1b7f)

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/91/44491/3 in repository toolchain/jenkins-scripts. discards 899e9d950 round-robin-notify.sh: Remove unnecessary info from jira reports discards 6b5066d1c round-robin-notify.sh: Simplify single_commit_p() and add a s [...] discards 21fc0e4f2 round-robin.sh (build_abe): Fix disabling of fortran for *emb [...] adds bb1cb1b7f round-robin.sh (build_abe): Fix disabling of fortran for *emb [...] 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 (899e9d950) \ N -- N -- N refs/changes/91/44491/3 (bb1cb1b7f) 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: round-robin-bisect.sh | 647 ------------------------- round-robin-notify.sh | 1256 ------------------------------------------------- 2 files changed, 1903 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/91/44491/2 updated (d436f31e0 -> 2be6134fd)

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/91/44491/2 in repository toolchain/jenkins-scripts. discards d436f31e0 round-robin-notify.sh: Remove unnecessary info from jira reports discards 6215e36df round-robin-notify.sh: Simplify single_commit_p() and add a s [...] discards 01811153e round-robin-notify.sh: Move single_commit_p() here adds 2be6134fd round-robin-notify.sh: Move single_commit_p() here 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 (d436f31e0) \ N -- N -- N refs/changes/91/44491/2 (2be6134fd) 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: round-robin-bisect.sh | 647 ------------------------- round-robin-notify.sh | 1256 ------------------------------------------------- 2 files changed, 1903 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024