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 4c82651904 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 1fbb85d6d3 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 0b0b1c029e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 4a5d0c4bfb 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 9c87cb3e9c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 662055e0cd 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards fd21d2c1e4 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards cccbf445f6 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 11501d8243 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards ad10244e0d 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 54767ca56f 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 7f6da679a4 121: onsuccess: #908: 1: Success after glibc: 2 commits discards e1590d9069 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 2188191cc9 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 24fe3bc930 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards ca1588d37b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 232525dcef 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 9669d4af69 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 909b3c9685 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 1420d68ea6 113: onsuccess: #898: 1: Success after linux: 3 commits discards 2d4df4c321 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 919cfd0cc9 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 092c15e10d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards e137d9a7f1 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 5a17d0f695 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards d0d1d1ca01 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 583ee9602e 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5138d26c7f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards f3a91db686 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 166759e503 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards cf1fe1bf37 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 98a68171d3 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 5faa341734 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 5989301084 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 79e0b213c8 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards da57026b78 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards c1bee80025 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 9cfe459bad 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 935bea6e42 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 0a547adc4b 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 8a14ab3531 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards e4714c2a1c 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 8242e6b414 90: onsuccess: #867: 1: Success after binutils: 4 commits discards bdc40425d8 89: onsuccess: #864: 1: Success after binutils: 25 commits discards f14f0ddae7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 15fe23e98e 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards fe056b4dc5 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 1c9ee422df 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 19d55c4533 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 0938bb40c7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 9b737b6ce6 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards f8bd565d1b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards b09aea5494 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 417019b146 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards d91da83556 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 29e389896a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards da46239853 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 6b3d2fa426 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards e4d3aff4fd 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 695c0c24cc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 4814af3524 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards c3e3475dfa 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 8f6a7042e1 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 0c93bd147f 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 41913bc587 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 98071d6f84 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards eff632d1f9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards bf24fe152a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 1c6cab2fa9 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 7b8028e7fa 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards ecbdc1e99f 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards d4fb9f1ef1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 7de1eefbdb 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 858f6ec34e 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards c7d1a318e9 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards c01a728672 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 0fd29d9526 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 551fd253d8 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 214ca7d270 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards d62cd270dc 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 515736b144 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 89d0819fcb 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 8fd0d2e183 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards df88a7d1b2 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 51ffa5b2fb 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards b7f7a4ca47 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 85b8469064 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 6d705f4be8 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 6b2681ec0b 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 982a2bd066 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards c4ee8f5474 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 87bf851867 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 974951557b 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards b08562e2d0 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards d2dfd71ff6 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 577618bc2c 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 2b1699a0f7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 043b84fbbb 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 2d562f2597 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards d38f1c24df 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards fa9d2c7c5e 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new c65618c67c 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 9d4a7e8d7b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new b3bb80352e 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new c1696056e9 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 0d2b218f4f 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 889bd0632f 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 22232eb256 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 5b124b0eb4 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 78116184c9 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new eb3a7829fa 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new f970eabcf1 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new d53e4a557d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new ed631d59af 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 52f63c5428 45: onsuccess: #815: 1: Success after binutils: 6 commits new 992990f438 46: onsuccess: #818: 1: Success after binutils: 10 commits new a16d07208c 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 1dd3937455 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 8b44584c47 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new d1530ba187 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 934b2bee3d 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new f0fa8f8c53 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new f07a23f22d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 1f530e82ed 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 011e34d103 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new d8ac8549c7 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new fd715cbe9b 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new ada639dee8 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 45dd63501c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new e5687c83d4 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 295329a512 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 4852bf0939 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 0469a5eecf 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 06ea9588c0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 064d5186df 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 3cad2a8cc1 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 930045b55e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new f6f5acfd6c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 9dec99e855 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 0d43054df1 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 6a7f10335b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new c2d5d6adfc 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new fc8de97424 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new e68f506aae 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 3e42962f19 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 0ed589d7a8 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 58a24f747d 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 7495188efb 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new fd1d4004f1 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new df24cacd03 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 77d7020c4c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 1947663a07 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 3c686f6b1c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 6865804544 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new f784fd962d 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 832d22066c 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 7beb3bfc21 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 84724da6c2 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new f88357dd53 89: onsuccess: #864: 1: Success after binutils: 25 commits new 7bd931fb9b 90: onsuccess: #867: 1: Success after binutils: 4 commits new 85db247b43 91: onsuccess: #870: 1: Success after binutils: 5 commits new 4d4bfbc641 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 77b8569a10 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 22b7114139 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 6459b1141f 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new d9a09daa08 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 9d47ceb450 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new ce1b0071d2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 961c3e3294 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 00586328e9 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 0b837d3e2c 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new f9255c8a77 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 99295083d9 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 1382698080 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new ea9ed9177f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new b0c6043cf2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 0f7339b33a 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 3d6d25e1df 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 9cab28564d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 8e536331b7 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 13874d9830 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new ebd99c52ef 112: onsuccess: #896: 1: Success after binutils: 24 commits new 7bce1241e2 113: onsuccess: #898: 1: Success after linux: 3 commits new e825b4db1c 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new a74a7a8e85 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new f0905de8e2 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new e25e70e578 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 72e5cd99da 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 468ad398ac 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new ab2ce7f7c1 120: onsuccess: #906: 1: Success after binutils: 29 commits new ba487c8e97 121: onsuccess: #908: 1: Success after glibc: 2 commits new 4a0a11c4c5 122: onsuccess: #909: 1: Success after linux: 2753 commits new 8892194822 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 2db9990854 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 5bca96dcd6 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new fd291e0cc8 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 2ad2eb4da6 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 84a092ca05 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 003e9be1ed 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 9a7485ae02 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new dab0f8bee2 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 88865af0f5 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 8a7e5638eb 133: onsuccess: #920: 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 (4c82651904) \ 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 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39980 -> 40100 bytes 04-build_abe-gcc/console.log.xz | Bin 215820 -> 216240 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8692 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 245000 -> 245652 bytes 08-build_abe-gdb/console.log.xz | Bin 39396 -> 39596 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2128 -> 2272 bytes 11-check_regression/console.log.xz | Bin 11276 -> 12764 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 52 +- 11-check_regression/mail-body.txt | 204 +- 11-check_regression/results.compare | 96 +- 11-check_regression/results.compare2 | 3967 ++++++++++++------ 11-check_regression/results.regressions | 96 +- 12-update_baseline/console.log | 64 +- 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 | 206 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 96 +- sumfiles/gdb.log.xz | Bin 1947788 -> 1886960 bytes sumfiles/gdb.sum | 6866 ++++++++++--------------------- 30 files changed, 5184 insertions(+), 6513 deletions(-)