Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/91/42291/4 updated (aaacff4cc -> d5d769f69)

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/42291/4 in repository toolchain/jenkins-scripts. discards aaacff4cc tcwg_gnu-build.sh: Add tcwg_gnu_native_fast_check_gdb CI job adds d5d769f69 tcwg_gnu-build.sh: Add tcwg_gnu_native_fast_check_gdb CI job 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 (aaacff4cc) \ N -- N -- N refs/changes/91/42291/4 (d5d769f69) 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/42291/3 updated (a6be488e2 -> ebcdefbfd)

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/42291/3 in repository toolchain/jenkins-scripts. discards a6be488e2 tcwg_gnu-build.sh: Add tcwg_gnu_native_fast_check_gdb CI job new ebcdefbfd tcwg_gnu-build.sh: Add tcwg_gnu_native_fast_check_gdb CI job 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 (a6be488e2) \ N -- N -- N refs/changes/91/42291/3 (ebcdefbfd) 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/42291/2 updated (534eac358 -> a1b7a94bd)

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/42291/2 in repository toolchain/jenkins-scripts. discards 534eac358 tcwg_gnu-build.sh: Add tcwg_gnu_native_fast_check_gdb CI job new a1b7a94bd tcwg_gnu-build.sh: Add tcwg_gnu_native_fast_check_gdb CI job 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 (534eac358) \ N -- N -- N refs/changes/91/42291/2 (a1b7a94bd) 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/42291/1 updated (b5074b20c -> 336d96bc8)

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/42291/1 in repository toolchain/jenkins-scripts. discards b5074b20c tcwg_gnu-build.sh: Add tcwg_gnu_native_check_gdb_fast CI job new 336d96bc8 tcwg_gnu-build.sh: Add tcwg_gnu_native_check_gdb_fast CI job 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 (b5074b20c) \ N -- N -- N refs/changes/91/42291/1 (336d96bc8) 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/41891/3 updated (4d046afe3 -> 0bd584c5e)

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/41891/3 in repository toolchain/jenkins-scripts. discards 4d046afe3 round-robin.sh: Fix unbound variable adds 0bd584c5e round-robin.sh: Fix unbound variable 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 (4d046afe3) \ N -- N -- N refs/changes/91/41891/3 (0bd584c5e) 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/41891/2 updated (784d7096b -> add96506c)

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/41891/2 in repository toolchain/jenkins-scripts. discards 784d7096b round-robin.sh: Fix unbound variable new add96506c round-robin.sh: Fix unbound variable 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 (784d7096b) \ N -- N -- N refs/changes/91/41891/2 (add96506c) 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/41891/1 updated (1eb0fdf94 -> c0fb1c61f)

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/41891/1 in repository toolchain/jenkins-scripts. discards 1eb0fdf94 round-robin.sh: Fix unbound variable new c0fb1c61f round-robin.sh: Fix unbound variable 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 (1eb0fdf94) \ N -- N -- N refs/changes/91/41891/1 (c0fb1c61f) 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/39391/1 updated (e30c3f6e4 -> d09581cc0)

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/39391/1 in repository toolchain/jenkins-scripts. discards e30c3f6e4 tcwg_gnu-build.sh: Clean sysroot when re-building linux heade [...] adds d09581cc0 tcwg_gnu-build.sh: Clean sysroot when re-building linux heade [...] 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 (e30c3f6e4) \ N -- N -- N refs/changes/91/39391/1 (d09581cc0) 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/39291/1 updated (b94d1eccc -> 10bc0743e)

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/39291/1 in repository toolchain/jenkins-scripts. discards b94d1eccc round-robin-bisect.sh: Don't report regressions in bare-metal [...] discards 1ed20c0a7 round-robin-bisect.sh: Warn, but don't fail, on jira errors discards fb7852bee round-robin.sh (clone_repo): Fix checkout of branches adds 10bc0743e round-robin.sh (clone_repo): Fix checkout of branches 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 (b94d1eccc) \ N -- N -- N refs/changes/91/39291/1 (10bc0743e) 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 | 848 -------------------------------------------------- 1 file changed, 848 deletions(-) delete mode 100755 round-robin-bisect.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/39191/1 updated (902a54d9d -> 0380e905f)

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/39191/1 in repository toolchain/jenkins-scripts. discards 902a54d9d tcwg_gnu-build.sh, round-robin-bisect.sh: Ignore ERRORs in pa [...] adds 0380e905f tcwg_gnu-build.sh, round-robin-bisect.sh: Ignore ERRORs in pa [...] 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 (902a54d9d) \ N -- N -- N refs/changes/91/39191/1 (0380e905f) 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