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 f34e8fee969 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 6cc47461529 113: onsuccess: #898: 1: Success after linux: 3 commits discards e378c3645f0 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 4400839b5a6 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 544a28fca08 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 2b8ea08d5b4 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 889f913a3db 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards b4fe4c55535 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards eed425caac1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards c427449dc14 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards dd3b92b270c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards ceb34d6730e 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 2b6b711e859 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards dce3c9980cb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 4844a540e78 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards a335e64583d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 2691677253d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards e0469971f33 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards b97b6280f9b 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 133b87338f8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards d2021398dd7 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 71c6bd43a3f 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 2e76a5f9876 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards d5a9191978b 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 94fa02af736 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 0d7b5a475d7 89: onsuccess: #864: 1: Success after binutils: 25 commits discards dfd8d5fdf24 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 12cbae9d972 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 97de769a153 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards f96c6724cac 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards d9cef9c478c 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 0fe4439f1bb 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 90499166e9f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 6e68f18bdc5 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 284dcccbf80 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 67a81e015ce 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 5e5ebee0e3a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards f783e2d60f8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 2b63a081621 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 2e92b243dad 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards fc45b7647f3 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 9509125d339 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 626040662c8 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 628a14db019 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 3e5c86b8246 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 64896c65e61 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 69926d4391a 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 72904d04e2d 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 4c7d1a59cd5 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards d8638452e82 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 175b4d2e5f7 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 0ad05c7334e 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 2cf63c033fb 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards f2403866ed6 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 9589b1893e5 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 66712baf6ea 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 9b1af0314ab 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 97b6c17e1e6 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards fa8ec981a92 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 635b96fbe83 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 15325508f1a 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 227e24ba126 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 5825a7be819 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 58831cfe3a7 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 7d6af74a007 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards f7bf35e0b14 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 72efde8a878 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 73cecda6e51 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 1ee73fec53e 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 0cc81732d79 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 68382266702 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards b3238b10901 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 0d764366357 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 2e2025c49b0 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 3bdbda7585a 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 7b113dfc528 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards f8f3a55956c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards a4c1c9f6c46 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 3769fcb77e7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards ed743667702 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards ff0ab3fddde 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 360c1914e35 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 445162d5881 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 2e38a67ed4c 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 0b3aac5aa48 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 7758bacc8d1 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 55374301559 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 2c511d76d8e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards c2533f265c1 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards bb91c7c5fb5 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards c3f74c1731e 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 77e2c469a61 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 06c0bb136c0 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 23c71756c56 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 970ee4dc14a 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards ccc557cff0f 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 13469926b16 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 087d49c13bc 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 14ca641cdc4 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 458d35bf15f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2044c3f771d 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 38799586172 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b85f6eb378a 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 70550ef9554 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new a22f52b8c0f 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 95670eaebfc 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f4fd96f043b 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 697f9af4c7e 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new a9082f2a80a 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 5ef72b08c69 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new eb09f4f2365 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 16d7faf0313 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new b8556932339 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new fc630c65f02 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 8a507e1cece 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 3713ceb4c87 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 1cc1cbc5e0a 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 13557c0e2a3 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new ec1066f578b 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new ce55208a6b7 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 9a3d29daa22 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 9fd0e551d5f 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 6e4823e4de5 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 54859ba20e8 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 3c7062bc92b 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new d3c160a7a1a 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 48771e31b89 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new ff20e61e059 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 050b62b7749 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 1ea0cd2c5dc 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new f5293a8740e 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 4c486c8c8f3 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 4ec19e485c0 45: onsuccess: #815: 1: Success after binutils: 6 commits new 82b8bce49dc 46: onsuccess: #818: 1: Success after binutils: 10 commits new 378a8f985d5 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 479f6f544e1 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new d01dfd9cbc2 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 7bbe7e7c582 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 7eca6b8107c 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new bceebb6dba1 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 38a15fed99e 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 4cc8c84b35e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new f36a94a05ca 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 1886689c33e 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 9c8651e8e42 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new ea568d1606f 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new e30b609ddc0 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new e3b6e4f3ee8 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 79721912d7a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 7762fef59c4 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new b99fb26aa4d 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new d2ec8834e4a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new c1ce05f1e9a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 219916799d9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 3020b1c16df 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new aa4596f3d45 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new f43ae63e89f 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new a5e8b831d30 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new cf55ee8ad31 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 8619e8890fc 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 091c65c3ec4 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new d6b961a98b9 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 73ce5475bf2 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 8423bed23da 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new b4add76f2ab 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 3eeb9a7798b 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new e6d622cd9a6 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new b0c5d81ad03 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 25048cff141 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 477eab3e737 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 7b73ef57f1e 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 7ff949284f7 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new c6b04e0aede 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new c56d609b31b 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new c42fd89cf86 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 9b98c6a4307 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 918533e923a 89: onsuccess: #864: 1: Success after binutils: 25 commits new 7438838f0ca 90: onsuccess: #867: 1: Success after binutils: 4 commits new 3ed75ff011c 91: onsuccess: #870: 1: Success after binutils: 5 commits new b8e1b87670f 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 2640631133c 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new c6b0c06ce14 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new fda1603e1f8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 3d76f6649d6 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 9e5079e7889 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new dfdf8f1da06 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 2eace5010f9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 04772f9789f 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new eed50de65ac 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 8356b481f73 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 0bc2804e4c9 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new c1d889755f0 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 88a8c271cf1 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new cd8ea7adc81 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 36fa7cc7008 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 6edb2272d10 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 7e574b63248 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new ca48dd00909 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new fb26730c066 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 5a2f1e4f5b1 112: onsuccess: #896: 1: Success after binutils: 24 commits new 9060e969077 113: onsuccess: #898: 1: Success after linux: 3 commits new 764e4a06f6a 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 50110757368 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...]

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 (f34e8fee969) \ 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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39932 -> 39172 bytes 04-build_abe-gcc/console.log.xz | Bin 215132 -> 213820 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8476 bytes 07-build_abe-glibc/console.log.xz | Bin 243808 -> 243528 bytes 08-build_abe-gdb/console.log.xz | Bin 38996 -> 38508 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2108 -> 2072 bytes 11-check_regression/console.log.xz | Bin 15564 -> 9520 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 154 +- 11-check_regression/results.compare | 68 +- 11-check_regression/results.compare2 | 4864 +++++++--------------------- 11-check_regression/results.regressions | 68 +- 12-update_baseline/console.log | 60 +- 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 | 156 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 68 +- sumfiles/gdb.log.xz | Bin 1925804 -> 1867864 bytes sumfiles/gdb.sum | 5278 +++++++++++++------------------ 31 files changed, 3463 insertions(+), 7333 deletions(-)