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 50110757368 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards 764e4a06f6a 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 9060e969077 113: onsuccess: #898: 1: Success after linux: 3 commits discards 5a2f1e4f5b1 112: onsuccess: #896: 1: Success after binutils: 24 commits discards fb26730c066 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards ca48dd00909 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 7e574b63248 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 6edb2272d10 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards 36fa7cc7008 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards cd8ea7adc81 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 88a8c271cf1 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards c1d889755f0 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 0bc2804e4c9 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 8356b481f73 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards eed50de65ac 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 04772f9789f 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 2eace5010f9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards dfdf8f1da06 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 9e5079e7889 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 3d76f6649d6 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards fda1603e1f8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards c6b0c06ce14 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 2640631133c 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards b8e1b87670f 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 3ed75ff011c 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 7438838f0ca 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 918533e923a 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 9b98c6a4307 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards c42fd89cf86 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards c56d609b31b 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards c6b04e0aede 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 7ff949284f7 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 7b73ef57f1e 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 477eab3e737 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 25048cff141 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards b0c5d81ad03 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards e6d622cd9a6 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 3eeb9a7798b 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards b4add76f2ab 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards 8423bed23da 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 73ce5475bf2 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards d6b961a98b9 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards 091c65c3ec4 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 8619e8890fc 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards cf55ee8ad31 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards a5e8b831d30 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards f43ae63e89f 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards aa4596f3d45 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 3020b1c16df 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 219916799d9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards c1ce05f1e9a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards d2ec8834e4a 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards b99fb26aa4d 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 7762fef59c4 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 79721912d7a 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards e3b6e4f3ee8 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards e30b609ddc0 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards ea568d1606f 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 9c8651e8e42 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 1886689c33e 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards f36a94a05ca 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 4cc8c84b35e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 38a15fed99e 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards bceebb6dba1 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 7eca6b8107c 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 7bbe7e7c582 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards d01dfd9cbc2 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 479f6f544e1 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 378a8f985d5 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 82b8bce49dc 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 4ec19e485c0 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 4c486c8c8f3 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards f5293a8740e 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 1ea0cd2c5dc 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 050b62b7749 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards ff20e61e059 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 48771e31b89 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards d3c160a7a1a 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 3c7062bc92b 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 54859ba20e8 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 6e4823e4de5 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 9fd0e551d5f 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 9a3d29daa22 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards ce55208a6b7 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards ec1066f578b 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards 13557c0e2a3 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 1cc1cbc5e0a 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 3713ceb4c87 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 8a507e1cece 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards fc630c65f02 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards b8556932339 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 16d7faf0313 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards eb09f4f2365 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 5ef72b08c69 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards a9082f2a80a 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 697f9af4c7e 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards f4fd96f043b 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 95670eaebfc 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a22f52b8c0f 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 70550ef9554 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards b85f6eb378a 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new edd10869a30 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6c79a7870ae 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new a82a6928cab 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ad96d452a13 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 71de4b94cbe 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 5c10e7b2807 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 11f5cabe986 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 47c35c7a38e 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 2a67166c1ca 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 7515f0a8a36 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new b933e11375a 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new e91b3b00d1a 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 487863e448f 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new a142d129d63 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new f4388ae5a39 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 1d173fee3a8 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 33e0c320528 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new c3fdaa2c677 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new ad4acb22f9e 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new bd730219112 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 76d512c4b80 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new b4070b09f09 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new 4755befe8eb 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new 2741fe667bd 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new cd63c31318e 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 44769232c94 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 23539344e57 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new f6b3dcc4b56 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 9f12ae9b9a3 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 27901b0cd31 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new e0a98e8064b 45: onsuccess: #815: 1: Success after binutils: 6 commits new 62c6d306846 46: onsuccess: #818: 1: Success after binutils: 10 commits new 47cdaf4ca0a 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 94fb18cf8c7 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 5c247e70589 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new cf07ec11f6a 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 0990429cdb2 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 9dd3201e298 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 7c47592175e 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new b03d03cabc8 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new de9fafc1a07 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 42d5f137aae 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new f8410f86fe2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new bf6011717b1 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 9588658df72 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new a27f3061a7f 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new 5ce02b44f82 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 57674ffe09c 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 8da6160e4b2 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 319c4d3f152 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new b5628524c9a 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 0c7c3b1df15 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 2097e9c0af8 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 29926ed2bc9 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 8ab427e34d7 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 817e4abccbf 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new be1d412a5b1 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new f8b429eb2e8 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 9341ba24dab 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 8229c4b5d86 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new ee9dbff490b 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 02693153e1f 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 4152f301d5a 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 40f5ff08503 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new ec2a3cfeb75 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 84d33388f5f 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 30c4d5998d6 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new be78c7fb7c1 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 495a5b15f86 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 422fd69cabd 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new a5430412f66 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new edbdefbab24 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 85e086becd0 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 885fd4ae7d7 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new d6418269223 89: onsuccess: #864: 1: Success after binutils: 25 commits new f3824f9c990 90: onsuccess: #867: 1: Success after binutils: 4 commits new c240c8beeeb 91: onsuccess: #870: 1: Success after binutils: 5 commits new 5cf930eb346 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 4b3b12f16c1 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 5f53b6c5687 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new b1870d56f5a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new 1082a8a1862 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new 0a822ffdeaf 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 3490c09bd56 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new fad77287c07 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 6397f68a425 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 9e85c87b12d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new ad0dd9c7155 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new c7a43e975ff 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new c7d98880011 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 0c5395d62b3 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 1e46cc37683 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 75c669d5bb3 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new a1e1f68c087 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new b83bce98317 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 82062370428 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 0db5a83e25b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 9753c30dc93 112: onsuccess: #896: 1: Success after binutils: 24 commits new 95e96ecde2b 113: onsuccess: #898: 1: Success after linux: 3 commits new 253d048c6d7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 5cfa94992a7 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new f0e3534a54c 116: onsuccess: #901: 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 (50110757368) \ 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 1748 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39172 -> 38908 bytes 04-build_abe-gcc/console.log.xz | Bin 213820 -> 213680 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8476 -> 8864 bytes 07-build_abe-glibc/console.log.xz | Bin 243528 -> 243712 bytes 08-build_abe-gdb/console.log.xz | Bin 38508 -> 38632 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2072 -> 2028 bytes 11-check_regression/console.log.xz | Bin 9520 -> 16104 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 29 +- 11-check_regression/mail-body.txt | 124 +- 11-check_regression/results.compare | 56 +- 11-check_regression/results.compare2 | 3129 +++++++++++- 11-check_regression/results.regressions | 56 +- 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 | 126 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 56 +- sumfiles/gdb.log.xz | Bin 1867864 -> 1950092 bytes sumfiles/gdb.sum | 8257 +++++++++++++++++++++++-------- 31 files changed, 9428 insertions(+), 2525 deletions(-)