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 55af42f02c1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards dfe0bd9ad0d 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards d03a3809256 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 1107584579a 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 8585e77da39 113: onsuccess: #898: 1: Success after linux: 3 commits discards 48e728fc8ae 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 45d978aef04 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 7b0869e29e6 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 05977ad1508 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 5be0adc6738 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards a32c6b427e7 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 599b401166b 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 1dca1f1ab39 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards 89723433075 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 566673dd5b6 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 52be5204b3a 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 9ac9b82009e 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 0a2dbdc84f6 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 7f9de7fabd6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards c4fd27a0ddd 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 43338d496cf 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards b0077ab8f50 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 69c100c3d09 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 858deb36e4d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards f2ae4c3aae9 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 894544bf9cc 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards b880f945ec5 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 3dbd830c12d 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 9a843214bcd 89: onsuccess: #864: 1: Success after binutils: 25 commits discards b4df038adeb 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 67a98358aba 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 2f544290145 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 2d194ec1599 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 04f7e1f95cf 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards b174fe853fc 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 8500a2d0f13 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards e9faf111b94 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards f5ce8f4e2cb 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards fc3a68eb82c 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 5df194d256a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards a927cd973bc 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards d08f987afd9 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 6689e478265 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 3aeb33a6d5a 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards ef1dd90a872 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 6856f8ed5d1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 4c75992b4e0 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 02eddb576d5 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 5646ab1575b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 4a7dec337a9 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 1038749475a 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 1109c589198 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 7541cd6af80 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 2ff5975ea77 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 015aa1445dc 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 521d9b1ef1b 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards c814fc38ea0 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 8e1b1e68da9 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards a45beac880d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 48cddd9c7b8 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards c9e957fbbd3 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 273e4d9f757 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards f7d5cc572db 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 802c4ac9bb9 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 9552972e0b5 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards de95ab3e96e 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards a3fdf33c2fe 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards f698aa737d0 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards c662a6898d0 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards da27bc1d833 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 125fe9f13bb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 6dd8f02aede 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 83159e019eb 45: onsuccess: #815: 1: Success after binutils: 6 commits discards cf161ed628d 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards deb2c223ff3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards f45b125f535 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 813d53b60d8 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 7182402da12 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 4df407ffcda 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 064d1a3f91c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 338615c1798 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 4003f8efe05 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 3b056b5f1bd 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards f6710550f75 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 048e3bc4cde 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 40e803f8c11 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards e84736a6d43 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 32788008eee 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards eb413b368ed 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 931c8548140 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 9bba45cba7b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards fdea7ae9d78 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards 1fd8aa68d5a 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards ceef21a5c5e 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 90170d15b2a 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 882291c9030 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 75a47c01ac0 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 0fb3af28d72 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards ff2c29e72e6 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c0540799f74 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 446061f4f5f 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 45c2f1c2c6e 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9339caed597 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6e846e9aa51 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4ad5d71b77a 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 0857af93735 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new a92c629bce0 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 2396c62d0f0 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 8d7e07d66b2 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 0b32557e8a4 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 8b06e9b6740 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 0e2854a94d5 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 04c8a7b58e9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 850c2950abb 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new e632732dd51 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 73fd5447718 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 25469902132 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 0645552dc4b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new d6eea6a46c1 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new fd4c8b50017 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new b6e5c96b268 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new ca2c408aebf 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 4e4b1c02a3a 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new dad32ae933d 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new e92c53aeb4c 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 89ec3424f31 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 04ae5ca8641 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new be57e7e7148 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new fd1a45cccf4 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new dc4e9c0c2d8 45: onsuccess: #815: 1: Success after binutils: 6 commits new b2d0905f982 46: onsuccess: #818: 1: Success after binutils: 10 commits new 2ca60b64df5 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new c6f6dcdaa2d 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new cc5bb032c74 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new eb60b64964f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new f4ca5f6914b 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new c01383bebd9 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new e59115382da 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 87726b1c61e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new ed7ef0d8ac0 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new ccf9868b4ef 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 01029e04024 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new a767e695992 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 10859d6c0e4 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 0a64edd383e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 9a27aa6d7f1 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 7c5c0799776 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 5118edb5f4b 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new e74abb1d895 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 9e0d520dc46 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new c90c29caada 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 9b1bbd1b6a5 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 63e119564ef 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 8a608d68d0f 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 203c1eccf41 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 0ed9c343b7d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new cba56b89270 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 6e6376913fc 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new d05e961af83 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new e31451503a0 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 6d57f2e77e8 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 37d8e74f000 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 4964474ee48 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 9f6bf3a1e50 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 8f89233b32c 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2399a05a484 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 8a99567a507 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new a63f0cb649a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 5591b7aace9 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 795b600fc54 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 49211ff3363 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 0d4626fb18e 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new a35d11b83ad 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 8f386e5a2f9 89: onsuccess: #864: 1: Success after binutils: 25 commits new c7621f82bf3 90: onsuccess: #867: 1: Success after binutils: 4 commits new 9718cfeb7be 91: onsuccess: #870: 1: Success after binutils: 5 commits new 6364313562b 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new c9dfb823b73 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new cea4acff3a5 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 45a56708fc5 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new dc460c3d544 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 3c24fbb22fc 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 1bacfb2c2e5 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new bccea8976e4 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 8bcd2fdcb37 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new fd3fac4b326 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 69b0ebd33f7 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 7947fff0b82 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 3a245f0519f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 440cf464712 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new f10dc9e3da4 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 2334c6c7e01 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new b1ea62d8fa0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 9cee59df8a9 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new e092c2035e9 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 24e033176b4 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 8929eb22386 112: onsuccess: #896: 1: Success after binutils: 24 commits new f9201ee87cd 113: onsuccess: #898: 1: Success after linux: 3 commits new 39cced6f3c7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new db517bafeb6 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new bece1d8f55b 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new adad5d1f90b 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new a8f0b471d8b 118: onsuccess: #903: 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 (55af42f02c1) \ 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 1804 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40848 -> 39596 bytes 04-build_abe-gcc/console.log.xz | Bin 216956 -> 214268 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 246992 -> 242868 bytes 08-build_abe-gdb/console.log.xz | Bin 40780 -> 38960 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2960 -> 2120 bytes 11-check_regression/console.log.xz | Bin 12996 -> 20512 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 31 +- 11-check_regression/mail-body.txt | 134 +- 11-check_regression/results.compare | 61 +- 11-check_regression/results.compare2 | 3890 ++++++++++- 11-check_regression/results.regressions | 61 +- 12-update_baseline/console.log | 62 +- 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 | 136 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 61 +- sumfiles/gdb.log.xz | Bin 1860072 -> 1847748 bytes sumfiles/gdb.sum | 10906 ++++++++++++++---------------- 30 files changed, 9107 insertions(+), 6283 deletions(-)