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 d5c76dfc2ba 113: onsuccess: #898: 1: Success after linux: 3 commits discards 190e3a240cc 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 14bdc94f7a8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards 4f1e7ad92cc 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 04c27f7f45f 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards fae0e07e10a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards ead2954b29d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 92859fcf654 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards 63e6b1064a4 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards df116a7650f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 2cbf3aa4dba 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards c70c0c709fc 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards 615adda481d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 3ac76410979 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 9422f2ef293 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 595d6f488bf 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards c9d0275b3c8 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards ad6c27cba24 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 856671d1cff 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards 5fb134668f5 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 1634ca93137 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards 019f079c263 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards a264b76a612 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 4b8214179b3 90: onsuccess: #867: 1: Success after binutils: 4 commits discards b161d46695c 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 6a95846b7c1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards 2b0a15cebf8 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards 42d23dce2e6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 52ac3e5e32c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 6492f92fe75 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 93f21ff56ec 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards 9d32300f39e 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards c3ee17c2309 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 94d097e886e 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards ad689a66bec 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards dbd53fe0bdd 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards 3501880ca1c 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards a0248cb10a2 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards ca386b00a91 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 4ded441e9ae 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards ad5f27ac3af 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 0a1423d3faf 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 218c0b13885 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 2b935d22eae 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards 749fe408fae 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards b61696035eb 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 8febcb7c6e8 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards 37135c1ef27 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards 897535f094b 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 715e8c2b5f6 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 6862b820aa4 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards 3be1905610d 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards ba0ebacdd57 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards d7ffb32cc35 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 6aab360fe87 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards cbf5caa80fd 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards 69c2d43292a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 05eb35fe097 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 5fbe73a6f6e 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 720604bd56e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards e024a04b1ef 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards ba4ce4ecc02 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 3f6e601b853 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards dd4b782ee76 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 2bc25c9490d 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 924573e0579 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 81035bac135 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards a746905495b 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 9ddaf0597de 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 0bcaf6aa8ff 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 0cbfbb5feeb 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 9399dfe36c3 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards ff3daba0ee9 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 125414c7dca 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards 3529e67d699 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards c5591821927 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards e93790ac024 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards ec5acba8420 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 0b50e1d2d41 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 988d119d265 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards 5d4d6954975 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 50f3403c486 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 2df1635b6d4 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards c9c8e345b81 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 2b8ac279acf 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 14b2de3cfc3 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 0836f310f9a 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards 4c146d99226 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards aea447d0ba3 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 0d130726e4b 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 931e9d44e0c 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards f5194dbf17e 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards 313069dd94c 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards 002310744a5 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 64c01b3b1a0 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 629fe62fced 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 7c422764657 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 80372c445f0 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 2c9b1269f52 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 7845b90663a 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 68ef9d0f029 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a8b4ceba186 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2044c3f771d 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 458d35bf15f 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 14ca641cdc4 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 087d49c13bc 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 13469926b16 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ccc557cff0f 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 970ee4dc14a 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 23c71756c56 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new 06c0bb136c0 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 77e2c469a61 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new c3f74c1731e 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new bb91c7c5fb5 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new c2533f265c1 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 2c511d76d8e 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 55374301559 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 7758bacc8d1 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new 0b3aac5aa48 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 2e38a67ed4c 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 445162d5881 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 360c1914e35 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new ff0ab3fddde 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new ed743667702 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 3769fcb77e7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new a4c1c9f6c46 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new f8f3a55956c 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 7b113dfc528 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 3bdbda7585a 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new 2e2025c49b0 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 0d764366357 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new b3238b10901 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 68382266702 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 0cc81732d79 45: onsuccess: #815: 1: Success after binutils: 6 commits new 1ee73fec53e 46: onsuccess: #818: 1: Success after binutils: 10 commits new 73cecda6e51 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 72efde8a878 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new f7bf35e0b14 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 7d6af74a007 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 58831cfe3a7 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 5825a7be819 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 227e24ba126 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 15325508f1a 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 635b96fbe83 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new fa8ec981a92 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 97b6c17e1e6 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new 9b1af0314ab 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 66712baf6ea 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new 9589b1893e5 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new f2403866ed6 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 2cf63c033fb 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 0ad05c7334e 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 175b4d2e5f7 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new d8638452e82 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 4c7d1a59cd5 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 72904d04e2d 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new 69926d4391a 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 64896c65e61 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 3e5c86b8246 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 628a14db019 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 626040662c8 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new 9509125d339 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new fc45b7647f3 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new 2e92b243dad 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new 2b63a081621 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new f783e2d60f8 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new 5e5ebee0e3a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new 67a81e015ce 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 284dcccbf80 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 6e68f18bdc5 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 90499166e9f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 0fe4439f1bb 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new d9cef9c478c 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new f96c6724cac 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 97de769a153 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 12cbae9d972 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new dfd8d5fdf24 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new 0d7b5a475d7 89: onsuccess: #864: 1: Success after binutils: 25 commits new 94fa02af736 90: onsuccess: #867: 1: Success after binutils: 4 commits new d5a9191978b 91: onsuccess: #870: 1: Success after binutils: 5 commits new 2e76a5f9876 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 71c6bd43a3f 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new d2021398dd7 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 133b87338f8 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new b97b6280f9b 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new e0469971f33 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 2691677253d 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new a335e64583d 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 4844a540e78 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new dce3c9980cb 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 2b6b711e859 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new ceb34d6730e 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new dd3b92b270c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new c427449dc14 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new eed425caac1 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new b4fe4c55535 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 889f913a3db 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 2b8ea08d5b4 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 544a28fca08 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 4400839b5a6 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new e378c3645f0 112: onsuccess: #896: 1: Success after binutils: 24 commits new 6cc47461529 113: onsuccess: #898: 1: Success after linux: 3 commits new f34e8fee969 114: onsuccess: #899: 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 (d5c76dfc2ba) \ 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 1724 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 40012 -> 39932 bytes 04-build_abe-gcc/console.log.xz | Bin 216424 -> 215132 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8916 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 247268 -> 243808 bytes 08-build_abe-gdb/console.log.xz | Bin 40748 -> 38996 bytes 09-build_abe-dejagnu/console.log.xz | Bin 4000 -> 3896 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2156 -> 2108 bytes 11-check_regression/console.log.xz | Bin 12208 -> 15564 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 171 +- 11-check_regression/results.compare | 86 +- 11-check_regression/results.compare2 | 4498 ++++++++++------- 11-check_regression/results.regressions | 86 +- 12-update_baseline/console.log | 58 +- 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 | 173 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 86 +- sumfiles/gdb.log.xz | Bin 1864344 -> 1925804 bytes sumfiles/gdb.sum | 8008 ++++++++++++++++--------------- 31 files changed, 7229 insertions(+), 6028 deletions(-)