Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allnoconfig updated (8e5885f8b -> 34cda80c4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 8e5885f8b 8: onsuccess: #352: all: Success after binutils/gcc: 14 commits new 34cda80c4 9: onsuccess: #353: all: Success after binutils/gcc/linux/qem [...] 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: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29672 -> 29952 bytes 04-build_abe-stage1/console.log.xz | Bin 86556 -> 86736 bytes 05-build_abe-qemu/console.log.xz | Bin 31444 -> 31248 bytes 06-build_linux/console.log.xz | Bin 3284 -> 3280 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 2300 -> 3140 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- 17 files changed, 23 insertions(+), 23 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (572a9511d -> 355e53293)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 572a9511d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 703b5ba3f 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards f343c37c1 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f40d3d1fe 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 78e9234ca 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards a67e40d49 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 423d632b9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 2fe4b80d6 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5e2b85aff 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 3bfe84bb1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 74cba0ee2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 5c55f26b5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards e65d59fec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d8a7c5b7e 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5f9edd828 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e5d063b5c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 930fdea9a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards d21c3a7b5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9b6be0ed6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 723f790c1 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 91e14651f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ce8eb716f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards fee763086 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards d92e4d0cf 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 5b7f4caea 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 24c24d32d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a533287e2 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9aea2efd3 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 119f191d5 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8ca1fc43a 74: onsuccess: 1: Successful build after linux: 44 commits discards 7293f0e69 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f0dc098a6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 115de6c42 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 9bff44834 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 8eb679ff5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 418322a8c 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e7c95c4e3 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5a4f832a0 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7f59733fe 65: onsuccess: 1: Successful build after gcc: 4 commits discards 57ddab8a7 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 554aa3450 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 271b58c1a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards b70a3141d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 08cab8924 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 53fa26449 59: onsuccess: 1: Successful build after glibc: 2 commits discards 088972302 58: onsuccess: 1: Successful build after binutils: 2 commits discards a3a0d7ad0 57: onsuccess: 1: Successful build after gcc: 7 commits discards e7193d373 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 70f67c98b 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b2c1cd69d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 2e16f2d8e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 44466bbf2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 742bdf494 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 17320803f 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b8359bf09 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0732d90ee 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 3fa116c0d 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ba19fd793 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 673a5b625 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8d924d2ad 44: onsuccess: 1: Successful build after linux: 34 commits discards 3416d7be0 43: onsuccess: 1: Successful build after gcc: 2 commits discards fe841ba8e 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 23a23a643 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 82cec5ea6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3698781ce 39: onsuccess: 1: Successful build after gcc: 2 commits discards 7ddbcc615 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7b0858065 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d9d8f85f4 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cb606bf67 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d2c3a527e 34: onsuccess: 1: Successful build after gcc: 3 commits discards 02662aa06 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 93ec0dc3c 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 89515ae64 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8c64d1d1a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 6284647ae 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9364aa344 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards c0078cec1 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1ab54aa07 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a0957fd78 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6455d4cd6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 506c53687 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ca7955754 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 71dfc0984 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c3e6d037a 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0fed02ad3 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5cd6a5330 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 27fc6bff8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4264f6899 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1688a5605 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4f12f92ff 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards be49792c9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5d254fdad 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9106f8fb3 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ee50988fe 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 832e17817 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ee9bcd19f 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 162dbd4e5 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 69f9384f2 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eb2e6b9e6 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e22409953 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 22581b48e 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 99c3d74fb 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8e148508b 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 85caa0ff9 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e9ed7ecac 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 75dde4ec7 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6280aaa9e 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 00ea325bc 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 125ad721a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ca9a5cdd8 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 233320195 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3921d8682 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bc83519f0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2609a8393 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 69a4757ff 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dab579f07 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5b42fe53b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b6958ecaf 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2dd167798 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7be95817c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 35d95f629 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1c0034631 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 57d13eeb5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ec54a6f85 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 87e53f2f7 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c09aa71bd 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ede47a1bd 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6ff172cce 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a74402856 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 5f22387c1 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ee10c44b5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0a131af09 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c8c54557d 34: onsuccess: 1: Successful build after gcc: 3 commits new 9f4a4b225 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 73a832a73 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2619c4c39 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2fff71aac 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ffd6ee2f1 39: onsuccess: 1: Successful build after gcc: 2 commits new 7247b3934 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 777a6e8fa 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b059f6bb8 42: onsuccess: 1: Successful build after baseline build: no n [...] new c4f2493c5 43: onsuccess: 1: Successful build after gcc: 2 commits new 45d25b40e 44: onsuccess: 1: Successful build after linux: 34 commits new e4edaa215 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2e99ce5e9 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new e89dde60c 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7520c904a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 1b384883b 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b63df51fe 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b97175acf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 463e37143 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 134965146 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 38b08df35 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 805dd4b54 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3e775270b 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7c8011495 57: onsuccess: 1: Successful build after gcc: 7 commits new 6b858086a 58: onsuccess: 1: Successful build after binutils: 2 commits new 8a55d4d7d 59: onsuccess: 1: Successful build after glibc: 2 commits new 74bbe6f5f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 8f24d13ee 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d7c0807bd 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 1c43efaa2 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c9cf76439 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a3b4ff99f 65: onsuccess: 1: Successful build after gcc: 4 commits new 024d382f2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1dd647693 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 039e8a334 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5f08983c3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 5c7d2140a 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 91b4561f6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 9fb16a636 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dba325a11 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b14d2c676 74: onsuccess: 1: Successful build after linux: 44 commits new 49f84d072 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fa7fcab94 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 3380bc01c 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 61d2f76c4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ec5dfbd66 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 8a1f84b98 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 5ebb5a84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d476329e2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ed33d02ad 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new bd291c65e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 47da9a3b0 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 61b9c3fd1 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 427175eac 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f8bd5478c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new db9f6efca 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 967c29c14 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6cca1fc61 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new cbd945ccf 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new c306296b2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 974beb9e1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new d30cdf24a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 4557a80e0 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 85486502c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new f99f636bf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 99813c136 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new e79a0280f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 64a0c9043 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 8f438942e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new b5897afa8 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 355e53293 104: onsuccess: #1697: 1: Success after gcc: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (572a9511d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1824 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29824 -> 29936 bytes 04-build_abe-stage1/console.log.xz | Bin 90976 -> 90604 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 233924 -> 234112 bytes 08-build_abe-stage2/console.log.xz | Bin 223180 -> 223708 bytes 09-build_abe-gdb/console.log.xz | Bin 37132 -> 37100 bytes 10-build_abe-qemu/console.log.xz | Bin 31828 -> 31264 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2584 bytes 13-check_regression/console.log.xz | Bin 4608 -> 4208 bytes 13-check_regression/mail-body.txt | 50 - 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 24 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 52 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2680256 -> 2648552 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2196224 -> 2229700 bytes sumfiles/gcc.sum | 2654 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 878412 -> 882076 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201128 -> 201196 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422780 -> 418400 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 1512 insertions(+), 1604 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (6e9076758 -> 98d7e017f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts. discards 6e9076758 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards d84339a19 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards c160ef0d4 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 0b3292ac8 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards e09d71fa9 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 3afe614e3 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards e2113ac6d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards f8726c025 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards c16b401db 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 4b963d43e 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards b40eaf4fb 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards deeaed71f 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 18a93f783 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 7a16c44f4 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards f2e6e0fe9 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 5def9cab7 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards e187dea06 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 9b3d7c669 88: onsuccess: 1: Success after gcc: 20 commits discards dd1f4858f 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 39638e569 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards fb1f3d037 85: onsuccess: 2: Success after binutils: 4 commits discards 31cadeebf 84: onsuccess: 2: Success after gcc: 9 commits discards e87ecdd19 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards cc967b7d2 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards e5896950d 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 1a9752b37 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 5fe0895fd 79: onsuccess: 1: Successful build after gcc: 3 commits discards e127adaa2 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards a12163c45 77: force: 2: Successful build after gcc: 32 commits discards c3270fca4 76: onsuccess: 2: Successful build after binutils: 10 commits discards 9cd3e7df7 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ee3711fc8 74: onsuccess: 2: Successful build after gcc: 13 commits discards 648038ba0 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards dc6c9c434 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards d13b72a57 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 613564bd6 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 8ce4bf51c 69: onsuccess: 2: Successful build after baseline build: no n [...] discards 18f173e8a 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9901fe64d 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 968a75a1d 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 5ba6f8d70 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e0114560f 64: onsuccess: 2: Successful build after gcc: 7 commits discards e6702375c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 5376f52b8 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3e6322087 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 8e763eeaf 60: onsuccess: 1: Successful build after gcc: 15 commits discards 30301ee6f 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 470c9f10d 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards d5daa3204 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 4e6446c62 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards b6f5c2d95 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7e145a5d9 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f05876c92 53: onsuccess: 2: Successful build after gcc: 5 commits discards 588b37cf2 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 6ace02c46 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards a6d06dc0f 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 05d0d198c 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 2f722e37e 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8cf6e6785 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2bc955dc1 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards dfaf87a85 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 6d9db78b3 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 58d14a072 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 7543dd024 42: onsuccess: 2: Successful build after gcc: 2 commits discards fa2b4ac21 41: onsuccess: 2: Successful build after baseline build: no n [...] discards a18752bc3 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ae6773524 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4473232cc 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 3a80322e5 37: onsuccess: 2: Successful build after gcc: 2 commits discards 432355391 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 711e3b9a0 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d1b99f6df 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 56902d7bd 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7575bb72a 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards bd0127bae 31: onsuccess: 2: Successful build after gcc: 8 commits discards 565214e5c 30: onsuccess: 2: Successful build after gcc: 7 commits discards b5752b660 29: onsuccess: 2: Successful build after binutils: 5 commits discards eb12dc029 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1264893dd 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 0680d3b2b 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards de2056f27 25: onsuccess: binutils-gcc: 2 discards eb9c5112d 24: onsuccess: binutils-gcc: 2 discards c442f9b34 23: onsuccess: binutils-gcc: 2 discards 071047d20 22: onsuccess: binutils-gcc: 2 discards 20f85561c 21: onsuccess: binutils-gcc: 2 discards 30ede983b 20: onsuccess: binutils-gcc: 2 discards 30e789463 19: onsuccess: binutils-gcc: 2 discards e4cef45aa 18: onsuccess: binutils-gcc: 2 discards 53470177a 17: onsuccess: binutils-gcc: 2 discards 35369e426 16: onsuccess: binutils-gcc: 2 discards f6ce57dc8 15: onsuccess: binutils-gcc: 2 discards 9b4de7fe3 14: onsuccess: binutils-gcc: 2 discards a2cbc3a1f 13: onsuccess: binutils-gcc: 2 discards 131548974 12: onsuccess: binutils-gcc: 2 discards 8eee5246d 11: onsuccess: binutils-gcc: 2 discards 8cd4fe249 10: onsuccess: binutils-gcc: 2 discards 475da8790 9: onsuccess: binutils-gcc: 2 discards 6cee6758f 8: onsuccess: binutils-gcc: 2 discards 756d4e48e 7: onsuccess: binutils-gcc: 2 discards ab5667c4e 6: onsuccess: binutils-gcc: 2 discards 777a4b164 5: onsuccess: binutils-gcc: 2 new 15f951e66 5: onsuccess: binutils-gcc: 2 new 2812c62ea 6: onsuccess: binutils-gcc: 2 new 86ce73d6f 7: onsuccess: binutils-gcc: 2 new c249f0800 8: onsuccess: binutils-gcc: 2 new b7994087b 9: onsuccess: binutils-gcc: 2 new 8ee327f6b 10: onsuccess: binutils-gcc: 2 new 84c43766e 11: onsuccess: binutils-gcc: 2 new 1e77ce33c 12: onsuccess: binutils-gcc: 2 new 92bb8f20f 13: onsuccess: binutils-gcc: 2 new ba8f9563f 14: onsuccess: binutils-gcc: 2 new 8b9d40086 15: onsuccess: binutils-gcc: 2 new 45bd1bfd6 16: onsuccess: binutils-gcc: 2 new 2b894bd96 17: onsuccess: binutils-gcc: 2 new d0a01aaff 18: onsuccess: binutils-gcc: 2 new 4b1f03772 19: onsuccess: binutils-gcc: 2 new 1630e4724 20: onsuccess: binutils-gcc: 2 new c0e5fd878 21: onsuccess: binutils-gcc: 2 new 29f5c9d74 22: onsuccess: binutils-gcc: 2 new c8696f08a 23: onsuccess: binutils-gcc: 2 new 393032a82 24: onsuccess: binutils-gcc: 2 new 6af2760ca 25: onsuccess: binutils-gcc: 2 new de0e1fe92 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 49c1994d6 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new c94efd3b2 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 43dc5dc8e 29: onsuccess: 2: Successful build after binutils: 5 commits new 39b268b70 30: onsuccess: 2: Successful build after gcc: 7 commits new f6ea0022b 31: onsuccess: 2: Successful build after gcc: 8 commits new 74d46935e 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 21d10ae19 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 36454cbef 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 0880cbdcb 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 0b07143ec 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new be7a18abe 37: onsuccess: 2: Successful build after gcc: 2 commits new 82848da6c 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new c93041290 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0c317c82f 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new f7cd01118 41: onsuccess: 2: Successful build after baseline build: no n [...] new f4255d291 42: onsuccess: 2: Successful build after gcc: 2 commits new a10a4e239 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 1f43cd120 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f420bf728 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 5acbb8cad 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 6d3f4bb97 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f99997c60 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9941c3861 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 7d6f7cc55 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2be8e151e 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 750efea99 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new cea39bf46 53: onsuccess: 2: Successful build after gcc: 5 commits new 3a2793a81 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c71618087 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 37cf8475f 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 965a52556 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 0cad5c619 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new 5e6d81205 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 33810c866 60: onsuccess: 1: Successful build after gcc: 15 commits new 93c71ab06 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new f13f97d3a 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8fed58f43 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 4c0b2d648 64: onsuccess: 2: Successful build after gcc: 7 commits new 60f141079 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2f6761248 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 6e23c83ad 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6b4ba0b65 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a45f2fa93 69: onsuccess: 2: Successful build after baseline build: no n [...] new 004ab8b83 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 7cfc216de 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4f39680a8 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new bed0acba3 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 94af51c05 74: onsuccess: 2: Successful build after gcc: 13 commits new 93a50bc5d 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 8d078eff0 76: onsuccess: 2: Successful build after binutils: 10 commits new 883a16051 77: force: 2: Successful build after gcc: 32 commits new 27fb2fc78 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 864541a66 79: onsuccess: 1: Successful build after gcc: 3 commits new 59d4cbecd 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 5617d0761 81: onsuccess: 2: Success after binutils/gcc: 16 commits new c9d3d2416 82: onsuccess: 2: Success after binutils/gcc: 26 commits new b8cb1613d 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 08cc4fde5 84: onsuccess: 2: Success after gcc: 9 commits new d985f5574 85: onsuccess: 2: Success after binutils: 4 commits new 76a8117df 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 1570b10f9 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 5126568cc 88: onsuccess: 1: Success after gcc: 20 commits new db2b9f452 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 9a16f7f28 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 05cd5a63d 91: onsuccess: #1473: 2: Success after gcc: 2 commits new ca9e599f1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 8d2885afb 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new 475efe8a7 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 5f819adce 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 5cd751643 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 5ba518eb0 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 6928af192 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 3ce1ce489 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new a8874b2be 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 757561b1d 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new cac917733 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 4f08c6bc2 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 61fd26186 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 2e5d162b6 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 98d7e017f 106: onsuccess: #1527: 2: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (6e9076758) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1676 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2712 bytes 04-build_abe-binutils/console.log.xz | Bin 37628 -> 37600 bytes 05-build_abe-bootstrap/console.log.xz | Bin 271668 -> 269760 bytes 06-check_regression/console.log.xz | Bin 1804 -> 1792 bytes 07-update_baseline/console.log | 58 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- manifest.sh | 12 +++---- 9 files changed, 37 insertions(+), 37 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto_lean updated (2164a4d8c -> fa0310ae1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from 2164a4d8c 11: onsuccess: #118: 2: Success after binutils/gcc: 12 commits new fa0310ae1 12: onsuccess: #119: 2: Success after binutils/gcc: 9 commits 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: 01-reset_artifacts/console.log.xz | Bin 1680 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50708 -> 50820 bytes .../console.log.xz | Bin 932360 -> 937060 bytes 06-check_regression/console.log.xz | Bin 2096 -> 2124 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++++--------- 12 files changed, 15 insertions(+), 15 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean updated (c83d5c873 -> b4a97d275)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto_lean in repository toolchain/ci/base-artifacts. from c83d5c873 38: onsuccess: #413: 2: Success after binutils/gcc: 25 commits new b4a97d275 39: onsuccess: #414: 2: Success after binutils/gcc: 6 commits 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: 01-reset_artifacts/console.log.xz | Bin 1808 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 51372 -> 50304 bytes .../console.log.xz | Bin 938188 -> 941440 bytes 06-check_regression/console.log.xz | Bin 2344 -> 2032 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 12 files changed, 14 insertions(+), 14 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (b71b12c9c -> f752500b5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards b71b12c9c 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards ac52c14e8 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] discards 2bb875f97 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 2edc6e9d0 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] discards df1183769 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] discards 64ef07bab 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 326ab9537 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] discards b5e828028 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] discards 6a7a0d6a9 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 682cbce2b 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] discards b231ce17c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] discards 07a88ea27 95: onsuccess: #1529: 7: Success after baseline build: no new [...] discards 690d81d38 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 134d5141c 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] discards c54b0204e 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 32c351e54 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 59d12b55e 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 203c8b245 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 73d49b73e 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 64b73de20 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 091ef3a83 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 617829898 85: onsuccess: 7: Success after gcc: 9 commits discards c6a87faab 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 148fbf2b7 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards a67f336a8 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards ab6f268e4 81: onsuccess: 7: Successful build after gcc: 2 commits discards 1f3f28be7 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards efe644422 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 5d9375a37 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b12415009 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards c574024b2 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 3782c315b 75: onsuccess: 7: Successful build after linux: 44 commits discards 53a49df8f 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards be70ca262 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 911c9b605 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 7404fbea2 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards ffcf00cc2 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 87da99bfa 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards e776ee3b1 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards dd9e8afbe 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4500c19f6 66: onsuccess: 7: Successful build after gcc: 3 commits discards a80b9c313 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cf09a29ef 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0266e0112 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards d8ecc6513 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards b76197842 61: onsuccess: 4: Successful build after gcc: 15 commits discards fea118aed 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards e4591db78 59: force: 7: Successful build after gcc: 2 commits discards e9bcdd716 58: onsuccess: 7: Successful build after glibc: 2 commits discards ff8b1d990 57: onsuccess: 7: Successful build after gcc: 7 commits discards 34cd050cf 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 046f05da8 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fefe1e24e 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 4ec5a8644 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] discards a3a98627a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards fad2f9fb4 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards ddb930b27 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 2f7841333 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards c1b201c31 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 017159daa 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 43bbe622b 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards f53c0c856 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6b9a7897c 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards cdec483d2 43: onsuccess: 7: Successful build after gcc: 2 commits discards 74da085dd 42: onsuccess: 7: Successful build after baseline build: no n [...] discards d7ad67ce0 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7369d9cf6 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 72147d516 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits discards cd633df01 38: onsuccess: 7: Successful build after gcc/linux: 94 commits discards aefa9fa2d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 96b9b29e2 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 09b1dc3a1 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 7db600b22 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 1cd53dcdc 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6e0c51cd1 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 02c9f221b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f6fe8b0e7 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards c84056e17 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 94e5195e7 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards a745c928a 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 997bd8301 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards be0e7a661 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 29dcf2782 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 841b3de2d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3c947d902 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2a97f37c4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8143210f9 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9b254a859 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7d0a54e08 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7796c943a 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b7852f535 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 616f1b2a0 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 37b4f9cee 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4266f9c09 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b77cde2b3 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e768eafbf 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 51343f027 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fbf653606 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9f258e127 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9948bbd4e 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f28b3b495 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1089b3436 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c103fcefc 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3a2842477 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ec2103972 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7c62eb16d 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84edebcdc 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 11179f36d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new df8222ec3 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9ba861b5f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 78cd73d54 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 864adeba9 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d0405245c 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9f12fde28 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 42271e6a9 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c57f4eddb 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2d158625d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d93a3d64f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 94124291b 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 449e693bf 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c6f62672a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7e5b32e17 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new fa60f4ba0 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 211fb3104 28: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5700e5e99 29: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 93634f04f 30: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new aa709da91 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 3a0224fac 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new c86c4c471 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new d6c08525e 34: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 22250cf0d 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new ac2f2df17 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1a2a10c3d 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new eb08f3a08 38: onsuccess: 7: Successful build after gcc/linux: 94 commits new 469900fb7 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 commits new ca86eaf6b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 65d0ec0d9 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new bdfa2ade0 42: onsuccess: 7: Successful build after baseline build: no n [...] new adc3f822b 43: onsuccess: 7: Successful build after gcc: 2 commits new d54dd49c2 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 2a9a5134a 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 91e5b20aa 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new aa2500ffc 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3b754ac9f 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 76d1f436d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9af8e3e45 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 49733247a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9d5a17235 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 72f98604b 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 12 [...] new 57c41daf5 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 1cbca3d0b 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0594ece6c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3c8d70c69 57: onsuccess: 7: Successful build after gcc: 7 commits new 4b9415973 58: onsuccess: 7: Successful build after glibc: 2 commits new da33f1d38 59: force: 7: Successful build after gcc: 2 commits new ae7b28ef2 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 27156c50b 61: onsuccess: 4: Successful build after gcc: 15 commits new 673a59cf4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 84ab553e0 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 34587bd7a 64: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 336cf78cf 65: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 8647cdcd6 66: onsuccess: 7: Successful build after gcc: 3 commits new 2be0feb10 67: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 401983ecb 68: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3a5fb57c5 69: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c2a7b6602 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 4a835e2c3 71: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new ec8e5b22d 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 41c918fe6 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2b02f6a8c 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 464bc4b40 75: onsuccess: 7: Successful build after linux: 44 commits new 325e089b3 76: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3b71b0a57 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 5a1d13e29 78: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9898318fc 79: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 583bd3bd4 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new bb208fe85 81: onsuccess: 7: Successful build after gcc: 2 commits new 1182870c2 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 5a1fa0c01 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 5a12ae682 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2b5217168 85: onsuccess: 7: Success after gcc: 9 commits new 59464e9f9 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 9d1d26530 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 86b5dd348 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 78a5d3a60 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 01713bc14 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 943c5a4ab 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b64d2901b 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new fba3124ae 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gdb [...] new 73ea13154 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new abd2aff0a 95: onsuccess: #1529: 7: Success after baseline build: no new [...] new ca6ccd4f8 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gdb [...] new 492534169 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gdb [...] new d6d14ad3b 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new cc78b3a1c 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gdb [...] new a5a53399f 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/gd [...] new 1248222c1 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 9e5c9d6fc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/gl [...] new 5a416f32a 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-271 [...] new bdcafddcc 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 2b084ce7c 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/gd [...] new d499fac43 106: onsuccess: #1617: 7: Success after gcc: 2 commits new f752500b5 107: onsuccess: #1618: 7: Success after gcc: 2 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (b71b12c9c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1728 -> 1864 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 29852 -> 29812 bytes 05-build_abe-stage1/console.log.xz | Bin 91456 -> 90960 bytes 07-build_abe-linux/console.log.xz | Bin 8628 -> 8596 bytes 08-build_abe-glibc/console.log.xz | Bin 233860 -> 233584 bytes 09-build_abe-stage2/console.log.xz | Bin 224132 -> 223780 bytes 10-build_abe-gdb/console.log.xz | Bin 37152 -> 37268 bytes 11-build_abe-qemu/console.log.xz | Bin 31192 -> 31248 bytes 12-check_regression/console.log.xz | Bin 2324 -> 2136 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- manifest.sh | 22 ++++++------ 14 files changed, 45 insertions(+), 45 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-release-aarch64-spec2k6-Os updated (effcd410d -> ff2bf96c2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_gnu_apm/gnu-release-aarch64-spec2k6-Os in repository toolchain/ci/base-artifacts. from effcd410d 8: onsuccess: #72: 1: [TCWG CI] No change after binutils/gcc/ [...] new ff2bf96c2 9: onsuccess: #73: 1: [TCWG CI] No change after binutils/gcc/ [...] 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: 01-reset_artifacts/console.log.xz | Bin 1996 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30532 -> 30712 bytes 04-build_abe-stage1/console.log.xz | Bin 69768 -> 70400 bytes 06-build_abe-linux/console.log.xz | Bin 7876 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 237512 -> 238196 bytes 08-build_abe-stage2/console.log.xz | Bin 173976 -> 177200 bytes 09-benchmark/benchmark-build.log | 102 +- 09-benchmark/benchmark.log | 100 +- 09-benchmark/console.log.xz | Bin 3692 -> 3692 bytes 10-check_regression/console.log.xz | Bin 9940 -> 10056 bytes 10-check_regression/csv-results-0/md5sum.csv | 78656 +- 10-check_regression/csv-results-0/perf.csv | 3957 +- 10-check_regression/csv-results-0/results.csv | 687074 +++++++++--------- 10-check_regression/csv-results-0/size.csv | 685331 +++++++++-------- 10-check_regression/csv-results-0/vect.csv | 46 +- 10-check_regression/csv-results-1/md5sum.csv | 50336 +- 10-check_regression/csv-results-1/perf.csv | 3694 +- 10-check_regression/csv-results-1/results.csv | 687021 ++++++++--------- 10-check_regression/csv-results-1/size.csv | 685530 ++++++++--------- 10-check_regression/csv-results-1/vect.csv | 36 +- 10-check_regression/results-brief.csv | 59 +- 10-check_regression/results-compare.csv | 14 +- 10-check_regression/results-full.csv | 3803 +- 10-check_regression/results-internal.csv | 246 +- 10-check_regression/results.csv | 246 +- 10-check_regression/results.log | 1440 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 19 +- dashboard/squad/400.perlbench/results-metrics.json | 2 +- dashboard/squad/401.bzip2/results-metadata.json | 19 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 19 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/410.bwaves/results-metadata.json | 19 +- dashboard/squad/410.bwaves/results-metrics.json | 2 +- dashboard/squad/416.gamess/results-metadata.json | 19 +- dashboard/squad/416.gamess/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 19 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 19 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/434.zeusmp/results-metadata.json | 19 +- dashboard/squad/434.zeusmp/results-metrics.json | 2 +- dashboard/squad/435.gromacs/results-metadata.json | 19 +- dashboard/squad/435.gromacs/results-metrics.json | 2 +- .../squad/436.cactusADM/results-metadata.json | 19 +- dashboard/squad/436.cactusADM/results-metrics.json | 2 +- dashboard/squad/437.leslie3d/results-metadata.json | 19 +- dashboard/squad/437.leslie3d/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 19 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 19 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 19 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 19 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 19 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/454.calculix/results-metadata.json | 19 +- dashboard/squad/454.calculix/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 19 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 19 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- dashboard/squad/459.GemsFDTD/results-metadata.json | 19 +- dashboard/squad/459.GemsFDTD/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 19 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 19 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/465.tonto/results-metadata.json | 19 +- dashboard/squad/465.tonto/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 19 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 19 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 19 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/481.wrf/results-metadata.json | 19 +- dashboard/squad/481.wrf/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 19 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 19 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- .../results-functional.json | 0 dashboard/squad/Mean/results-metadata.json | 12 + dashboard/squad/Mean/results-metrics.json | 5 + dashboard/squad/dashboard-push-squad.sh | 519 +- dashboard/squad/summary-annotation.txt | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 48 +- mail/mail-body.txt | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1276368 -> 1281648 bytes save-temps/401.bzip2.tar.xz | Bin 94184 -> 94296 bytes save-temps/403.gcc.tar.xz | Bin 3578488 -> 3566324 bytes save-temps/410.bwaves.tar.xz | Bin 15104 -> 15108 bytes save-temps/416.gamess.tar.xz | Bin 4217844 -> 4209356 bytes save-temps/429.mcf.tar.xz | Bin 36436 -> 36564 bytes save-temps/433.milc.tar.xz | Bin 167660 -> 167792 bytes save-temps/434.zeusmp.tar.xz | Bin 126324 -> 126276 bytes save-temps/435.gromacs.tar.xz | Bin 980240 -> 979172 bytes save-temps/436.cactusADM.tar.xz | Bin 723656 -> 725092 bytes save-temps/437.leslie3d.tar.xz | Bin 46388 -> 46332 bytes save-temps/444.namd.tar.xz | Bin 207892 -> 207504 bytes save-temps/445.gobmk.tar.xz | Bin 1820452 -> 1833676 bytes save-temps/447.dealII.tar.xz | Bin 6262232 -> 6164956 bytes save-temps/450.soplex.tar.xz | Bin 716168 -> 710012 bytes save-temps/453.povray.tar.xz | Bin 1410352 -> 1407944 bytes save-temps/454.calculix.tar.xz | Bin 1231072 -> 1231752 bytes save-temps/456.hmmer.tar.xz | Bin 379840 -> 379556 bytes save-temps/458.sjeng.tar.xz | Bin 148156 -> 148232 bytes save-temps/459.GemsFDTD.tar.xz | Bin 144972 -> 145204 bytes save-temps/462.libquantum.tar.xz | Bin 61476 -> 61720 bytes save-temps/464.h264ref.tar.xz | Bin 564004 -> 563104 bytes save-temps/465.tonto.tar.xz | Bin 2071788 -> 2069264 bytes save-temps/470.lbm.tar.xz | Bin 26332 -> 26340 bytes save-temps/471.omnetpp.tar.xz | Bin 1083504 -> 1066784 bytes save-temps/473.astar.tar.xz | Bin 88480 -> 88156 bytes save-temps/481.wrf.tar.xz | Bin 1563156 -> 1583604 bytes save-temps/482.sphinx3.tar.xz | Bin 255284 -> 254180 bytes save-temps/483.xalancbmk.tar.xz | Bin 11814700 -> 11851012 bytes 129 files changed, 1444401 insertions(+), 1444580 deletions(-) copy dashboard/squad/{400.perlbench => Mean}/results-functional.json (100%) create mode 100644 dashboard/squad/Mean/results-metadata.json create mode 100644 dashboard/squad/Mean/results-metrics.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (843ade1dd -> 392f03b2a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 843ade1dd 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards e598612ef 102: force: #1551: 1: Failure after gcc: 306 commits discards 31ae0291b 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 36d88a602 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 145238e1d 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 1c1f6e2ea 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 5df5a5a98 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7f566e941 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 685d58cad 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2516b6d2f 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 54cc1bc7b 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards d518b390a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 8886b4cfa 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 91e24bb13 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards d6d3f1624 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 1f3d7a396 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 67543a10e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 107bd8e1f 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards e2b8b8c46 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards bae7741b8 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 4c56ee9a4 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 50d9dac81 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 9aa28d780 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9fa037ad0 80: onsuccess: 7: Successful build after linux: 44 commits discards ff29eaa89 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards e4f088123 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 933fa6900 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards cd47fe659 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards aca0becd7 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards 653befc98 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 268c1cd96 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ac5c08751 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 42e77153a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 05946c22b 70: onsuccess: 7: Successful build after gcc: 4 commits discards 31004756a 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e4e159e7b 68: onsuccess: 7: Successful build after linux: 6 commits discards ee53df031 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards b4f14fae2 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 2a5a42aca 65: onsuccess: 7: Successful build after binutils: 3 commits discards bc9a64d8d 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 2bd658056 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 280021e60 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards a77a99f46 61: onsuccess: 4: Successful build after gcc: 5 commits discards 7b63e5e1d 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards a521fd5db 59: force: 7: Successful build after gcc: 3 commits discards 98403c564 58: onsuccess: 7: Successful build after glibc: 2 commits discards 2fcea9746 57: onsuccess: 7: Successful build after gcc: 7 commits discards c76a14dc2 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 90aab2862 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 815074825 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 59f97765c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards a0b44495c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 0ae4c664a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards e97b17499 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards fe38a05ef 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9a7ef59e5 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 82572adf7 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 34399be61 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards e45aafb9f 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 689b38b26 44: onsuccess: 7: Successful build after linux: 34 commits discards 276a2ace6 43: onsuccess: 7: Successful build after gcc: 2 commits discards 958a04413 42: onsuccess: 7: Successful build after baseline build: no n [...] discards d0ccd30f1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 80739eefc 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 25c9d37a3 39: onsuccess: 7: Successful build after gcc: 2 commits discards e06ddeb3a 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards abf92b020 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 6dea01ccb 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1ea47b44a 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 0ab8c2ab5 34: onsuccess: 7: Successful build after gcc: 3 commits discards a8d547548 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8ab292e48 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 3907a596a 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3549d1cc6 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards d8c77fe5c 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 199eeea7e 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards becbceafb 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards edf20b48f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6ce29e528 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5da47f33d 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards be2278ed1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 850fc8ec0 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a4d6e3eb2 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e75875cf6 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2b28acadb 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5a11cbfd5 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 55b9fff51 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e4e400ab6 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 833ae1bf8 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5b247de2c 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 292b857fe 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 716ba3878 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3fce669ee 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8e58ca000 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9ea228664 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d6b16a17b 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 961ab4453 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards fd1e1cc82 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 297b5e7c8 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d61738970 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6ebf4a805 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d322302b2 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0bad1b21d 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a9d5cb919 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 56d7e57f7 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1567e250d 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 86df744d3 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3e90b379f 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7420a7771 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 98e888841 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f621d52cf 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e3d2f534d 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a3e876cc2 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 969089912 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a196da6e4 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d66bb82e5 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a3e1b8fb9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a43c9fc8f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1863b5363 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5c8de57b0 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7941f67ff 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f2885003e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 259aa7378 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d3af495c7 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 93d25ffd4 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 345dc96eb 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new afb9fa6ca 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new e5f776f8c 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new c8d876bb3 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 753dbebdb 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new b97dd51d3 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 8afd44c81 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9074aa380 34: onsuccess: 7: Successful build after gcc: 3 commits new 12ae2ce9f 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 12ed13987 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 93654f6c0 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new d085117b3 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 942fea842 39: onsuccess: 7: Successful build after gcc: 2 commits new 64a00f38c 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new a653fe250 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5897046d3 42: onsuccess: 7: Successful build after baseline build: no n [...] new 5cea3edfc 43: onsuccess: 7: Successful build after gcc: 2 commits new c3e7e7a51 44: onsuccess: 7: Successful build after linux: 34 commits new 2487f54a9 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 31d6362a7 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new dfa196164 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new de0ac06b8 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new c1052ed47 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 43434caae 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ca46c697a 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 18f11173f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new cf4400274 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 90e3b13c4 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 1367dcd0e 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new daea09555 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 91bdabea7 57: onsuccess: 7: Successful build after gcc: 7 commits new b539ec3b2 58: onsuccess: 7: Successful build after glibc: 2 commits new 985e3c23e 59: force: 7: Successful build after gcc: 3 commits new 2244b062c 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new f2382b1a1 61: onsuccess: 4: Successful build after gcc: 5 commits new 664e3f3e2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new c19975518 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 1c3020e27 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 2bcff586e 65: onsuccess: 7: Successful build after binutils: 3 commits new 17f9e6cbf 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new e5f582638 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new e4dd58b7c 68: onsuccess: 7: Successful build after linux: 6 commits new b300509d0 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9fd2f8e2d 70: onsuccess: 7: Successful build after gcc: 4 commits new c64b387de 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 00e6742c8 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9cafb757c 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 6e2f8c1cd 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new dcd544e46 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 602aba6c2 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 3f933eacc 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new df78fc0b1 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new ce03d14c6 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 2dab7eb31 80: onsuccess: 7: Successful build after linux: 44 commits new e94842331 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 875e0363c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 4ed9a17f1 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b8e1e4771 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new cfe53c97c 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new 6f8a9e4bb 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 1d68b78db 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 66d2fa7bb 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 3aac75dbd 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b6dccf672 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 54886ca5f 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 57410ae1a 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 8dc4eb400 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 7c40ec1ba 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new e45200e7e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b86587ecd 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f091bd94a 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 85d1d6f94 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new fbcf70635 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new b2159501d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new c8eddcb5a 101: onsuccess: #1547: 7: Success after binutils: 82 commits new c234e8e72 102: force: #1551: 1: Failure after gcc: 306 commits new 8d83e0591 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 392f03b2a 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (843ade1dd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1612 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30388 -> 30080 bytes 05-build_abe-stage1/console.log.xz | Bin 60304 -> 72464 bytes 06-clean_sysroot/console.log.xz | Bin 0 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 0 -> 8580 bytes 08-build_abe-glibc/console.log.xz | Bin 0 -> 240112 bytes 09-build_abe-stage2/console.log.xz | Bin 0 -> 202304 bytes 10-build_abe-gdb/console.log.xz | Bin 0 -> 37360 bytes 11-build_abe-qemu/console.log.xz | Bin 0 -> 31840 bytes 12-check_regression/console.log.xz | Bin 1768 -> 3936 bytes 12-check_regression/mail-body.txt | 23 +++++----- 13-update_baseline/console.log | 58 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 + git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 25 ++++++----- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++++---- results | 12 +++++- 26 files changed, 101 insertions(+), 72 deletions(-) create mode 100644 06-clean_sysroot/console.log.xz create mode 100644 07-build_abe-linux/console.log.xz create mode 100644 08-build_abe-glibc/console.log.xz create mode 100644 09-build_abe-stage2/console.log.xz create mode 100644 10-build_abe-gdb/console.log.xz create mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 dashboard/squad/score/results-functional.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan updated (99265bb2f -> 665637c44)

by git＠git.linaro.org

2 years, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-aarch64 updated (177699aff -> 798456afa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-aarch64 in repository toolchain/ci/base-artifacts. discards 177699aff 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits discards 71f8b122d 103: onsuccess: #2020: 1: Success after gcc: 2 commits discards 99aed64fb 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] discards 1641e7f98 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits discards 29bb7eec8 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits discards 7175753b5 99: onsuccess: #1974: 1: Success after gcc: 14 commits discards 768741ae3 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits discards 9ad47cdef 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits discards e9878ad84 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] discards c6dc8691a 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] discards 8e526641a 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits discards e10e4ff86 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] discards 630bd1207 92: onsuccess: #1965: 1: Success after gcc: 2 commits discards 777f5ebb9 91: onsuccess: 1: Success after gcc: Daily bump. discards cc6cc27dd 90: onsuccess: 1: Success after binutils/gcc: 6 commits discards bebf7f6ec 89: onsuccess: 1: Success after binutils/gcc: 9 commits discards 9ddf8e75c 88: onsuccess: 1: Success after binutils/gcc: 16 commits discards 1ab34a090 87: onsuccess: 1: Success after binutils/gcc: 4 commits discards 0f15d7d88 86: onsuccess: 1: Success after binutils/gcc: 13 commits discards 4173a4656 85: onsuccess: 1: Success after binutils/gcc: 9 commits discards 28ca00a75 84: onsuccess: 1: Success after binutils/gcc: 9 commits discards 6c9e8b172 83: onsuccess: 1: Success after gcc: 8 commits discards 357bf52f3 82: onsuccess: 1: Success after binutils/gcc: 10 commits discards 99b20e265 81: onsuccess: 1: Success after binutils/gcc: 27 commits discards d5f8d118c 80: onsuccess: 1: Success after binutils/gcc: 14 commits discards 2b677b737 79: onsuccess: 1: Successful build after gcc: Daily bump. discards 3c68b98ed 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 8f3af6f35 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards d1183ed37 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits discards 3a3bdf508 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits discards 91fc1e396 74: onsuccess: 1: Successful build after binutils: Automatic [...] discards 284d555de 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] discards 085d7c594 72: onsuccess: 1: Successful build after gcc: 2 commits discards 5f2ff4334 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits discards ced90c37e 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] discards 9fd50d6a9 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards fbcb97928 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 145249624 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 0b8012086 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards f09adc4f1 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 056fb54b9 64: onsuccess: 1: Successful build after gcc: 5 commits discards 07e641e2c 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards debcc2774 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards d674b68e4 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits discards b4542af01 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards 8c5a0bada 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits discards 8869f89dd 58: onsuccess: 1: Successful build after binutils: 2 commits discards 9731e3fa5 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards 10d700818 56: onsuccess: 1: Successful build after gcc: Daily bump. discards db474937c 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 4d1bb7c03 54: onsuccess: 1: Successful build after gcc: 7 commits discards d15aa23e3 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits discards b4affad6b 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards cbe4f53a7 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6290c3bd9 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 9a7d5d712 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 09e868963 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a689bb34e 47: onsuccess: 1: Successful build after binutils: 2 commits discards c0e3ed3c8 46: onsuccess: 1: Successful build after gcc: Daily bump. discards 3e7fbde74 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits discards 005e898fa 44: onsuccess: 1: Successful build after gcc: 2 commits discards 6c920b431 43: onsuccess: 1: Successful build after gcc: Daily bump. discards 17d15af20 42: onsuccess: 1: Successful build after binutils: Automatic [...] discards ce85fea48 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits discards 493d74ff7 40: onsuccess: 1: Successful build after gcc: 2 commits discards 8b1044f02 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards a3f815d86 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards 81cae6381 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits discards cb40455ef 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits discards 507ea1007 35: onsuccess: 1: Successful build after gcc: 4 commits discards e6f348913 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits discards b1b0e7764 33: onsuccess: 1: Successful build after gcc: 10 commits discards b7f46282c 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits discards e04f4d8b1 31: onsuccess: 1: Successful build after gcc: 2 commits discards 37d526596 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits discards e1286750c 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits discards 8455ac45b 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits discards 8ecc28feb 27: onsuccess: binutils-gcc: 1 discards 78f4fae5f 26: onsuccess: binutils-gcc: 1 discards d1e5f2736 25: onsuccess: binutils-gcc: 1 discards 1b8545542 24: onsuccess: binutils-gcc: 1 discards 965edf652 23: onsuccess: binutils-gcc: 1 discards 0fea1ea05 22: onsuccess: binutils-gcc: 1 discards ddfbf84d7 21: onsuccess: binutils-gcc: 1 discards d5bb6339b 20: onsuccess: binutils-gcc: 1 discards 4d5edd0fb 19: onsuccess: binutils-gcc: 1 discards 3cf1b3066 18: onsuccess: binutils-gcc: 1 discards 9e3d73634 17: onsuccess: binutils-gcc: 1 discards de742862f 16: onsuccess: binutils-gcc: 1 discards 95640f7d6 15: onsuccess: binutils-gcc: 1 discards 3ce3ef10b 14: onsuccess: binutils-gcc: 1 discards a255274a5 13: onsuccess: binutils-gcc: 1 discards e6e9e673a 12: onsuccess: binutils-gcc: 1 discards 134310940 11: onsuccess: binutils-gcc: 1 discards cfb78c084 10: onsuccess: binutils-gcc: 1 discards 3517ccb3c 9: onsuccess: binutils-gcc: 1 discards 3a07ccd55 8: onsuccess: binutils-gcc: 1 discards a05684995 7: onsuccess: binutils-gcc: 1 discards 20dbe2d9e 6: onsuccess: binutils-gcc: 1 discards 45fdea420 5: onsuccess: binutils-gcc: 1 discards 02ff502cd 4: onsuccess: binutils-gcc: 1 new d8974a697 4: onsuccess: binutils-gcc: 1 new c2a1c0bfd 5: onsuccess: binutils-gcc: 1 new e62d1f9ca 6: onsuccess: binutils-gcc: 1 new cc5e1f579 7: onsuccess: binutils-gcc: 1 new fcc3c8e5c 8: onsuccess: binutils-gcc: 1 new 9a2db5128 9: onsuccess: binutils-gcc: 1 new e4bc28b9c 10: onsuccess: binutils-gcc: 1 new 0adfe3209 11: onsuccess: binutils-gcc: 1 new ac81e3a4e 12: onsuccess: binutils-gcc: 1 new 1cfbb03c9 13: onsuccess: binutils-gcc: 1 new a1a18c655 14: onsuccess: binutils-gcc: 1 new 9ba022cd6 15: onsuccess: binutils-gcc: 1 new bab81aa61 16: onsuccess: binutils-gcc: 1 new 295f3fdb3 17: onsuccess: binutils-gcc: 1 new 1aee7406f 18: onsuccess: binutils-gcc: 1 new e1cf24ddb 19: onsuccess: binutils-gcc: 1 new ede66b592 20: onsuccess: binutils-gcc: 1 new 03f3f4f4f 21: onsuccess: binutils-gcc: 1 new 5a1ab5abd 22: onsuccess: binutils-gcc: 1 new f92503454 23: onsuccess: binutils-gcc: 1 new 09e4e87a0 24: onsuccess: binutils-gcc: 1 new df667b220 25: onsuccess: binutils-gcc: 1 new b8eaaee98 26: onsuccess: binutils-gcc: 1 new 0ae20ffba 27: onsuccess: binutils-gcc: 1 new 95252a328 28: onsuccess: 1: Successful build after binutils/gcc: 22 commits new 32aaa41bb 29: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 43d7d13fa 30: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3b4e2a27e 31: onsuccess: 1: Successful build after gcc: 2 commits new 7c55f246f 32: onsuccess: 1: Successful build after binutils/gcc: 9 commits new e19e088ad 33: onsuccess: 1: Successful build after gcc: 10 commits new 48fdbde3c 34: onsuccess: 1: Successful build after binutils/gcc: 5 commits new c1bc795d0 35: onsuccess: 1: Successful build after gcc: 4 commits new 1c7a38d0b 36: onsuccess: 1: Successful build after binutils/gcc: 11 commits new 531c8f163 37: onsuccess: 1: Successful build after binutils/gcc: 12 commits new 32f04ac32 38: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 8df94e652 39: onsuccess: 1: Successful build after binutils/gcc: 3 commits new d16805170 40: onsuccess: 1: Successful build after gcc: 2 commits new b3e9bf1e5 41: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 224f4eed1 42: onsuccess: 1: Successful build after binutils: Automatic [...] new 4ec54a9be 43: onsuccess: 1: Successful build after gcc: Daily bump. new a54a1d766 44: onsuccess: 1: Successful build after gcc: 2 commits new 7be23538c 45: onsuccess: 1: Successful build after binutils/gcc: 4 commits new e9b09167d 46: onsuccess: 1: Successful build after gcc: Daily bump. new 4aa87332f 47: onsuccess: 1: Successful build after binutils: 2 commits new 08157e85c 48: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 8cc25c0c7 49: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 3ea74543b 50: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 47505b717 51: onsuccess: 1: Successful build after binutils/gcc: 8 commits new e73d32d17 52: onsuccess: 1: Successful build after binutils/gcc: 4 commits new f51786772 53: onsuccess: 1: Successful build after binutils/gcc: 7 commits new f092b7f11 54: onsuccess: 1: Successful build after gcc: 7 commits new 7ee719586 55: onsuccess: 1: Successful build after binutils/gcc: 4 commits new fa2adbe31 56: onsuccess: 1: Successful build after gcc: Daily bump. new 829569c57 57: onsuccess: 1: Successful build after binutils/gcc: 9 commits new 7e02f7f33 58: onsuccess: 1: Successful build after binutils: 2 commits new 961636341 59: onsuccess: 1: Successful build after binutils/gcc: 25 commits new 37565fa4b 60: onsuccess: 1: Successful build after binutils/gcc: 3 commits new ec4928174 61: onsuccess: 1: Successful build after binutils/gcc: 14 commits new 73851f566 62: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 6bb7a894e 63: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 407f9d298 64: onsuccess: 1: Successful build after gcc: 5 commits new 429abae05 65: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 0a18764a6 66: onsuccess: 1: Successful build after binutils/gcc: 10 commits new 796be2f24 67: onsuccess: 1: Successful build after binutils/gcc: 6 commits new 338e9536d 68: onsuccess: 1: Successful build after binutils/gcc: 3 commits new 3893904c5 69: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new e23766d2d 70: onsuccess: 1: Successful build after gcc: libstdc++: Add [...] new 1199c0868 71: onsuccess: 1: Successful build after binutils/gcc: 2 commits new 6d058c928 72: onsuccess: 1: Successful build after gcc: 2 commits new 198ce729d 73: onsuccess: 1: Successful build after binutils: PR29494 Tr [...] new 5dd6167dc 74: onsuccess: 1: Successful build after binutils: Automatic [...] new 98190835b 75: onsuccess: 1: Successful build after binutils/gcc: 18 commits new 350b86916 76: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 5a714a21e 77: onsuccess: 1: Successful build after binutils/gcc: 23 commits new 21a00d7f6 78: onsuccess: 1: Successful build after binutils/gcc: 5 commits new 59126a72e 79: onsuccess: 1: Successful build after gcc: Daily bump. new 8e858f21c 80: onsuccess: 1: Success after binutils/gcc: 14 commits new 9ba9518f2 81: onsuccess: 1: Success after binutils/gcc: 27 commits new 7932b9660 82: onsuccess: 1: Success after binutils/gcc: 10 commits new 742796451 83: onsuccess: 1: Success after gcc: 8 commits new 1900d7322 84: onsuccess: 1: Success after binutils/gcc: 9 commits new b96fc9817 85: onsuccess: 1: Success after binutils/gcc: 9 commits new ed0f86de9 86: onsuccess: 1: Success after binutils/gcc: 13 commits new ceb1def29 87: onsuccess: 1: Success after binutils/gcc: 4 commits new b36357f15 88: onsuccess: 1: Success after binutils/gcc: 16 commits new 216f545aa 89: onsuccess: 1: Success after binutils/gcc: 9 commits new 36c37635b 90: onsuccess: 1: Success after binutils/gcc: 6 commits new 39518eff3 91: onsuccess: 1: Success after gcc: Daily bump. new c3d7567a8 92: onsuccess: #1965: 1: Success after gcc: 2 commits new 823299095 93: onsuccess: #1966: 1: Success after basepoints/gcc-13-2390 [...] new 1b77eb2c8 94: onsuccess: #1967: 1: Success after binutils/gcc: 2 commits new b740367e1 95: onsuccess: #1968: 1: Success after basepoints/gcc-13-2392 [...] new 96f61e26b 96: onsuccess: #1969: 1: Success after basepoints/gcc-13-2393 [...] new 33a81f32b 97: onsuccess: #1972: 1: Success after binutils/gcc: 7 commits new 66572e40c 98: onsuccess: #1973: 1: Success after binutils/gcc: 36 commits new 66aed1d34 99: onsuccess: #1974: 1: Success after gcc: 14 commits new 73a5c0b5c 100: onsuccess: #1975: 1: Success after binutils/gcc: 6 commits new 7232a5712 101: onsuccess: #2018: 1: Success after binutils/gcc: 336 commits new e446a4b40 102: onsuccess: #2019: 1: Success after basepoints/gcc-13-270 [...] new 2436e2b23 103: onsuccess: #2020: 1: Success after gcc: 2 commits new 13e669a60 104: onsuccess: #2021: 1: Success after binutils/gcc: 2 commits new 798456afa 105: onsuccess: #2022: 1: Success after gcc: 4 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (177699aff) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1668 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 37912 -> 37232 bytes 04-build_abe-gcc/console.log.xz | Bin 212572 -> 212772 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3880 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2404 -> 2548 bytes 07-check_regression/console.log.xz | Bin 4168 -> 4188 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 22 +- 07-check_regression/results.compare | 9 +- 07-check_regression/results.compare2 | 50 +- 07-check_regression/results.regressions | 27 - 08-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 27 - sumfiles/g++.log.xz | Bin 3546288 -> 3584284 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 3103168 -> 3094300 bytes sumfiles/gcc.sum | 4642 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037452 -> 1032300 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2192 -> 2192 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 206836 -> 207036 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2548 -> 2544 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 450076 -> 448908 bytes sumfiles/libstdc++.sum | 4 +- 35 files changed, 2432 insertions(+), 2489 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022