Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/43/30343/1 updated (92ae5624e -> 90dec5cc1)

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/43/30343/1 in repository toolchain/jenkins-scripts. discards 92ae5624e tcwg-dev-build: Enable builds using manifests new 90dec5cc1 tcwg-dev-build: Enable builds using manifests 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 (92ae5624e) \ N -- N -- N refs/changes/43/30343/1 (90dec5cc1) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/29843/4 updated (0b630c5a8 -> 5ece393b1)

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/43/29843/4 in repository toolchain/jenkins-scripts. discards 0b630c5a8 tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards dd49fbf78 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 06f786a9a tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 73d563e61 tcwg_kernel-bisect.sh: Remove --confirm_failure option discards 22b7df0e9 round-robin.sh: Improve comment. adds 5ece393b1 round-robin.sh: Improve comment. 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 (0b630c5a8) \ N -- N -- N refs/changes/43/29843/4 (5ece393b1) 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: tcwg_kernel-bisect.sh | 365 -------------------------------------------------- 1 file changed, 365 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/29843/3 updated (845244b56 -> 5ece393b1)

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/43/29843/3 in repository toolchain/jenkins-scripts. discards 845244b56 tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards c29f90f4f tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 8a8898023 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 73d563e61 tcwg_kernel-bisect.sh: Remove --confirm_failure option discards 22b7df0e9 round-robin.sh: Improve comment. adds 5ece393b1 round-robin.sh: Improve comment. 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 (845244b56) \ N -- N -- N refs/changes/43/29843/3 (5ece393b1) 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: tcwg_kernel-bisect.sh | 365 -------------------------------------------------- 1 file changed, 365 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/29843/2 updated (96da56ccf -> 964a669f3)

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/43/29843/2 in repository toolchain/jenkins-scripts. discards 96da56ccf tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards bdae8b950 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards d772207c8 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 82ffe64ac tcwg_kernel-bisect.sh: Remove --confirm_failure option discards bedb5b13e round-robin.sh: Improve comment. adds 964a669f3 round-robin.sh: Improve comment. 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 (96da56ccf) \ N -- N -- N refs/changes/43/29843/2 (964a669f3) 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: tcwg_kernel-bisect.sh | 365 -------------------------------------------------- 1 file changed, 365 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/43/29843/1 updated (10370ddfa -> 1efd682eb)

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/43/29843/1 in repository toolchain/jenkins-scripts. discards 10370ddfa tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards 582dd8440 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 883bead54 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards f484163fb tcwg_kernel-bisect.sh: Remove --confirm_failure option discards c20e3014f round-robin.sh: Improve comment. adds 1efd682eb round-robin.sh: Improve comment. 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 (10370ddfa) \ N -- N -- N refs/changes/43/29843/1 (1efd682eb) 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: tcwg_kernel-bisect.sh | 365 -------------------------------------------------- 1 file changed, 365 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/42/47042/2 updated (8c7637088 -> 2ff19b1bd)

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/42/47042/2 in repository toolchain/jenkins-scripts. discards 8c7637088 tcwg_chromium-build.sh: fix another issue adds 2ff19b1bd tcwg_chromium-build.sh: fix another issue 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 (8c7637088) \ N -- N -- N refs/changes/42/47042/2 (2ff19b1bd) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/42/47042/1 updated (973d46020 -> 28d585603)

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/42/47042/1 in repository toolchain/jenkins-scripts. discards 973d46020 tcwg_chromium-build.sh: fix another issue new 28d585603 tcwg_chromium-build.sh: fix another issue 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 (973d46020) \ N -- N -- N refs/changes/42/47042/1 (28d585603) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/42/46842/1 updated (e9c38a1f7 -> 286f5e4d4)

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/42/46842/1 in repository toolchain/jenkins-scripts. discards e9c38a1f7 round-robin.sh (build_abe): Fix thinko in previous commit adds 286f5e4d4 round-robin.sh (build_abe): Fix thinko in previous commit 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 (e9c38a1f7) \ N -- N -- N refs/changes/42/46842/1 (286f5e4d4) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/42/46342/1 updated (46d25e6d8 -> 62494a99a)

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/42/46342/1 in repository toolchain/jenkins-scripts. discards 46d25e6d8 round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...] adds 62494a99a round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...] 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 (46d25e6d8) \ N -- N -- N refs/changes/42/46342/1 (62494a99a) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/42/45642/3 updated (11c2ca8e2 -> 9485a171d)

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/42/45642/3 in repository toolchain/jenkins-scripts. discards 11c2ca8e2 tcwg_bmk-build.sh: rename samples-variabilty.py script adds 9485a171d tcwg_bmk-build.sh: rename samples-variabilty.py 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 (11c2ca8e2) \ N -- N -- N refs/changes/42/45642/3 (9485a171d) 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, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024