Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[gcc] branch master updated (328477f6ee8 -> be6195c7e7a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 328477f6ee8 d: Merge upstream dmd, druntime 5f7552bb28, phobos 67a47cf39. new be6195c7e7a gdbhooks: Update gdbhooks.py for recent tree_code_type chan [...] 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: gcc/gdbhooks.py | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig updated (786a1bdf16a -> bfb2fb05cc9)

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/llvm-master-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from 786a1bdf16a 57: onsuccess: #5: boot: Success after binutils/llvm/linux/ [...] new bfb2fb05cc9 58: onsuccess: #6: boot: Success after binutils/llvm/linux/ [...] 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 1756 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2460 bytes 03-build_abe-binutils/console.log.xz | Bin 30648 -> 27112 bytes 04-build_kernel_llvm/console.log.xz | Bin 64868 -> 64420 bytes 05-build_abe-qemu/console.log.xz | Bin 32040 -> 32160 bytes 06-build_linux/console.log.xz | Bin 3936 -> 3044 bytes 07-boot_linux/console.log.xz | Bin 5660 -> 5668 bytes 08-check_regression/console.log.xz | Bin 4240 -> 4320 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (10af7021706 -> c459b4fb6f5)

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_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards 10af7021706 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 51397ec318e 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 029e4c50123 212: force: #24: 1: Success after binutils: 2 commits discards 422a8110028 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 595626e4046 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 4655373d4ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b59bf7e7fb2 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 02e6c41e4e9 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 98480832c40 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 25ceb198cb0 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1dfc5763c8a 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4990dba3071 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 62af3970cc6 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0545660e7c3 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fc0a01f06c7 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2a66b34169c 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 01c82984de5 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 98116901bd4 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 84338d1f2f9 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ebc2e4101e1 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0e1bc8cdb21 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards c10ad2513d4 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5011984f696 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 78dc008778b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2ad0b45ad72 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards cbf164bb953 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 08b7881805e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 87cd0daf3d5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 6f4557cc609 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 1c901da95e3 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards be9483c5644 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 711b42693eb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards b8db38d209e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards db641d84680 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 3446a2c0d56 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 92e35330638 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards edcfba747d2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 51586a0e3fd 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 96609513715 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 7054587238f 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 4123f8b6d89 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 5f1ae993473 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 999a2b828cf 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards df09fd47fb7 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 50533a902bf 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 2fbb1a5dbb1 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 61adeb07a58 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 8d574b66c43 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards c7cb3d6ba68 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards b1f45623c67 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards e0c417c45fc 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 0c828908b6e 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 68818eb0709 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 6472f74f6a4 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards ebb4cb9ecb1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 92a4d3d72d5 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 80e5a0e3519 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 2d29cfd88e8 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards aa28f4e6df3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 840875f9ed1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 98a5fdb37ca 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 241db191392 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 9df74fae9e3 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards c4eecca5a25 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 025066de901 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 6de25999706 149: onsuccess: #684: 1: Success after linux: 10 commits discards d13c53793ca 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 24ff4229145 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 37362cddc4e 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 0939ce19f13 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards c8624b7c189 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards f942ee68ffb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards efde725deef 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 3d6808ef56f 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 8917d998c9c 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 73c586ab2b9 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 2a220907f78 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 5a4c0426760 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards b502bb4a675 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards c126d951bf1 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 09883fd08ca 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards c95d71d0cea 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 1709654920d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 02a3d0c6347 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards a4fdf8810db 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 70314b7896f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4f4045c3234 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards e5bcf0caa2d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards f887834bf07 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2514ca68eba 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 5e0d4912681 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 2c17786d4a5 123: onsuccess: #655: 1: Success after binutils: 22 commits discards db82c4e0beb 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards bbb78ad2b9b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards dc7c60a85d0 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 4aed62677a9 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a6dda4a5edf 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards a0c178f20cc 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 9a76600bffe 116: onsuccess: #647: 1: Success after linux: 3 commits discards f36c41967a8 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 90e3e1bca60 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 8b967671f11 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 902964da244 115: onsuccess: #645: 1: Success after binutils: 27 commits new 24b978de2d5 116: onsuccess: #647: 1: Success after linux: 3 commits new b0fc93ea0b2 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 54ef4d59eb7 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 11c8c7851dc 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new b3ff1c3c697 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new cf1219267c5 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e6494150c6a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new b2524b3874c 123: onsuccess: #655: 1: Success after binutils: 22 commits new 47a532a660a 124: onsuccess: #657: 1: Success after glibc: 2 commits new 2b27443b679 125: onsuccess: #658: 1: Success after linux: 3224 commits new 9c5d1b9424c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new ef4c07b4bf4 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new dc6541fa0c8 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 2edb0c052f5 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 298d0121654 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new accd651ffa2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 59589fc9293 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 4d9a62fd88b 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 0762836f758 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 1d2280c978b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new a447774885b 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 15a95c0a347 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 7fbb464ba01 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2e3b8d5f038 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 00980a7714d 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new e3d9e7f0c33 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 636bec12a25 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 31cbb15b108 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3e19522a6f1 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 14f4c063571 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ac9e7bd8e5f 146: onsuccess: #680: 1: Success after binutils: 20 commits new 25582d0b195 147: onsuccess: #681: 1: Success after gcc: 6 commits new e36f8df7b75 148: onsuccess: #683: 1: Success after glibc: 9 commits new 2cf5d7eba13 149: onsuccess: #684: 1: Success after linux: 10 commits new 7aa0c7ff8e8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 5caddf4147f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 4d094efde5a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 21ee9f4bfe7 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 12235e55120 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 7bdf75386d1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 74d88e81b32 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 11e58819994 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new ab5e46f56c5 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 6196cab5412 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 12edf85618e 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new f6029a60931 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 29c267be1ff 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new aaafb40c35c 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new cb7cb33a828 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 6b7a2a1e7e1 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new f804561ca47 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new bcee8e7b98f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 7c3f6d485e6 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 972ed9f802a 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 88e107e419f 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 71eb28fb3e0 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 433dde68f51 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 1e9decbc0d0 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 3f2d827d5d5 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 071f4d2c5ff 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 4390b0b0f36 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 09827205208 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new bf6fa23ed1c 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 78c0c25c4dc 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 27bcfd31dd3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new a1c985be215 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 878a6cd01fa 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 75e6f69b3a8 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 5215bd66be4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 6a950e037fb 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new e5d3b5b6f9c 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new b07df5c16b0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 2bbc082b7ef 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new af2403a5e0e 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 18397b4495f 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new c4a4996ad30 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 96a8426ba28 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new b9d95ce39a7 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 70329e876c6 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4e240e92ffb 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f5497bf9154 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 03d2591ce2f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9ce6a8bcb67 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2da2dcb0c75 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 040edc30327 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7110150466c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7343923cb5e 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 66931a8e776 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new e39ad4764ee 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4235efd8dfc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new d95f81906db 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 93093f2d492 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 4d07001bc26 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 17a9967c43f 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 84e0a27938d 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 44026fc43fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new d4300a610a1 212: force: #24: 1: Success after binutils: 2 commits new fd0fc4e2cce 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 5192d0e05f5 214: onsuccess: #26: 1: Success after binutils: 12 commits new c459b4fb6f5 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] 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 (10af7021706) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 2036 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 3448 -> 2484 bytes 03-build_abe-binutils/console.log.xz | Bin 39312 -> 34944 bytes 04-build_abe-gcc/console.log.xz | Bin 203992 -> 202768 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 243896 -> 242160 bytes 08-build_abe-gdb/console.log.xz | Bin 38992 -> 34664 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3784 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2652 -> 2100 bytes 11-check_regression/console.log.xz | Bin 3592 -> 5092 bytes 11-check_regression/mail-body.txt | 19 -------------- 11-check_regression/results.compare | 19 ++++++++++++-- 11-check_regression/results.compare2 | 21 ++++++++++----- 12-update_baseline/console.log | 40 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 21 +-------------- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++----------- sumfiles/binutils.log.xz | Bin 62888 -> 63136 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83976 -> 83972 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122464 -> 122400 bytes sumfiles/ld.sum | 13 +++++----- 29 files changed, 89 insertions(+), 98 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (3947a30d871 -> 3402b201e29)

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 3947a30d871 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 4bfde90a5e6 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] discards 7dc5cadf830 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] discards f541da58b05 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards b116961331e 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 41f5281fb85 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 72c393aacc2 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards e947cc070e0 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 931e77a625a 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a1a587ca6b8 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards efa3031c75c 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards d0a9f801d63 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards f4838449a58 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards 4a7cda7a091 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7cffc3262c3 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 106a9a9f295 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards e746f903f97 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards f25f9ca7ce1 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 6622e98990f 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a6dc938e736 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards baf1b993bd2 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards c41eac3b31c 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c6120311104 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 728f65a0034 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards 89e95c544a5 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards df8b3c265a3 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 85929d437c5 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards 1ac519dd601 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 8f5793f90c2 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards f0e26db3cdd 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards d14ae31f526 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards af2558073d1 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards f265fc09de4 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 2cc62a1f356 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards ac20b20c6b0 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 9f4b3a09a00 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 3ba766e0857 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards 245bfdfd465 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards fde1869c3ab 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards 34c00aad3f4 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards b16c3acfb6d 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards 736508b4b9a 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 53dc9213447 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 2d55e7a36df 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards aae9f9137bd 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards f8c5d32236d 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 947feb8f2a9 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards edc57d36a22 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards fc03cdb9441 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards 952484c6ba8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards 3bd58639e6f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards b13a192cddb 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards 3f106318d51 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards 43fb810f2a6 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 213c8842efa 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards eef2056205d 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards 451e5d9e4b7 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards ac5cd45601f 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards b5803d76da4 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards ce94a86a318 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards 4b540753fb7 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards d54e164dccc 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards a896bc1473b 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 2390a9eb743 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards f760f3f0f78 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards d17c4c6af90 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards d02f625dd5c 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards 509ea060350 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards f76130bd7ed 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards 3cea1afd6c0 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards bdd7fa7ca55 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards a70ee95df6f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards e1cc6006bcd 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards a22d8460496 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards c0ccfe9b8c6 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 2170624c7ed 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 3752e53caec 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 3e37b4311bf 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards 14b6c4b1f2e 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards bc570f37aea 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards e5661ba76ff 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards 4093f80f40f 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 45eebcd5174 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards d3b4d949db6 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 4fbe149462b 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards c4e9ffd3131 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards c428d3060b2 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 17c88f400a3 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 414e149ae6f 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards c5c2ea4bbca 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards 9b7742e1612 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards acdc9d944f0 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] discards 36d69ebd8ed 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards d83d611e115 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] discards 3993dcf9e2f 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] discards 83fdaeb8b64 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards ac0b59e152c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] discards 32609e2182d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] discards d8add8eabf9 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] discards 349ee529a83 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] discards 45ddc9cb52b 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] new 2fef677fead 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] new c5f7e6aaa21 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] new 8a73008911d 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] new 9f693dc3a38 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] new 444714860b4 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] new 99ca42f6745 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 94421f41003 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] new 2fdcf75a973 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new 42c1f87f107 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 6eb0bed51c8 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new ccd50aeb886 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new 6045456d538 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new 582ab70e1d3 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new a98d0567f6a 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 27b98e133d7 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new 2fb3b6dd05d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new 9f3319ae7a3 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new f2a1b2f20a6 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new afb656cd510 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new 643870ca75b 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 0ce396cadc1 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new a179a926fc4 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 54006d24ba6 387: onsuccess: #2208: 1: Success after gcc: 2 commits new c9dc6368382 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new 1686b854f9f 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 9ae13ec0fc5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 16257966e98 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new 6ac4e1a1ef2 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new 698b2a029b5 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new 2faecf6624d 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new 03178fae6ff 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new 52ff8540210 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new ff30202243e 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new 63c6989bfb3 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new e0a49119e04 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new 7cdce7226e1 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new fa8a42eec65 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new 8a865254f4e 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new 551a74592e7 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new 2b7e02fc725 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new d081034a636 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new ee50f02bcaa 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new 55c3e3538cd 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new 0fc71e9511c 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new df139018581 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new 9e424b0d0db 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new e803a17d202 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 2814199e910 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new 0875dcb1e15 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new d66f1bc438d 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new 4f73a78c754 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new 347d8f356b8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new 9ea7a920686 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new 49d74cca76a 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new f09e49a5794 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new 5561b13e462 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 4eb5175d527 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new 6dec9f3943e 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 195414b27cf 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 6714b36374c 424: onsuccess: #2248: 1: Success after gcc: 6 commits new c4d415691f4 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new a36d00469f1 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new d053e7da1a2 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 24af5b70f13 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new a7f53a6d274 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 27b6f7eb852 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new ffefaea6e11 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new fe1cfda1cab 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new c53e51fd16d 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new d97de105af5 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 607f8afc8ce 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new ba459a6dd29 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 7826c71020c 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new 9885b4e7698 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new b43ba2e1210 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new cd7d14666ec 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new c2ddfc81e8e 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new 9bdf43384e9 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new c56ddc784bd 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 8187061edc4 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c03a1491998 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 0a54501e041 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 097fb9bfed8 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c36a0657e43 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new dbb54ba18fb 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 39e0ba66183 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 69090c3bc8c 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b8dcd02d3e1 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new d1307b0aea3 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new c515c6ce087 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new be490011997 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 5cbdbe34a80 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 620fb7f0fb2 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new e9b7d68a121 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a1ade3939c0 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new dd7dfee23a5 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 512d37cac5c 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 9d2f2c1d573 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new dd16ebf1987 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] new 0f975c892d9 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] new 886a4088711 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 3402b201e29 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] 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 (3947a30d871) \ 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 1760 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 3496 -> 2576 bytes 03-build_abe-binutils/console.log.xz | Bin 31080 -> 27140 bytes 04-build_abe-stage1/console.log.xz | Bin 89832 -> 88972 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 236356 -> 234460 bytes 08-build_abe-stage2/console.log.xz | Bin 225616 -> 225196 bytes 09-build_abe-gdb/console.log.xz | Bin 38908 -> 34704 bytes 10-build_abe-qemu/console.log.xz | Bin 30592 -> 31628 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 7032 -> 6380 bytes 13-check_regression/console.log.xz | Bin 6916 -> 6384 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 13 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 28 +- 13-check_regression/results.compare2 | 242 +- 13-check_regression/results.regressions | 33 - 14-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 33 - sumfiles/g++.log.sep.xz | Bin 105984 -> 187320 bytes sumfiles/g++.log.xz | Bin 2661440 -> 2659892 bytes sumfiles/g++.sum | 153 +- sumfiles/g++.sum.sep | 11776 +----------------------------- sumfiles/gcc.log.sep.xz | Bin 128976 -> 120360 bytes sumfiles/gcc.log.xz | Bin 2237668 -> 2222280 bytes sumfiles/gcc.sum | 351 +- sumfiles/gcc.sum.sep | 1659 ++--- sumfiles/gfortran.log.sep.xz | Bin 30144 -> 49228 bytes sumfiles/gfortran.log.xz | Bin 900008 -> 897084 bytes sumfiles/gfortran.sum | 38 +- sumfiles/gfortran.sum.sep | 4572 +++++++----- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 217228 -> 217292 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.sep.xz | Bin 14228 -> 16424 bytes sumfiles/libstdc++.log.xz | Bin 446452 -> 440168 bytes sumfiles/libstdc++.sum | 18 +- sumfiles/libstdc++.sum.sep | 737 +- 52 files changed, 4464 insertions(+), 15410 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig updated (86ef68eb15e -> d7365c170d9)

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/llvm-master-arm-next-allyesconfig in repository toolchain/ci/base-artifacts. from 86ef68eb15e 86: onsuccess: #12: 21023: Success after linux: 2636 commits new d7365c170d9 87: onsuccess: #13: 21042: Success after binutils/llvm/linu [...] 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 1712 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2464 bytes 03-build_abe-binutils/console.log.xz | Bin 30700 -> 26760 bytes 04-build_kernel_llvm/console.log.xz | Bin 64256 -> 63984 bytes 05-build_abe-qemu/console.log.xz | Bin 30960 -> 31060 bytes 06-build_linux/console.log.xz | Bin 3656 -> 3612 bytes 08-check_regression/console.log.xz | Bin 3132 -> 4468 bytes 08-check_regression/mail-body.txt | 22 +++++++++++----------- 08-check_regression/results.regressions | 10 ---------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 24 ++++++++++++------------ mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 12 +----------- 19 files changed, 48 insertions(+), 65 deletions(-) delete mode 100644 08-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O2 updated (f70c0473bb0 -> 830c27f46cf)

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-code_speed-spec2k6/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from f70c0473bb0 68: onsuccess: #6: 1: [TCWG CI] 456.hmmer speeds up by -4% [...] new 830c27f46cf 69: onsuccess: #8: 1: [TCWG CI] No change after binutils/gl [...] 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 1940 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2864 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 30976 -> 27752 bytes 04-build_abe-stage1/console.log.xz | Bin 72580 -> 72696 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 245196 -> 243168 bytes 08-build_abe-stage2/console.log.xz | Bin 177808 -> 177324 bytes 09-benchmark/benchmark-build.log | 184 +- 09-benchmark/benchmark.log | 182 +- 09-benchmark/console.log.xz | Bin 4172 -> 4096 bytes 10-check_regression/453.povray.symbols-skipped | 1 - 10-check_regression/481.wrf.symbols-skipped | 1 + .../compare-results-vs-first-internal.csv | 244 +- .../compare-results-vs-prev-internal.csv | 256 +- 10-check_regression/console.log.xz | Bin 15456 -> 16280 bytes .../csv-results-vs-first-0/md5sum.csv | 1956 +- .../csv-results-vs-first-0/results.csv | 666124 +++++++-------- .../csv-results-vs-first-0/size.csv | 667928 +++++++-------- 10-check_regression/csv-results-vs-first-0/sve.csv | 27978 +- .../csv-results-vs-first-0/vect.csv | 356 +- .../csv-results-vs-first-1/md5sum.csv | 2874 +- .../csv-results-vs-first-1/perf.csv | 3310 +- .../csv-results-vs-first-1/results.csv | 773186 ++++++++--------- .../csv-results-vs-first-1/size.csv | 776289 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 28894 +- .../csv-results-vs-first-1/vect.csv | 458 +- .../csv-results-vs-prev-0/md5sum.csv | 3089 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3302 +- .../csv-results-vs-prev-0/results.csv | 743465 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 746576 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 28966 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 504 +- .../csv-results-vs-prev-1/md5sum.csv | 2874 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3310 +- .../csv-results-vs-prev-1/results.csv | 773186 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 776289 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 28894 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 458 +- 10-check_regression/exe.improvement | 1 - 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/jira-body.txt | 3 - 10-check_regression/mail-body.txt | 3 - 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/error_code-1 | 0 .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/symbol.regression | 1 + .../output-bmk-results/symbol.regression.diff | 1 + 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3131 +- 10-check_regression/results-vs-first-internal.csv | 248 +- 10-check_regression/results-vs-first.csv | 248 +- 10-check_regression/results-vs-first.log | 1386 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 10 +- 10-check_regression/results-vs-prev-full.csv | 3411 +- 10-check_regression/results-vs-prev-internal.csv | 256 +- 10-check_regression/results-vs-prev.csv | 256 +- 10-check_regression/results-vs-prev.log | 1616 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 12 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 12 +- .../squad-vs-first/403.gcc/results-metadata.json | 12 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 12 +- .../416.gamess/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metadata.json | 12 +- .../squad-vs-first/433.milc/results-metadata.json | 12 +- .../434.zeusmp/results-metadata.json | 12 +- .../435.gromacs/results-metadata.json | 12 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 12 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 12 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 12 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 12 +- .../447.dealII/results-metadata.json | 12 +- .../450.soplex/results-metadata.json | 12 +- .../453.povray/results-metadata.json | 12 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 12 +- .../squad-vs-first/456.hmmer/results-metadata.json | 12 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 12 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 12 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 12 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 12 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 12 +- .../squad-vs-first/470.lbm/results-metadata.json | 12 +- .../471.omnetpp/results-metadata.json | 12 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 12 +- .../squad-vs-first/481.wrf/results-metadata.json | 12 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 12 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 12 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 128 +- dashboard/squad-vs-first/summary-annotation.txt | 1 - git/binutils_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 35 +- mail/mail-body.txt | 35 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results_id | 2 +- 115 files changed, 3100042 insertions(+), 2972435 deletions(-) delete mode 100644 10-check_regression/453.povray.symbols-skipped create mode 100644 10-check_regression/481.wrf.symbols-skipped delete mode 100644 10-check_regression/exe.improvement delete mode 100644 10-check_regression/output-bmk-results/error_code-1 create mode 100644 10-check_regression/output-bmk-results/symbol.regression -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig updated (5dbe570ba9f -> 5c0a3e106cc)

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/llvm-master-aarch64-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 5dbe570ba9f 51: onsuccess: #5: boot: Success after binutils/llvm/linux/ [...] new 5c0a3e106cc 52: onsuccess: #6: boot: Success after binutils/llvm/linux/ [...] 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 1768 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2544 bytes 03-build_abe-binutils/console.log.xz | Bin 30848 -> 27244 bytes 04-build_kernel_llvm/console.log.xz | Bin 65364 -> 67712 bytes 05-build_abe-qemu/console.log.xz | Bin 31144 -> 32340 bytes 06-build_linux/console.log.xz | Bin 2984 -> 2936 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4224 -> 4320 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 33 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig updated (db3e33aa888 -> e27b55cc358)

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-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from db3e33aa888 48: onsuccess: #5: all: Success after binutils/gcc/linux/qe [...] new e27b55cc358 49: onsuccess: #6: all: Success after binutils/gcc/linux/qe [...] 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 1748 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 30644 -> 26844 bytes 04-build_abe-stage1/console.log.xz | Bin 89184 -> 88620 bytes 05-build_abe-qemu/console.log.xz | Bin 31000 -> 30376 bytes 06-build_linux/console.log.xz | Bin 4040 -> 3924 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4200 -> 4320 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 9 --------- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 20 files changed, 27 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (3f3e618421f -> c7a9a1e93df)

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_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 3f3e618421f 212: force: #27: : Failure after baseline build: no new commits discards c0e6bc41486 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0d0957742da 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 621bc209147 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 108b33b93d9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 3fd27b061dc 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards ca7f695c5cc 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9b3a6924392 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1e1d6b1259b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cdaa087258b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fa735011e21 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a03187fa5f1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ba0cd1577a3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 5fb219eca55 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 88c2b1dd704 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 52d529c6bb3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d1b8bd70805 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 6521d1cbd35 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 4be37f278e6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 5224a4a8ed1 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards a68d53bb77e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 3c8cff479bf 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards f4688a1c0ce 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 0ecae54e53d 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards beabba48ea7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards e4a5dbc7ff4 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 3dcdfa77a50 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 2db0aa2f90c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 27b1cdb8dee 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 2425c1d3949 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 9f3275a0951 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 8ae7e1bd613 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards f8cf8f8bdde 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 105edc34498 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards a6d2e7da3f1 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a469757b724 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 591cf91d670 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards f5fad975d7d 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 6caab166679 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 2748d9befba 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards d3d566c70d9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 206d1d1f0c7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards fb3857e859f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards c51b332f020 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 7920d61bd72 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4c115ffc0e7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards f786d33352b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9acb487c76f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2fbcf8ce413 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 50e9c4fae57 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 049bdebaea8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 025f9d5c8a2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 3a89da45f25 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards b515fa0ef23 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards aa50b389acb 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 002e5f6da7b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards afbf343bf88 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b15baf0f1d8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards b4050b1cff0 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 39e0837eb4c 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards d3d114d5370 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 9fe19be7d72 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 2b9ad1e6c64 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 4c653d9b665 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 5d066f9b194 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards b008e2acdf3 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 7bf955523d6 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards ae3500a9799 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 9d00eec9dc2 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 7d9388ccda9 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 323cf72d116 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 4b3a9d6a78d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards bb8d211a465 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards e049ed6f2de 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 28c8507f050 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards edc5ea91c0f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards f6af779a06e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 30052c5e450 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards c13aa8c4850 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards b5d673e9283 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 60b80417284 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 0a86091fe36 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a66cb6f5f17 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards dd6f401e943 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 39fb1ba27de 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 76d602248d3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards e4276f24cbe 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 11f664acf87 125: onsuccess: #614: 1: Success after linux: 12 commits discards bc7241e12a5 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 2ec9e63e0cb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 04b4eb34bc1 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 50520d08ed4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 362095951f9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 4c345492d37 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 36989457128 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards b775f7bebe5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards cb9012d3ce3 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 6e5628faf95 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 2b69c8a4ff1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards d6a1c8c2eb0 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 3de94cbbe73 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 7605120b1a0 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new a5c6ace0201 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 3764eabb360 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new a8bf816de35 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new b9e79a01ae6 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new b47c4eb8804 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 2a3e518e546 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new ad7dcfa9562 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 687f74aecf9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new b952d75cf48 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 547e0bcb7a6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 82ab3569b48 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new c5d30ba3ba0 124: onsuccess: #612: 1: Success after binutils: 18 commits new 247f3226efd 125: onsuccess: #614: 1: Success after linux: 12 commits new ce3ab4c50e5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b6bc0c87a5f 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e00d79ffb37 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 482c3fda64d 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new f17ba0c4bfc 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 5fdc56251f3 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new db3658805fb 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 6adc19b5c68 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new ed919065905 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 03dcc80a50a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new b6d5ca7cb1a 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new d3c1ac52cfd 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new b87f406018d 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new f45cffb766f 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c3caa69c4a5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new de26541bfd5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new c58fc1fa257 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 09b2e47f935 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 7b0297a51a1 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 59ac70b1158 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 7962867e53f 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 0985375defe 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new d5fbed22ae6 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4f1db502acb 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 61b8403248d 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new daf14d5c8b7 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4825837ebd1 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 4dc1e22d43b 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 1836b0f0026 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 5267e68ba6c 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 41ec8d1abff 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 732af35775b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 48a5ccaeca9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 459e4b590c7 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new bc29733c75d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 85f81b66d62 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 77ea73703b6 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new dc88531c7db 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new e0d5a6fa056 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 8616588729a 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 5936d098563 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 1cf277552a5 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new f6bbe07cab2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 1f8a6c5f3b7 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 853f732d924 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new fd574bd8c58 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 9698fa494e0 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 5d9b5e2abc8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 8aa0e25fd40 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 603fe4d38f8 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 42bd1a77ae0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new ae49b4023af 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 493e1f0c6a6 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 8216d13d994 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new a90d3c6f5e7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 64956667714 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 6c3cd268238 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new e41c1044aea 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new a2df8bec62b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new abf5cbe5766 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 1ec26b89439 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new f99b2971a4f 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 8471b105b65 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 680f602e556 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 4493354ec97 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new adc40b51e6a 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new ba04da506a5 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 9548071fdb2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a8610336b33 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ecf18b6c16c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1b8247508eb 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e855a2db69a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d399fcafed1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 84c8f909092 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 99b9f0667ac 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 01d24c12448 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0795d7971b9 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 80b6dd1520f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c540f53224e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new cdaec2e3782 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 5de8d3bb7ad 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new ac6f74b0b58 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0be96fcce1c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 6b8c7ea305d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1f6156a8c5f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 5a3f8f1daaa 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new aaec93ffbb9 212: force: #27: : Failure after baseline build: no new commits new c7a9a1e93df 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] 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 (3f3e618421f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 1724 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 3444 -> 2452 bytes 03-build_abe-binutils/console.log.xz | Bin 52668 -> 48356 bytes 04-build_abe-gcc/console.log.xz | Bin 236000 -> 236520 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9236 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 235808 -> 233108 bytes 08-build_abe-gdb/console.log.xz | Bin 50308 -> 47420 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1052 -> 4248 bytes 11-check_regression/console.log.xz | Bin 2504 -> 4072 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 66 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.regressions | 2 - 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 66 +- mail/mail-subject.txt | 2 +- manifest.sh | 33 +- results | 4 +- sumfiles/gdb.log.0.xz | Bin 0 -> 2932132 bytes sumfiles/gdb.log.1.xz | Bin 0 -> 143088 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 16976 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 14948 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 10396 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10256 bytes sumfiles/gdb.sum | 99688 ++++++++++++++++++++++++++++++ sumfiles/gdb.sum.0 | 99684 +++++++++++++++++++++++++++++ sumfiles/gdb.sum.1 | 8554 +++ sumfiles/gdb.sum.2 | 2349 + sumfiles/gdb.sum.3 | 2361 + sumfiles/gdb.sum.4 | 2197 + sumfiles/gdb.sum.5 | 2174 + 39 files changed, 217065 insertions(+), 169 deletions(-) delete mode 100644 11-check_regression/results.regressions create mode 100644 sumfiles/gdb.log.0.xz create mode 100644 sumfiles/gdb.log.1.xz create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/gdb.sum.0 create mode 100644 sumfiles/gdb.sum.1 create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3 create mode 100644 sumfiles/gdb.sum.4 create mode 100644 sumfiles/gdb.sum.5 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/bmk-scripts] branch master updated (66c3424 -> 4051664)

by Prathamesh Kulkarni

This is an automated email from the git hooks/post-receive script. "Prathamesh Kulkarni pushed a change to branch master in repository toolchain/bmk-scripts. from 66c3424 Skip calculating size if exe is not found. new 4051664 Adjust exe check in metric scripts. 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: md5sum-data-to-csv.py | 2 +- sve-data-to-csv.py | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023