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 f7e7d5c26a 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 599509c61a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 3849c38d62 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards cead47fdcd 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 4f93725d5b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 5a9ab14857 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards fd46016330 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 661a788d72 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards b3a5fac286 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards cba9932696 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards b193a3ff50 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 390e73fddf 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 694efcf3cd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 7c189d98ec 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 657469d3a0 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards c990a843a2 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards b265c698b4 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards eadb432219 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 17e044bcdf 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 9a43779055 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 32363c143e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 432928a33f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 48fcecc248 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 76c454a0b1 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 0e4fc31f87 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 498f11110d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards da46a90983 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 89c42d8788 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards b243985fe7 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 0ded5a2bc0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards 26a41acaad 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards f94e7f2a0c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards b10705b9ea 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 012a5c3a49 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards d59a9f3a93 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 65368bdcd8 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 1d4bae1578 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 26f9e5b4ec 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 2ac05cd1f9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards de07a5d9d9 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 6988b5962f 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 93c7cb4069 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 45b8ec3224 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards fd16adcff4 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards e1c0bb56f5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 3e5aaad2d2 125: onsuccess: #614: 1: Success after linux: 12 commits discards 9fecf54710 124: onsuccess: #612: 1: Success after binutils: 18 commits discards f08cd45dfd 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 2bce347912 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 3c29690fdd 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 4517054be5 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 9b6e7cebe1 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0589e7e190 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 55aa8106fe 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards e4fb6a76c7 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 6cb2b469ea 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 1c5381e338 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards b8f2c907ad 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 6f7287235c 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards a9ad00a7f5 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 27d989623f 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 55b3bd2b80 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 7c4869a2b5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 0452b5b835 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards ca139cb31f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 89612b7c08 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards f5c1fe43a9 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 2de18223c3 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 40a31d1d1a 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 6ce3f60e1b 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 7ee0e2a10b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 056a34719a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 076fbcf8a2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 9f22a1248a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards e24d070449 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards f13807db6c 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 699650c026 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards b610e5f4e1 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards ae68290690 92: onsuccess: #575: 1: Success after linux: 34 commits discards fa9f03d0f3 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 633af88ac9 90: onsuccess: #572: 1: Success after binutils: 15 commits discards ade197a599 89: onsuccess: #570: 1: Success after linux: 11 commits discards 365248701d 88: onsuccess: #569: 1: Success after glibc: 10 commits discards db350cc89d 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 8631bc52a7 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 5a8a530048 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 0aeaf87c2b 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 51239847d3 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 240a3c0a58 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 80d4fa8e1f 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 92c766c444 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 857a16b61d 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 815e18fdae 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 7376debbdb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 16b41ea9f3 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 242131c3c4 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards ea2db97c95 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards be601c1c55 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards b373553e80 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards fc379bc9ba 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 45fb304871 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new d84a97024a 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 6779053ade 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new a1b43f6c16 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new e96830d3e5 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 28db6c5edc 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 5c77865010 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 66a5fcc8d9 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 6316925a85 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 7b89f6873b 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 56f47162df 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 9941c621d8 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 0a7b997fdd 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 570ad57238 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new f2d06fb0f4 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 6f73be3f43 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 3674dfa973 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new 1419f0477a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 5aaf499228 87: onsuccess: #567: 1: Success after binutils: 8 commits new ac4819173b 88: onsuccess: #569: 1: Success after glibc: 10 commits new 5d2967cc02 89: onsuccess: #570: 1: Success after linux: 11 commits new 75f4b5fdf8 90: onsuccess: #572: 1: Success after binutils: 15 commits new 88a45c6734 91: onsuccess: #574: 1: Success after glibc: 3 commits new 1aabea87bc 92: onsuccess: #575: 1: Success after linux: 34 commits new bd97aa94ac 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new be5d956685 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 8febbeed7e 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new afe5e4dca0 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 45a0d3bab8 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 5d3a1ca527 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 510a58e7f6 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 5593d89588 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new fda348d519 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 5b40513259 102: onsuccess: #586: 1: Success after binutils: 5 commits new 65e46dddff 103: onsuccess: #589: 1: Success after binutils: 3 commits new 126e41a8b8 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 246f944ca8 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new e40b89229c 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 9b5868d6d8 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 3326f4423b 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new f7dff842be 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 9af6b569e9 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 5ae31dd5d4 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 50451bc32e 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 7207798ffa 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 22bc70cf68 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 6656526c5f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 1ede14e1c8 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 26de517432 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 3e2b52f1e1 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 4761053ab7 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 1310c2d71b 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 0d9048d9f1 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new d0057b7eb8 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new d31984dd12 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new daafd5f6bf 124: onsuccess: #612: 1: Success after binutils: 18 commits new e9e8d249af 125: onsuccess: #614: 1: Success after linux: 12 commits new 9b6a35f00c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 7b5857248e 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 047966d3f6 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 06af23aa98 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new e46630eb60 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new ac6aaa4ac5 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 4e064117e9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 77f8155405 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 544c09064d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 03022bb03c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new a2a4862755 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 82cb52b9be 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 2cb9948abe 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new e6cde34aac 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 754043ffaa 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new be1d69f4e4 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 3f1d1c4ac2 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new e8d1db6fd0 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new a367c09e0e 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 69f2f7ea9d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 6c3d4606e7 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new d9cde1a733 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 7d777f5cea 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 22f673dbc6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new d59c9dc110 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new ed5a3ac01e 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new b767587427 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 33963faffc 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 5f1743fb23 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 49050c19a9 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 6ea621044d 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 555c6f9eca 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 6bf580f19f 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 0494dcf6bf 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 21e9195834 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 439d8995a2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 3837966e33 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new a8fe53a518 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new afddfc182f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 5eecbb3524 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 4137059e3b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new e15cd3a257 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new d76d943529 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new e6cbd01135 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new af7b9f60c7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 9ce280eadd 171: onsuccess: #665: 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 (f7e7d5c26a) \ 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 1784 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52084 -> 52064 bytes 04-build_abe-gcc/console.log.xz | Bin 238680 -> 239596 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8736 -> 8876 bytes 07-build_abe-glibc/console.log.xz | Bin 236128 -> 236448 bytes 08-build_abe-gdb/console.log.xz | Bin 50636 -> 50588 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3868 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2264 -> 2288 bytes 11-check_regression/console.log.xz | Bin 10144 -> 21180 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 69 +- 11-check_regression/mail-body.txt | 192 +- 11-check_regression/results.compare | 118 +- 11-check_regression/results.compare2 | 4733 ++++++++++++- 11-check_regression/results.regressions | 114 +- 12-update_baseline/console.log | 64 +- 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 | 194 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 114 +- sumfiles/gdb.log.xz | Bin 1819980 -> 1840824 bytes sumfiles/gdb.sum | 10560 +++++++++++++++++------------- 31 files changed, 11144 insertions(+), 5070 deletions(-)