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 d9f6e6864a0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards de67044a1fc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 34c497e064a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 38791f22057 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards db469e122db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2d25e775ad2 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fad3effe4a6 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4300f87f953 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 22a6aae1cb7 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e05f1ee7935 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6138398974c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 11bdb1eedba 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 65ca1168547 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d99fb45f684 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 40ab4749c9f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 7f444169df5 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards cc59c9282fc 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e05f49addb9 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards b6fb4055127 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1886130caee 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ee38660ad4c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards d797c12765f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards c0364508599 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 01118ee48ae 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 80537b6fa0d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards b11ed300fbd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 17750f98542 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 7b4bb8ab9fd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 2552534de75 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 89a5657294b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 86bc69bce24 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards d521e94ee61 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards f088a94bd7f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 55cfa18838e 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 5ee6bcedef2 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 72ed91c2e56 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 4e68bd01056 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 05f74e351d7 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a05fa658a78 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 6cf40f9e0ed 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards e2536ccb572 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 8c318840f83 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 92c21c1ce9f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 5be151b9d6e 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a7885f98b30 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0310b9d7f45 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards e8dfb5b0286 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 4cf1b4f74e5 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 411879111fb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 38ffb51e0a6 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 84c956eb672 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 989eb7ec4e9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 3a013a94170 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8d5d3bd1b58 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 72e7251733e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ea9b950f730 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards c0aa3fbc62a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards c3c72236b4c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 6b1fb13c16a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards b5be86edf4d 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards b08c10e45fd 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 815afc3ca08 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards c2daddf74c4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards bb354348b77 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 8ca0e8a1f93 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 737e76fa3b4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards e1a6751e92c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 380b46779c9 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f4830d400ab 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 4b689853286 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 647d4c6b4f0 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards a678a9c0ec5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards ef4faccaed7 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 4b4981cdacc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 60c0d72fafe 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards f5c8135c2e6 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 4fba228c61b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 95ae81fa8e4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 11c0a5f0101 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 6afebdb904e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards f4539b8dae1 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 47e28ca4461 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 410e7e86878 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 84da46d299f 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards d7498dceafc 125: onsuccess: #614: 1: Success after linux: 12 commits discards d24c0f3bb0f 124: onsuccess: #612: 1: Success after binutils: 18 commits discards ee6d10d996c 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 171e1a1e13e 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e5aa926f78f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 3d3bf36501b 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 009082bc885 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards f91ab5739bc 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards de324bc55c5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 4cb4612d15b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0f0f700c6ed 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b6418235e34 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 37e8e3663b4 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 5a93c33f065 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 81f6f35cc9b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards f8d6f726fe3 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 645a5af1edb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new c6624184a6a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new b3c39cf8686 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4f493135207 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new aa170b58b37 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 13120ed1900 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 6063578be88 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new ef07a1f045a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3329c259a5c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 599cde5d5d9 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 2cc1cd0bf90 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 105878a9a3c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 6f239b0cfe2 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5359229d65c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 2ada3eb63e3 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 2e04c578b75 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new fa2a7732632 124: onsuccess: #612: 1: Success after binutils: 18 commits new 102760424e8 125: onsuccess: #614: 1: Success after linux: 12 commits new 24d2f1db67c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 7a053d2a420 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 5b39117f529 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e130f2f60c4 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new e43fa9b2f8a 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new b7fc0852f41 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 317152e2184 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 4a922fa4316 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new a3775f4c6c1 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 52e4e5fdf99 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 9047508a2a2 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1b689c86179 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 94282aa9a44 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new f216d096aef 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 75478275eb6 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 68320755907 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 456e3d7171a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new bc5a6d04aca 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 8c737a73e12 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 4d769533d69 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 1e4d6ff1248 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new c86bc00012b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 0265148f714 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 9388fc72536 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 528f53d74d0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 0bbe166770a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 2ac340c8f05 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 3ced90d5b82 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b69763224bb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 6b9cfb7aeda 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8c5c6869ec8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 1c1901288e6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a1a6e55a3fd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ee41aac31b5 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 0d0cff6bf0f 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 1d5d4117e3e 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 8eeb2157e29 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 16efcfb5dc1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new a262026cceb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 553ba70ad58 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new b4f3f7d7429 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new e9d8937ddd7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new e4938e4cbc2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 8e91dcfe338 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 661b465a4f9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 4135dc5b380 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 7572d623767 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 07d65b4c68c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 894d1509e45 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 982667c39ca 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new c615975e6db 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a9c9e8868fd 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new ef477daaeb5 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 590ee53cee7 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 8c877a08781 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new a0a798b74b5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new bfcfac28e42 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 603ce77a94e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9e4d86b28c3 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new cec6fdd503f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new aacee198f33 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 461ef46a400 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new b15780a725c 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new f07877716b3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 236a61389b1 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 47dc63488f9 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 3c8bfba9bf4 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 47051986b26 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c4f0751efc8 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ca179141a55 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new daf4c66b800 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new a11d465ab3c 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new fde376660ff 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a1f4b90ed18 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new aafffe63629 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 578ee32f0eb 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 56730fd9bff 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ad30838fe0a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new aad283b2a2a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 53e73159606 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new bb3a48bb7f3 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 514a9a36b5f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c1e23aaa2e1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 91c3c47e0f3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 843a63965b3 210: onsuccess: #19: 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 (d9f6e6864a0) \ 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 1760 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52192 -> 52596 bytes 04-build_abe-gcc/console.log.xz | Bin 236912 -> 237232 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8280 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 235992 -> 235552 bytes 08-build_abe-gdb/console.log.xz | Bin 50988 -> 51316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3796 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2000 -> 2160 bytes 11-check_regression/console.log.xz | Bin 7516 -> 7972 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 91 +- 11-check_regression/results.compare | 52 +- 11-check_regression/results.compare2 | 235 +- 11-check_regression/results.regressions | 52 +- 12-update_baseline/console.log | 66 +- 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/jira-body.txt | 2 +- mail/mail-body.txt | 93 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 52 +- sumfiles/gdb.log.xz | Bin 2929564 -> 2931788 bytes sumfiles/gdb.sum | 4433 ++++++++++++++++--------------- 31 files changed, 2648 insertions(+), 2506 deletions(-)