This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards 843a63965b3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 91c3c47e0f3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c1e23aaa2e1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 514a9a36b5f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards bb3a48bb7f3 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 53e73159606 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards aad283b2a2a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ad30838fe0a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 56730fd9bff 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 578ee32f0eb 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards aafffe63629 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a1f4b90ed18 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards fde376660ff 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards a11d465ab3c 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards daf4c66b800 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ca179141a55 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c4f0751efc8 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 47051986b26 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3c8bfba9bf4 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 47dc63488f9 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 236a61389b1 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards f07877716b3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards b15780a725c 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 461ef46a400 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards aacee198f33 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards cec6fdd503f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 9e4d86b28c3 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 603ce77a94e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards bfcfac28e42 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards a0a798b74b5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 8c877a08781 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 590ee53cee7 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards ef477daaeb5 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a9c9e8868fd 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c615975e6db 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 982667c39ca 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 894d1509e45 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 07d65b4c68c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7572d623767 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 4135dc5b380 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 661b465a4f9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 8e91dcfe338 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards e4938e4cbc2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards e9d8937ddd7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards b4f3f7d7429 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 553ba70ad58 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards a262026cceb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 16efcfb5dc1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 8eeb2157e29 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 1d5d4117e3e 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 0d0cff6bf0f 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards ee41aac31b5 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a1a6e55a3fd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 1c1901288e6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8c5c6869ec8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 6b9cfb7aeda 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards b69763224bb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 3ced90d5b82 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 2ac340c8f05 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 0bbe166770a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 528f53d74d0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9388fc72536 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 0265148f714 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards c86bc00012b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 1e4d6ff1248 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 4d769533d69 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 8c737a73e12 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards bc5a6d04aca 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 456e3d7171a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 68320755907 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 75478275eb6 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards f216d096aef 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 94282aa9a44 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 1b689c86179 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 9047508a2a2 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 52e4e5fdf99 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards a3775f4c6c1 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 4a922fa4316 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 317152e2184 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards b7fc0852f41 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards e43fa9b2f8a 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards e130f2f60c4 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 5b39117f529 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 7a053d2a420 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 24d2f1db67c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 102760424e8 125: onsuccess: #614: 1: Success after linux: 12 commits discards fa2a7732632 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 2e04c578b75 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 2ada3eb63e3 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 5359229d65c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 6f239b0cfe2 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 105878a9a3c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 2cc1cd0bf90 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 599cde5d5d9 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 3329c259a5c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards ef07a1f045a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 6063578be88 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 13120ed1900 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards aa170b58b37 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 4f493135207 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards b3c39cf8686 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 9067c6d28ea 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 81ae32652ae 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new 1aad1c6ed29 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 71ccd5d97d5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 07433011600 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 0b5004b16c7 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new c3e89a6c412 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new b2eeadce232 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new f568c71b395 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new b4465b90eac 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new a90eed535cf 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 544b455fd5e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 6e0e6608b94 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 82f8f861cfc 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new bb524ca79ef 124: onsuccess: #612: 1: Success after binutils: 18 commits new 64a49412128 125: onsuccess: #614: 1: Success after linux: 12 commits new 296552bf784 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b7e9a3f30bb 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d601d2755b1 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 268bc041d83 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 164e19b9c47 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 8ce025a6460 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 1b7fb2bca99 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 66f3758b7fd 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 3360ee4b06d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 13a30c42c1c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new dd6d4b199a3 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 48b8848a570 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new f50bb18e367 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 71d1e96bcbd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 78ba52b3670 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 30c5b92e115 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new ff549f546f7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 592290e7340 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 8dbd74aca79 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new d38af193d76 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new ff322691b57 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 4e54a6f98d7 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 981152c84df 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new d63d6bcf80c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5764d603efe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new ac832597911 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 87b5d59b046 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new b4ca68855cb 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 25d96ed1909 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new d03ba0dea76 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8bd7446c4b7 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 3467d7bf2ae 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ced2a4ea7c2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new d6b7d6cff62 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 0af4c3fab1b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 01b6c2127b8 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 3fe0475958f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 63e218d01ba 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new c75cb71b621 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 60e7471807c 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new fa735bd9d12 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 0a8d0318e68 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new bacace96583 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 2acc962fad1 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new ce16eb26885 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new e7072affca9 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 7c34444dcc9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 422a37d0e07 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 0a26666bf17 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 85cf39b1e8b 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new fab320fd2c1 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new c713600e88a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new f30dd3101df 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new a8f669f64d6 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 81edd316a4c 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 1d0314e30de 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 516d844d3e9 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 1c5ee70fc14 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new eb97fd468f5 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 6db535e462c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new d8172b89318 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new ad4dfa4f123 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 3e2e3cee547 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 6df3331d662 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new b598502d351 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new f54b8e69251 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new fcb8e43d007 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c66740cf985 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new b38a4f0eb75 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new eca5d866768 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 43f637acd56 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d7d1ca070b1 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 3f2d1b294f4 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 19f8d229b0f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new c15644cc51a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ab3268bce36 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7e00d539f0f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bd960d697d8 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 24601174782 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 83dbc1faead 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 06b32a2ee59 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new e454b1e3e08 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new eca4bd5af01 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new c60874571d8 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new b501e1fe4f2 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e27aadb1e8c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (843a63965b3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1748 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52596 -> 52656 bytes 04-build_abe-gcc/console.log.xz | Bin 237232 -> 238028 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 9080 bytes 07-build_abe-glibc/console.log.xz | Bin 235552 -> 235084 bytes 08-build_abe-gdb/console.log.xz | Bin 51316 -> 50268 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3748 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2160 -> 2016 bytes 11-check_regression/console.log.xz | Bin 7972 -> 7716 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 20 +- 11-check_regression/mail-body.txt | 98 +- 11-check_regression/results.compare | 46 +- 11-check_regression/results.compare2 | 211 +- 11-check_regression/results.regressions | 46 +- 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 98 +- manifest.sh | 38 +- results | 46 +- sumfiles/gdb.log.xz | Bin 2931788 -> 2948932 bytes sumfiles/gdb.sum | 4422 ++++++++++++++++--------------- 29 files changed, 2533 insertions(+), 2574 deletions(-)