Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (9ff6a2cdf126 -> 281d6c0a9c85)

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_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 9ff6a2cdf126 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] discards 9316b970b76d 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] discards ebfa295c5fe3 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] discards 81be1675f0a1 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] discards 6865847167f5 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] discards 6c2eb02f5633 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards f53fa94c5f15 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 5361c80613a9 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards f784f8dc3d73 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards dff9b3e24c16 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards cdb27105d742 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 20018b238fbe 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards d2e57b059625 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards b0696ff1cf7f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards 5826f868fce2 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 21b3b39f63df 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards b15edfe9a72e 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards f9af6060dc15 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 254e394333ae 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 62873ed102d5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 8ce047c6be87 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 3e9947452064 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards b3048c5a573d 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards e6678847a063 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards b375c2c09733 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] discards 2076faf1b77b 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 66068892f583 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards e1c017924ec1 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 44f33222c78e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 5130d11eec74 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 5bc54c3fea3d 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] discards 6964dc79a1c8 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards e6cf2f5b9d5a 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards de05f906ae0a 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 5cd686176dd8 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 856e2692e5d2 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards 95025624d3a0 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 2c3d8b91d4ad 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 34349a8c2669 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards f522bb3c8c05 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 4cb99455f32c 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards dd1608d3d398 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 370f3f17ad55 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards 67811d59c0cc 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards b1ddbb4bcec3 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 6085418c2807 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards 42ca3f7a20d0 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards db0e3c070ef5 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 444e298d0ce5 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards a9eeec541ebb 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 0a058fda20df 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards b5436609f25e 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 56ebe13d295d 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards a4e2558a045d 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] discards 0b0469ef5b1a 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] discards 55b49eab210d 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] discards d0ce75f1eb1f 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 4083ef97717a 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 41b2aaf0d9ee 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 69dd74323e3d 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards df705ecc8c05 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards 3a3d55c83161 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards e959dcc7aa56 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 8020776dce3b 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 728a4752d5af 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards f8b69c86c994 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards 05754ceb0618 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] discards cfe39c2d22db 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] discards 54c56beef9bd 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards dfdbd160487f 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards 87c23896e118 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] discards 32c859391656 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] discards e72b2dc39efa 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 8ecc9b1bb094 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 97f7148d90da 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] discards 12fd9debe61a 162: onsuccess: #624: 1: Success after linux: 10 commits discards d91a7061a6d9 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 5fe9612e948f 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 8503cbed069f 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 5a5f96810b7c 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards ad10a39ad53b 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards f05592b411a6 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards c4a32542cf99 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 388512196900 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] discards 697d0fe1b5af 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] discards 7268db4325ed 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] discards 88739cfcfa89 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards 63c66ecb50a8 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 522062ee744b 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 2b88d24c41f1 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards fb0688a7a48a 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards c52624f58788 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 5c7290e8d10e 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 3f476a033ca0 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] discards 186b39c00361 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards feff4b23e899 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 42ad1245ae88 141: onsuccess: #601: 1: Success after linux: 794 commits discards 3062de824261 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 627776f3b8df 139: onsuccess: #599: 1: Success after binutils: 10 commits discards ec0366370745 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards e8f71f617d1b 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new b07ff2ff7dbf 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 5abcc17ff3a8 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 51928e8837a0 139: onsuccess: #599: 1: Success after binutils: 10 commits new 90f8d6264b24 140: onsuccess: #600: 1: Success after gcc: 23 commits new b6b278e893c0 141: onsuccess: #601: 1: Success after linux: 794 commits new 229c73b78294 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 086347b78658 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new afda512ca918 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] new eec9eed36daa 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new a4116ad4803e 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new a5016540e81f 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 8d7d6da2d764 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new b0852e6caecb 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new e36f1d2476bf 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 24c6edc799fd 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new f5fb9fceeef2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] new 39a674153021 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] new 743ff2cdfceb 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] new 4e6a9cac486d 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new f3df8debfd93 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 41de6a6dc0d6 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new 36fe5154b0d1 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new c5d10ae6cf5c 159: onsuccess: #620: 1: Success after binutils: 12 commits new 06b7d82180e1 160: onsuccess: #621: 1: Success after gcc: 11 commits new 92edcd31a831 161: onsuccess: #623: 1: Success after glibc: 9 commits new 71c49f1ae21f 162: onsuccess: #624: 1: Success after linux: 10 commits new 56eac4205dca 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] new 534092f48a3c 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new f1c865ce1690 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new b470cef25505 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] new 73ccab0486de 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] new 3e58b1e46c20 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new 105cec394dab 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new aae5f05419aa 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] new af15f884eb20 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new b0e64ffe7977 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 07339a924c1a 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new f4aa9b2e12de 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new 5c6e99791eef 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new e0744a06b66c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new e0f6ddee2896 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 4e283910b1c6 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new fe9d7c4da085 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 867889f49372 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new 2ddcb699587b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 9b02643723e6 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] new 8631bd224ce2 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] new fa1d766ca4f5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] new b2709aaf3137 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 8e88a5418ebd 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new 33ea5c845268 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new ca40917bdac8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new dd80fc8d4b93 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new d300643a8f44 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new c4c0fe779795 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 6792ff58174f 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 4401205c1a66 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new 09611b82180d 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new c0054ada3518 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new e7c7162c8de7 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new a01ebb7525fe 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 9223b173843e 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 8bda6a56d43f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 0ca533e0a253 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new a570b2cb174d 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 8946bfd6ccdc 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 567df369b947 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new b91f751eb513 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new 54b3bd309b93 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new dff5c15a1105 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 84aa384858bc 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] new c5637b939a51 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new bda81fe22efd 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 8ee9f8aaadfb 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 89079dc58f12 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new 9d3e4a843bb8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 0c73568e9277 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] new 725af4b86d1c 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 633df806de9b 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new d739db6c525a 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new cbf1c9266384 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 178e50e36c34 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new e6851219b679 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new aa851302e064 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new a4b2825c0488 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 5c2060eb5ee1 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new bd5a6109bfc6 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 4eaf10480a71 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new 240acc2b1c97 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new 01b2415b5d97 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 6597fd4511a4 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new e9f4e013484d 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 6a839b920739 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 2b358235a806 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new b9abf7056a0f 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new b66448123ff2 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new e61ece673f6c 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] new ee0b29ff6880 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] new 76073f841bf7 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] new c4278b350d5e 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] new a60fdfe8ab86 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] new 281d6c0a9c85 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] 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 (9ff6a2cdf126) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 2064 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49664 -> 49236 bytes 04-build_abe-gcc/console.log.xz | Bin 237504 -> 236748 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 231916 -> 232396 bytes 08-build_abe-gdb/console.log.xz | Bin 46884 -> 46364 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10428 -> 9992 bytes 11-check_regression/console.log.xz | Bin 5620 -> 4944 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 5 +- 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 98 +- 11-check_regression/results.regressions | 30 +- 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 27 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +- manifest.sh | 32 +- results | 30 +- sumfiles/g++.log.sep.xz | Bin 62996 -> 79940 bytes sumfiles/g++.log.xz | Bin 2883940 -> 2914596 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 10777 +++++++++++++++++++----------- sumfiles/gcc.log.sep.xz | Bin 68600 -> 81324 bytes sumfiles/gcc.log.xz | Bin 2464312 -> 2472976 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 1296 ++-- sumfiles/gfortran.log.sep.xz | Bin 24808 -> 32308 bytes sumfiles/gfortran.log.xz | Bin 958580 -> 952916 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 3647 ++++++---- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230596 -> 230684 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2700 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 9304 -> 11080 bytes sumfiles/libstdc++.log.xz | Bin 471604 -> 470772 bytes sumfiles/libstdc++.sum.sep | 317 +- 48 files changed, 10229 insertions(+), 6190 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (3a0260dd088b -> 090d160c29f1)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 3a0260dd088b 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 42ef5b1eec74 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 3f634a12f64d 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 262420cf422d 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 5abe5e94da8d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards ac10a69d787b 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards ca3aa4094c8c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards a585f4291ef1 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards b13cbb103eb9 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards d64582126db6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 94c303849a17 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards c5ae9f0c602a 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 9f1d81587bd3 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards bbd8efcd4ba2 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards a90066b12596 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 8883d150a6bd 121: force: #26: : Failure after baseline build: no new commits discards f21d85015bba 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards be57a6026661 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 468200e455e5 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards d4973cfae470 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards d8d39a25e537 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards f5823a263b4e 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards fbb5812f561d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 9e6c0cfdada8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards ebd3be2f63c3 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards abbeaa139bca 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 28f92819bcc1 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards e01100fafedd 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards cbd948eb0b9f 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 5b61886db3ce 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 54e7dbcc6009 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 9c0b5150d1af 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 9ee46aeb8c2d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards ad3614f11ac6 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 776cb2df7fcc 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 9ab4d5b1c3c6 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards a314485e9fe3 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards 744969c5de6b 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 9255be5f7f83 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards acb2deed8cb8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 266438905c74 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards d420fc562d16 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 3e8957e1f249 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 5a757d550088 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 5d1a4e127d2e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards a1eb4bf2cc81 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards ce445ad6ae9d 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards b6824aa1a418 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards 9fe9881b7e21 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 79a398bc3dd9 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 6f395199c317 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards 2d04ae3f81a5 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 897c0142d8f9 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 0cdf06f8db44 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards e6c18c805dc1 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 899e72a588cc 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards fa414d6fdd0a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 9abf8af0cb5e 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 8838f9a7b4f6 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 0f3071fab09a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 2b46f2a50c5f 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards 7d507e156b10 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards 49663542369c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards d8751b7140b9 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 86cdf1bfe0e4 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards 8f30c52244e2 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 29a5dfa7d062 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 75dfa4826efa 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards b6cdda523241 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards a69a361cb67c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 5aab17ca06e4 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards d57265f44a25 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 45b4d25093d4 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards 2f24bead0f9e 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 37edd5f8e5a8 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 4a8c0c07d151 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards a2038a0437c5 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards 09d6c2008caf 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards 7508688ef19c 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards efa960f05332 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards 860a31f69d98 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 55c290792c8f 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards af5206a99db5 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards e2029c206c2b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards c8eab267bb89 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 456953e1b8e6 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 3562a297b9a1 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards ac0acdf2b896 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 429496b8c866 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 5ac3cd28ee45 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 7cfed11a10bc 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards d19d5942481a 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards aad0736264ba 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 450ee8b6c583 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards 5c064bdd5918 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 5b5433ccf0f1 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards da1c3d3267dc 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards ad49c4b14d38 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] discards 82c6ce5dae5a 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] discards 9a44979f765d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] discards 57323ec3b8d6 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gd [...] new 337bdec93794 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gd [...] new 8f901a61295c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new a00d4f4524df 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new b29f14e87431 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 56f491a8e4fd 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new 64eb3bf15963 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new e98c21c1744d 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 4cc16bf36db1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 9d7228c4f430 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 84bdd935f70c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new b7d236506cbd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new ac8e50d5ba11 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 359aad3c43ca 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new e64556752313 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new fdf93d178751 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 3adbe3cb4fae 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 59e47b921042 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new d305690bfa30 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new fb84ced8f401 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 1f3ade66d7c9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new cf92c0b97cd4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new 812d6687691b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new bd47f71c84db 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new 42f8a9689dfb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new 917c731203cf 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new 7874eff2bd28 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new 4aee9cbc08f6 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new 9f5628be5996 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 1aa3cd96b1c5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 66318d8fd972 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new 696dc0cfd616 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 2ea4c8c9151d 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 8b9aefe61e9f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 9bb9f5c26d52 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new 4c30f0137a81 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new ecb28d08a6c4 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new dc51f158258d 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new 07677c0cb618 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 6482dc6a43ea 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new 06e5b083c7bb 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 07e23abf5c6c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new 82419aac2d03 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new 6c78c2c440d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 42daccd496cc 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new adfcb10c9177 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new 6a2784fa2bd9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new eddaa635a37a 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 40ee9f2facd8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 7dfbc8e2f2ba 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 7c25567c3eec 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 3a6ec04db157 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new 346813260c7d 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new eeac12c58643 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new ebc78ff55f07 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new 72001c02689e 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new 4b0611191504 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 80bde34e7f09 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 16aefb88a254 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new ea3b5c516829 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new a230646d4f3f 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new 3cd0643aa9f2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 73de783ab917 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 58eeb703b460 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 15a04fe24f07 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 2f3d5f6bc8e5 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new 3cdfd0995bda 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new b395f059bfbd 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new a160d566b3cb 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 33b8e1d234b8 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 071b4d46acea 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 9104da9d2837 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 373b41504adb 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new cd7af6475ae0 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 13e0c268ebf2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new fb4a197ea1ab 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 6fbfc7c7fa1b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 9ce1942e4b69 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new b16cdda49d1c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 97153be525c9 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new f82fe94c0f2d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 621dc9b12a5f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cc39fde7028c 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 18579ddf274f 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 9bc991d0a65d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 62c4a627f354 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new edcb893f5de7 121: force: #26: : Failure after baseline build: no new commits new e9d593c65fdd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 631c0cf04723 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 057724b1e35e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 5cf37d676d16 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 6d51debbb828 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 9a2dbe92a38f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new bfde7589bb2f 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 51f9be6d9ccf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 2bbc347bde38 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 3dfe7c09e159 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new e02963839ba6 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 4e01f3501ccf 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new da1f19a705c9 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 20532bff82ac 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 50045b96b953 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 090d160c29f1 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] 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 (3a0260dd088b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 2072 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49712 -> 49356 bytes 04-build_abe-gcc/console.log.xz | Bin 237772 -> 236412 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 8480 bytes 07-build_abe-glibc/console.log.xz | Bin 232028 -> 232780 bytes 08-build_abe-gdb/console.log.xz | Bin 47208 -> 47332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3344 -> 2784 bytes 11-check_regression/console.log.xz | Bin 4500 -> 4404 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 42 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 30 ++++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++++------------- manifest.sh | 32 +++++++++++++------------- sumfiles/gdb.log.xz | Bin 14436 -> 14444 bytes sumfiles/gdb.sum | 4 ++-- 25 files changed, 80 insertions(+), 82 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/gcc-compare-results] branch master updated (605ee41 -> a6d9c3c)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/gcc-compare-results. from 605ee41 From https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--mas [...] new a6d9c3c From https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--mas [...] 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: .../flaky/tcwg_gnu_native_check_gdb-master-aarch64.xfail | 9 +++++++++ 1 file changed, 9 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[binutils-gdb] branch master updated (9c137cd1640 -> c4e37fa8e52)

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 binutils-gdb. from 9c137cd1640 Automatic date update in version.in new c4e37fa8e52 gdb: remove unused parameters in print_doc_of_command, apropos_cmd 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: gdb/cli/cli-cmds.c | 2 +- gdb/cli/cli-decode.c | 16 +++++++--------- gdb/cli/cli-decode.h | 2 +- 3 files changed, 9 insertions(+), 11 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-O2 updated (922197137c1a -> 53e3d18faf7a)

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_size-spec2k6/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts. from 922197137c1a 1: onsuccess: #2: 1: [TCWG CI] No change after binutils/gc [...] new 53e3d18faf7a 2: onsuccess: #3: 1: [TCWG CI] Success 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 2316 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 27332 -> 26924 bytes 04-build_abe-stage1/console.log.xz | Bin 89284 -> 89756 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8276 bytes 07-build_abe-glibc/console.log.xz | Bin 233508 -> 232772 bytes 08-build_abe-stage2/console.log.xz | Bin 211692 -> 210572 bytes 09-benchmark/benchmark-build.log | 123 +- 09-benchmark/benchmark.log | 121 +- 09-benchmark/console.log.xz | Bin 4056 -> 4052 bytes 10-check_regression/bmk-specific-variability.csv | 148 +- .../compare-results-vs-first-internal.csv | 237 +- .../compare-results-vs-prev-internal.csv | 239 +- 10-check_regression/console.log.xz | Bin 15984 -> 18232 bytes .../csv-results-vs-first-1/md5sum.csv | 2233 +- .../csv-results-vs-first-1/perf.csv | 2531 +- .../csv-results-vs-first-1/results.csv | 36702 +- .../csv-results-vs-first-1/size.csv | 803965 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 18818 +- .../csv-results-vs-first-1/vect.csv | 32 +- .../csv-results-vs-prev-0/md5sum.csv | 2002 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2499 +- .../csv-results-vs-prev-0/results.csv | 2967 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 438110 +++++----- 10-check_regression/csv-results-vs-prev-0/sve.csv | 13870 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 32 +- .../csv-results-vs-prev-1/md5sum.csv | 2233 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2531 +- .../csv-results-vs-prev-1/results.csv | 36702 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 803965 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 18818 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 32 +- .../output-bmk-results/exe.improvement | 5 +- .../output-bmk-results/exe.regression | 7 +- .../output-bmk-results/symbol.improvement | 7 +- .../output-bmk-results/symbol.regression | 14 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 2700 +- 10-check_regression/results-vs-first-internal.csv | 237 +- 10-check_regression/results-vs-first.csv | 237 +- 10-check_regression/results-vs-first.log | 1486 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 23 +- 10-check_regression/results-vs-prev-full.csv | 2838 +- 10-check_regression/results-vs-prev-internal.csv | 239 +- 10-check_regression/results-vs-prev.csv | 239 +- 10-check_regression/results-vs-prev.log | 1432 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 16 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../450.soplex/results-metadata.json | 16 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 4 +- .../454.calculix/results-metadata.json | 16 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 4 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 16 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 27 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 36 +- results_id | 2 +- 117 files changed, 1100416 insertions(+), 1098856 deletions(-) create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[linux] branch master updated (00c7b5f4ddc5 -> 6ab608fe852b)

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 linux. from 00c7b5f4ddc5 Merge tag 'input-for-v6.3-rc4' of git://git.kernel.org/pub [...] new 179a88a8558b cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL new 6cc041e90c17 cifs: avoid races in parallel reconnects in smb1 new 09ba47b44d26 cifs: prevent infinite recursion in CIFSGetDFSRefer() new e03677100707 cifs: get rid of dead check in smb2_reconnect() new f7772da66255 Merge tag '6.3-rc4-smb3-client-fixes' of git://git.samba.o [...] new 1abce0580b89 powerpc/64s: Fix __pte_needs_flush() false positive warning new fd7276189450 powerpc: Don't try to copy PPR for task with NULL pt_regs new eca9f6e6f83b powerpc/pseries/vas: Ignore VAS update for DLPAR if copy/p [...] new 95d0b9d89d78 Merge tag 'powerpc-6.3-4' of git://git.kernel.org/pub/scm/ [...] new ec738ca127d0 mtd: spi-nor: fix memory leak when using debugfs_lookup() new 44ac5abac86b Documentation/security-bugs: move from admin-guide/ to process/ new 5c2712387d48 cacheinfo: Fix LLC is not exported through sysfs new a10ca0950afe Merge tag 'driver-core-6.3-rc5' of git://git.kernel.org/pu [...] new f95b8ea79c47 Revert "venus: firmware: Correct non-pix start and end addresses" new 2f1a6be12ab6 btrfs: fix race between quota disable and quota assign ioctls new 50d281fc434c btrfs: scan device in non-exclusive mode new 2d82a40aa7d6 btrfs: fix deadlock when aborting transaction during reloc [...] new 2280d425ba35 btrfs: ignore fiemap path cache when there are multiple pa [...] new 6ab608fe852b Merge tag 'for-6.3-rc4-tag' of git://git.kernel.org/pub/sc [...] The 19 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: Documentation/admin-guide/index.rst | 1 - Documentation/admin-guide/reporting-issues.rst | 4 +- Documentation/process/howto.rst | 2 +- Documentation/process/index.rst | 9 ++- Documentation/process/researcher-guidelines.rst | 2 +- .../{admin-guide => process}/security-bugs.rst | 0 Documentation/process/stable-kernel-rules.rst | 2 +- Documentation/process/submitting-patches.rst | 2 +- .../it_IT/admin-guide/security-bugs.rst | 2 +- .../it_IT/process/submitting-patches.rst | 2 +- Documentation/translations/ja_JP/howto.rst | 2 +- Documentation/translations/ko_KR/howto.rst | 2 +- Documentation/translations/sp_SP/howto.rst | 2 +- .../sp_SP/process/submitting-patches.rst | 2 +- .../zh_CN/admin-guide/security-bugs.rst | 2 +- Documentation/translations/zh_CN/process/howto.rst | 2 +- .../zh_TW/admin-guide/security-bugs.rst | 2 +- Documentation/translations/zh_TW/process/howto.rst | 2 +- MAINTAINERS | 4 +- arch/powerpc/include/asm/book3s/64/tlbflush.h | 9 ++- arch/powerpc/kernel/ptrace/ptrace-view.c | 6 ++ arch/powerpc/platforms/pseries/vas.c | 8 ++ drivers/base/cacheinfo.c | 16 ++-- drivers/media/platform/qcom/venus/firmware.c | 4 +- drivers/mtd/spi-nor/core.c | 14 +++- drivers/mtd/spi-nor/core.h | 2 + drivers/mtd/spi-nor/debugfs.c | 11 ++- fs/btrfs/backref.c | 85 ++++++++++++++++------ fs/btrfs/ioctl.c | 2 + fs/btrfs/qgroup.c | 11 ++- fs/btrfs/transaction.c | 15 +++- fs/btrfs/volumes.c | 20 ++++- fs/cifs/cifsfs.h | 5 +- fs/cifs/cifssmb.c | 30 ++++++-- fs/cifs/smb2pdu.c | 1 - 35 files changed, 216 insertions(+), 69 deletions(-) rename Documentation/{admin-guide => process}/security-bugs.rst (100%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[gcc] branch master updated (802ab7d0db5 -> 1719fa40c4e)

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 802ab7d0db5 RISC-V: Fix reload fail issue on vector mac instructions new 1719fa40c4e libiberty: Make strstr.c in libiberty ANSI compliant 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: libiberty/strstr.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (0839a8418cfb -> 94cf3eeaa299)

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 in repository toolchain/ci/base-artifacts. discards 0839a8418cfb 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/g [...] discards a08ff71c08f4 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/g [...] discards 4a208b874f7e 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] discards 1f173b6aac5c 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] discards 9af4566819d3 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits discards 1aa9c0a75f9c 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc [...] discards 8c5cbaa39a72 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits discards 3324e4f064e8 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: [...] discards 2a30fbac75bd 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits discards 1b98c214f135 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits discards 7db43535a4be 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits discards fd1747fa1d4b 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits discards 4654efc8d47a 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits discards 9ce6a2ef3de2 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 206af378b970 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards 7e9a9e0072aa 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards bfb588cde0a1 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards ffffe926de0b 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards 29c2e05d147f 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards a4eb0bb9fdcd 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards ed2325038ff3 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards 55b03f7bcfd9 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards 45bc1a43b06c 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards 0e65b92dd56f 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards e9c9a79b350b 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards 0370fc5376eb 178: onsuccess: #16: 0: Success after binutils: 15 commits discards 5870c6fb7016 177: force: #15: 0: Failure after gdb-13-branchpoint-1318- [...] discards 1ff82b357c90 176: force: #14: 2: Success after binutils: 18 commits discards fdb6ef1bf71a 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards 8027dbe4ec7e 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards a62f77226d6f 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards cad3f74fa766 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 0693a152de6c 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards 0ae19809880f 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards a58ef3e1e1a3 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 127ce06abdae 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 2cbc1809eb1b 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards ac4e6c1cea5b 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards 1620ff5cef0c 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards 1ab8c558d584 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards f829fb50f78b 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards 7f40ebbb9d9b 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards 0ff46f1002ea 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards 81906bcae921 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 5b72c144e74d 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards 8a3cc183c11c 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards 2434c0e875e9 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards b5a9f2466b99 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards 33cf19cac1c9 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards 912e5af62dbd 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards 0bd94cdeb6ad 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 24746f65c620 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards 420687a5f338 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards 34f84ad45116 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards 9819c540c4e4 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards f4e206d10119 148: onsuccess: #571: 2: Success after gcc: 4 commits discards 7537379a5250 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards bc695f38aa3c 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards 821324af848d 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards a793fd0ae06e 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards a71a84197f2c 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards 7210d4e3b907 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards dd94ab948287 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards cfdcfcc73aad 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards 6af3d0065c8a 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards 7796ad2c9042 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards db8a34429e9c 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 8f204f319e62 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards 67642b6de814 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards 105289317d73 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards 87cf66f0f883 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards 201d7bfb5db4 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards 72aee8e5d915 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards eeb530780c74 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards d7dd50cf7de7 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards 0af8b72f9629 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards 113e11186cd5 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards 33e20c6187fa 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards a428360a1f82 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 85b040ce0dca 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards 9158671248f0 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards 28d451746357 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards b662d663a432 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards 30c8027ce677 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards 72f568f9ef85 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards bd479409418a 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards 762bb47a0d8c 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards 56a88295f394 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits discards 73c4b82a9da3 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 521aee5e44d7 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits discards 93c287fc8a76 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits discards 878ecf200ee4 112: onsuccess: #527: 1: Success after binutils: 10 commits discards f4ebc48af36b 111: force: #526: 1: Failure after binutils: 5 commits discards 0a24ebae925d 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits discards 6b5e16c46f43 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits discards 97acd2eebdc2 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits discards 96f6686e297d 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits discards 7733914a97a3 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits discards 787b9ad42c36 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits discards 9a3331637169 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 6e16f5b52431 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits new ef9ef0c65131 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits new 67646e173cc9 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new 68195e662ee9 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits new e480ca8eebad 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits new 542c9837fa84 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits new 792dfedebe9c 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits new 5df45bc03444 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits new 1bd8257df107 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits new 3accd0412fe8 111: force: #526: 1: Failure after binutils: 5 commits new c04540c5597d 112: onsuccess: #527: 1: Success after binutils: 10 commits new 7225e4803b6d 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits new d0b717c51cf4 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits new 53b0e92153c2 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new dec7ffdd8e55 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new 31567621b64d 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new f8db3d7cfc79 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new ead1835fc0a9 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new e400dde2bac5 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new f24cdf596f7e 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new 654aa75cad22 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new a6fbebba3705 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new 3cc6b598c08d 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new e12b7af5d5c3 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new 413dcd6fe0e1 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new 0a0ccb171666 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new b1c910511f71 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new d71b0f37ec9a 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new 251656272b7d 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new 2a1a5a2e9d3a 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 37ae455c4cf3 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new 08b2474f7aa8 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 3758d9f0a680 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new eef3597ff9ae 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new 8d9146c1bc02 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new 6f474ca0aed7 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new 74cac075924d 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new 2447a5a9eae0 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new e3020c4551c9 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new ee68c0ef0a4e 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new 1de7a7001757 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new b3af607b857e 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new c8bd539a5e73 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new 6ddcf150ad91 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new 3839656f5718 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new f1a7be3a437f 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new 35337df9245c 148: onsuccess: #571: 2: Success after gcc: 4 commits new 1378e121b05e 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new ebed85a17926 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new b32f49883147 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new 12fb7c2ae32a 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new b0eae97562a5 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new f26cf58ed3f9 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new 8e33a826394e 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new 0d2190a41f52 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new 1fa5bb65e6d7 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new bca0e0e2249d 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new 54ac4761e98c 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new cf411c96ffb3 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 635d1cd957aa 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new 1f15374fb543 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new 31039f79b149 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new cfeed4d80743 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new 0ee4edfdb39c 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new f72984b12666 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new 6e03048b1fc7 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new e06c8198a446 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new 4ea602c7125a 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new 3884a0fc446d 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new 58c93f567c42 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new df94c3caec65 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 1f855b99c73f 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new e6af9888305c 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new e0fd990f7230 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 8e7d23d771e5 176: force: #14: 2: Success after binutils: 18 commits new e7e0f5e2e589 177: force: #15: 0: Failure after gdb-13-branchpoint-1318- [...] new 0821c2a53665 178: onsuccess: #16: 0: Success after binutils: 15 commits new 2fb8209dd552 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new c8883c6311cd 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new 03730c31e2cf 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 78a07af3305c 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new 8212abbb058b 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new 39836e650bc7 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new f17f167ebe4e 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new b6588822ed73 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new 3f878a7b158b 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new 5515263656ee 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new 7a5afc955c29 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new ad2d649cfe67 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new f89366e07e41 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits new 24bc834ee426 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits new 223c6ed78645 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits new e16a954b1b4b 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits new f2e3bb56449f 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits new 3f7b80e21828 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: [...] new 6ed01ee74652 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits new e298126bd6a0 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc [...] new e7a5e750876b 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits new 2d7e4ec7917a 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] new aa789ae6f553 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] new f8ce587b2c8d 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/g [...] new dec3318efe59 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/g [...] new 94cf3eeaa299 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/g [...] 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 (0839a8418cfb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1964 -> 1940 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2536 bytes 04-build_abe-binutils/console.log.xz | Bin 49408 -> 48948 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 609460 -> 611560 bytes 06-check_regression/console.log.xz | Bin 2784 -> 2548 bytes 07-update_baseline/console.log | 40 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 12 +++---- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 +++++----- manifest.sh | 18 +++++----- 13 files changed, 46 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-surfaceflinger/oriole-master updated (b4d9bca11f9f -> 7954191a53ed)

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_aosp-code_size-surfaceflinger/oriole-master in repository toolchain/ci/base-artifacts. from b4d9bca11f9f 7: onsuccess: #58: 2: [TCWG CI] Success after aosp_superpr [...] new 7954191a53ed 8: onsuccess: #59: 2: [TCWG CI] Success after aosp_superpr [...] 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 1992 -> 2156 bytes 02-build_aosp_toolchain/console.log.xz | Bin 199688 -> 198036 bytes 03-build_shadow_llvm/console.log.xz | Bin 131280 -> 130580 bytes 04-build_aosp/console.log.xz | Bin 69460 -> 68848 bytes 06-check_regression/console.log.xz | Bin 7044 -> 6552 bytes 06-check_regression/results-vs-prev.csv | 72 ++++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/aosp_superproject_rev | 2 +- git/llvm_rev | 2 +- git/toolchain_superproject_rev | 2 +- mail/changes-list-long.txt | 30 ++++++------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 24 +++++------ manifest.sh | 24 +++++------ size.csv | 62 +++++++++++++-------------- 15 files changed, 109 insertions(+), 113 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (10c8dea141d5 -> 95d2436d2d7e)

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-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 10c8dea141d5 68: onsuccess: #8: all: Success after binutils/llvm/linux/ [...] new 95d2436d2d7e 69: onsuccess: #9: all: [TCWG CI] Success after binutils/l [...] 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 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 27196 -> 26668 bytes 04-build_kernel_llvm/console.log.xz | Bin 65236 -> 65212 bytes 05-build_abe-qemu/console.log.xz | Bin 30808 -> 30808 bytes 06-build_linux/console.log.xz | Bin 3108 -> 3108 bytes 08-check_regression/console.log.xz | Bin 4328 -> 4248 bytes 08-check_regression/mail-body.txt | 27 --------------------------- 08-check_regression/mail-subject.txt | 1 - 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/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 27 --------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 22 files changed, 49 insertions(+), 86 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023