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-aarch64 in repository toolchain/ci/base-artifacts.

discards bc07bffbad 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards 71b479850e 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 9a184757b9 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards c18686ae7a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 51a169e6eb 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 3f3da45bcd 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 5448198a4c 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards 5c63714082 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 6ebf137ce2 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards c0c34665e3 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 1a38693b4e 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 71aead88e7 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 009c0abcb9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards cb32f3d480 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards d22686657b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards cd2236dfe0 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 4bdd2e1fa5 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards e8bbdbc425 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards b26f8965d5 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 4746cb892b 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards ef361631b6 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 20ba23c51f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 4dcea8b397 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 1275069f0f 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 87a02a825f 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards acca7ee411 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards ed4ce8f95c 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 8db084f071 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards b6f1505030 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 3d7ea2ed57 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 7e2839bcfc 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 0669215dd4 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards c39c3e41de 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards d3cde1059f 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 6e0f39790b 121: onsuccess: #908: 1: Success after glibc: 2 commits discards a0479c9212 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 7dfc1ca785 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards bf051e19fa 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards a4fd3f9d8e 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 22c4badeb6 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards c6e3497344 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 2b1f8ac5fe 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 0cc836e4a0 113: onsuccess: #898: 1: Success after linux: 3 commits discards 403eb6a7a5 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 35503ad037 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 7b58f6d033 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards eb9b825df5 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 6093535e8f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 9de086c20b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards f1b405e147 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 47c5eb1605 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 2206872ae0 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards e1ba42435b 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 3bc36f906b 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards a0db735464 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 7918a6875b 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 5dadeb386f 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards a9468c2257 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards c3a1ca646f 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 2c2ae763ef 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards ff32047114 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 9cc824a667 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 1954f2d86b 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards aecf796dfc 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 53b53d9d4e 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 27c9ae6131 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 90ec675134 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 85eef90079 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards ed8454ff7a 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 7cdc07407e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards a39a797e10 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 1c4557c823 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards e5c0f7290d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards f7c1c7c5e8 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards a7146a41aa 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 81ce43a00d 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 8e99c9b876 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards a45c7d1484 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 5729110aa0 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards c5c8871a79 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 64e8d0b389 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 3bbb7649e0 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards d65032ad74 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 4e870e855e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards ac8c5ffe77 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 83600c6e16 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards acec55e8b4 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 7c12b52640 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 04caed3442 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 6c3a6df73d 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 3969c33284 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 43db386afe 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 47ad225b5f 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards d067874807 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 1af4d5efb7 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 3c924ae303 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards c89cdb74ca 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 84a7001223 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 442889ab4e 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 33e2331375 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards c13d9c992c 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 54466f8418 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 502cf77569 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 5bd838715a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 77b76a7ff8 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new cc53a9cda6 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 4891af1b07 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 706375dc9a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 5f1c93449f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new c1fc03c0a1 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 301c7c9983 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 8f590660e8 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 797c4e3d48 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 384d55235b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 04cc68d779 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new fd01c411ac 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 540841311f 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new caa2d8c12c 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 0e5365f559 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new a6914bc109 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 35e01e384d 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new a8b548c377 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new efece980bc 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 636ab6a2f9 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 5d76f078da 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 4550021474 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 9b27a5a0be 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 355c1a8663 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new ae4256b774 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new cf83321dde 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new d83c9629ec 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 1ed3fae768 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 143d10a7bf 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new aa46e9e6b4 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 0d85e79be3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new d36a435990 89: onsuccess: #864: 1: Success after binutils: 25 commits new 816ece10be 90: onsuccess: #867: 1: Success after binutils: 4 commits new 1c926a38bb 91: onsuccess: #870: 1: Success after binutils: 5 commits new 18e8f18501 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 8644e70f30 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new ee992993b1 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 2c252b5d93 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new c445d9299d 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 80c50d6158 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new f9910ff3dc 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 671dc336a0 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 04238d553c 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 8b8ae7234f 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 087db42396 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new e697ca32d6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new a772b9c709 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new ae5f661971 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 9dacf72032 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 36d613cf11 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new ac7ab55b28 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d338ad6518 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 83f7423952 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new d7ed168ced 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 3a464c462d 112: onsuccess: #896: 1: Success after binutils: 24 commits new e816eaead1 113: onsuccess: #898: 1: Success after linux: 3 commits new 12b850000f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 22320909a3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 564f9b278f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 95ac47b137 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 2a5929f1a1 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 5e502afccc 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new c39ed9ef89 120: onsuccess: #906: 1: Success after binutils: 29 commits new 6d51d3641d 121: onsuccess: #908: 1: Success after glibc: 2 commits new e330142e52 122: onsuccess: #909: 1: Success after linux: 2753 commits new f8d7bfcb29 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new b6d34acd8a 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 28191abe99 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new ff5ae9eb8d 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new af11fb13c1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 26f809b110 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new f47c19e6ed 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new b0b563637c 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 550481d054 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new c6f96ddb55 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 427c449297 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 87861cf37a 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 26241120c5 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new f31fa9d513 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new b70d1d8569 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new df7eb73d86 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new d9e52c59fe 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 9d6108836c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 95e3c10660 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 3d8ecb22ee 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new c2a5d96d11 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new f3ec1c2ddc 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 1e5e69b6cb 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new f099331448 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 0fc799375a 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 5e59eaca9b 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 025de609ae 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new 287abc1840 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new 1440eed5e3 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new cb5728bf1b 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 0b229e5135 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 6b57867da5 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new 5a8697f58c 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new 70080a9f81 156: onsuccess: #949: 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 (bc07bffbad) \ 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 1756 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39652 -> 39156 bytes 04-build_abe-gcc/console.log.xz | Bin 214212 -> 212996 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8844 -> 8924 bytes 07-build_abe-glibc/console.log.xz | Bin 244744 -> 245592 bytes 08-build_abe-gdb/console.log.xz | Bin 39260 -> 38696 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2436 -> 2424 bytes 11-check_regression/console.log.xz | Bin 15452 -> 25448 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 39 +- 11-check_regression/mail-body.txt | 116 +- 11-check_regression/results.compare | 62 +- 11-check_regression/results.compare2 | 3497 ++++++++-- 11-check_regression/results.regressions | 62 +- 12-update_baseline/console.log | 60 +- 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 | 118 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 62 +- sumfiles/gdb.log.xz | Bin 1951640 -> 1969224 bytes sumfiles/gdb.sum | 10634 +++++++++++++++++++++--------- 30 files changed, 10639 insertions(+), 4061 deletions(-)