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 6c035bc5d94 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards c3e8a484f04 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 9ed5f9b06d6 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 1da654ef14c 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3a236ee2cf0 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards d38218d96bf 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 66fe08689ef 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 88419bf5b82 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 78e4c99ecdf 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards b20a70d1db0 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f186dc80630 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0fe5a103a47 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c9e5e10124e 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards d72e7184ecf 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards da1579f3a6c 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 01f15e034c4 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 567601cba5b 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2fe01a67906 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards ab5901c4242 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 4cb9587882a 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 24ca236935f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5523478014c 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards e611f04ca15 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c5a1de474f1 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 827498c0021 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 0ef453391f9 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 7b4d4d6b4f4 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 18ef0f6095e 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 5322226551f 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 881303c7b14 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 165a31d676d 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards f68fddd1a60 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards e55dd982cd5 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards a3f33138a66 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 7162c361f45 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards dce19ff65c5 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 0170704cfaa 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 5d7e2c7cfdc 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 7da1b80a455 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 9ad8d178e4f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards a61d0154267 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 175d8ee0f35 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 48394f9c014 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 631440b9a8d 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 91d34bb58c9 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards f08bbfd97f2 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 2d5cdb9721f 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards f908d078891 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 1c9def99304 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards bdd33ee6819 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards bd700afd885 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 5f28cf2a581 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 25cf5ec3bd4 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 664a556a28a 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 3bd4e32d5f6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 7ec3b4856bf 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards f7a0137eddd 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 8d218f844a6 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards bb9455f7ee1 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 59ef5fcaf73 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards bc1bbb3b9fb 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards cf71901c70e 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards ee5d3d6d728 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 832f9fbd8d9 162: onsuccess: #624: 1: Success after linux: 10 commits discards dbac19feee2 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 891f37494ae 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 79a1919a238 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 55a89b1e8d8 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b582d4208b0 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 3295f882171 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards de11f495ed3 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards cd163052e67 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 3106bdd465c 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 4129247f4fb 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 97a3b8cd952 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards e3bdd65812a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 69c837a56a0 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 032e971eac1 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards ebb103b0ce2 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 4368e35a77a 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards ae7a2e4c877 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards b6b948c5b07 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 51636d11442 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards d48a129bfe3 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 82e7a035d9c 141: onsuccess: #601: 1: Success after linux: 794 commits discards c44601010b3 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 9d7e9176b8f 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 26c40409da6 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 1cddb693bb6 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards a7cf1a92c1d 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 3f6fed70202 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards deb336df2b8 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards c0ca16a32b4 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 92b5d66d962 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 6ae6a61eac8 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 7ba36492cfd 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 57e0ce9a0f0 129: onsuccess: #588: 1: Success after linux: 4 commits discards f9b870bbcba 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 96284088087 127: onsuccess: #584: 1: Success after linux: 21 commits discards a9cd947b29e 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 2a74282574d 125: onsuccess: #581: 1: Success after binutils: 4 commits new 10d8c5866b7 125: onsuccess: #581: 1: Success after binutils: 4 commits new 275815e18a5 126: onsuccess: #582: 1: Success after gcc: 9 commits new f66eda167a7 127: onsuccess: #584: 1: Success after linux: 21 commits new a1483b686e0 128: onsuccess: #586: 1: Success after binutils: 22 commits new 2d5199f8cba 129: onsuccess: #588: 1: Success after linux: 4 commits new 48b702b676e 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 75e9aa1ba1d 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 06c880d159a 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 581ba80f179 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new f707e708a92 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new a71233079c6 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new eb47395f83b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new b3fe0d5c638 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new dd6f0e61661 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 2c3ddbc72ce 139: onsuccess: #599: 1: Success after binutils: 10 commits new 0e10215f7b1 140: onsuccess: #600: 1: Success after gcc: 23 commits new 0558a587bc4 141: onsuccess: #601: 1: Success after linux: 794 commits new 16f96990919 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 56ff285420d 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new d87610cd8ee 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 5d1782d1dc9 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 69be4272fb3 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 769f7b45797 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new bcfcd4e2ab1 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 75c4d8ea1e3 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 0e802dbf4b3 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 66af74e9256 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new fadd77aa849 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c2f7bdd3bb0 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 45b983dca67 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 1967d49f34f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 1839f7cff67 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 9b749aac43f 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 1bd9a1ab611 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new a4f40a1667c 159: onsuccess: #620: 1: Success after binutils: 12 commits new 8821ad61315 160: onsuccess: #621: 1: Success after gcc: 11 commits new 10cc91598e3 161: onsuccess: #623: 1: Success after glibc: 9 commits new 570868b731e 162: onsuccess: #624: 1: Success after linux: 10 commits new 27c30c09506 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 109a930ea8f 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 14864bf0caa 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 6d0c9c8cf9e 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new dc05141445d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 58f7ace8a16 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new aa04b13ab33 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 11112fb7ad3 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new a9cf07f7190 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 5645230710a 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new d92bb0119d7 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 6ce21a733a1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new b1d838d9285 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new ba6a32beb9f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 0dcd16e9ff4 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 150712fc26d 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new a1f5bc746e4 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new bdfe519447e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9923b1397a6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new ca2b96c9323 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 2bca50d9496 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new e55a0927d46 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 7e2baf3272c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new e9df2dc89c8 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new aca9ba66c8d 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new c2b1f8ae782 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 6449efa4f6b 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new e7f6a085727 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 772aaa80fe9 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new bac422cd19b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 9ed4cf95022 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 312b07fd08b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 0974bb26de4 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new a2bcb97ecee 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new cd6d797450f 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new b2170a04721 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 73d0ea0ef6e 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new ca9c8189fec 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8b297dd5117 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 89b5dbdecbf 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 1d9c3de02d3 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new c302ab32510 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 6b5ae5e5412 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ec5b7fff7c3 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new f2d2a436ca0 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 9304ef8f1b9 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 78e7da62be0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 73e02da8ccd 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 333703f8c0b 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new d49e3342f5d 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e7f19a32158 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 02cbb00be59 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new cd654ffcc8a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 530163b3557 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 29af1ed45de 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 0ea633aa73f 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new d4dfaa6f873 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0e45b3ec4d7 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 2c4d32f0080 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new b3417168928 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new d9921b748dc 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3df1342bb95 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 37341ebb089 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 6bfdc0fa035 226: onsuccess: #26: 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 (6c035bc5d94) \ 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 1768 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 48724 -> 49060 bytes 04-build_abe-gcc/console.log.xz | Bin 235124 -> 235536 bytes 06-build_abe-linux/console.log.xz | Bin 8816 -> 8204 bytes 07-build_abe-glibc/console.log.xz | Bin 232992 -> 233148 bytes 08-build_abe-gdb/console.log.xz | Bin 46132 -> 46484 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3776 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10260 -> 10732 bytes 11-check_regression/console.log.xz | Bin 8372 -> 5332 bytes 11-check_regression/mail-body.txt | 29 - 11-check_regression/results.compare | 14 - 11-check_regression/results.compare2 | 638 +-- 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/jira-body.txt | 2 +- mail/mail-body.txt | 31 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 81308 -> 48292 bytes sumfiles/g++.log.xz | Bin 2872680 -> 2881268 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 6377 +++++++++++++++-------------- sumfiles/gcc.log.sep.xz | Bin 94656 -> 51504 bytes sumfiles/gcc.log.xz | Bin 2512412 -> 2516772 bytes sumfiles/gcc.sum | 2 +- sumfiles/gcc.sum.sep | 7110 +++++++++++++-------------------- sumfiles/gfortran.log.sep.xz | Bin 46492 -> 44964 bytes sumfiles/gfortran.log.xz | Bin 953332 -> 962060 bytes sumfiles/gfortran.sum | 30 +- sumfiles/gfortran.sum.sep | 1773 +++----- sumfiles/libatomic.log.xz | Bin 2280 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233700 -> 233792 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 7868 -> 8724 bytes sumfiles/libstdc++.log.xz | Bin 476356 -> 479208 bytes sumfiles/libstdc++.sum.sep | 277 +- 44 files changed, 7034 insertions(+), 9371 deletions(-)