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 0c77dc65cda 112: onsuccess: #896: 1: Success after binutils: 24 commits discards c8bdc6e47c6 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] discards e24ee60199e 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 0750f2cd821 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] discards 55d573332e0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards db3c6adfc9f 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 23c2ef85e26 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards f440447708a 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards fbf0a95679c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 63719f4c19d 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards b0230a6643b 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] discards b6b323b493e 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 3596f01111c 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 38ab1cfe869 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards b07c8e9e499 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] discards 082f91bb67e 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] discards 71864d6f317 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] discards 44c2ce4d2f9 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] discards a7b02cf966b 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] discards 68def7917f2 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] discards e9fb6a8070d 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] discards 6c12f6bc8f2 91: onsuccess: #870: 1: Success after binutils: 5 commits discards d385c78c64e 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 7b78bfc4d78 89: onsuccess: #864: 1: Success after binutils: 25 commits discards bcbd276fc08 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] discards b96333786d0 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] discards ae994b0b127 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] discards 7ab9a2e4e8a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] discards 1b6c34099b6 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] discards 612342cfd89 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] discards da05f23cd3b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] discards 9cdc0490706 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 97e771bbbd4 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 81f421328d7 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 4cfd7151c0f 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] discards dd4e8622d10 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] discards bb6d4eaa5a9 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] discards 7cb124f33c8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] discards 30f5c720efd 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] discards f1beaf19834 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] discards 0368cb4453e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] discards 4559cd33c33 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] discards 6a0bf962e71 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] discards dfb4f3bff6d 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] discards 093771220a3 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 55a61c39340 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] discards ca21bb939fb 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] discards c41344f2853 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 7aa2e6b32f8 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] discards 71c3a3c5caa 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] discards ca411192ff0 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] discards 94f50818410 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] discards 9fd0335e280 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] discards 464d4b395a7 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] discards 623b8252abf 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] discards c7d551cad89 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] discards 02b97769fe8 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 51be3092df7 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards b613a325055 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards efc07b74650 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 86b05d72656 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards ecc85badf10 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 06070ef7e24 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] discards 151418d81ad 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 41a2258e684 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 937563dd452 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 47124fecffb 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 5b0ac2bdd7f 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 9a451d5f75c 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards a940af46104 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] discards 60dd88e1c37 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards ad42e605a32 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] discards 22ea07792aa 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] discards c4f49065eb4 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 645e4305d9b 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] discards 6e949bee668 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] discards 176c1b0abe7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] discards 742d4ebfb25 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 1bae6db8431 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] discards c29bc18920c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards c5ba3690b64 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 10209fbd839 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] discards d4def2beab4 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 81806cb5c75 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] discards 87d5825cace 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 410f732df7b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] discards eefe89f08f4 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] discards c62895081fc 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards f931c20ba1a 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 36f689d2173 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] discards 8c76bc087ba 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] discards e9c0c2444f1 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] discards b6438aec083 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 18d6273a885 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 2c92b49b158 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9554a08dcc8 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards e0ed4a5008d 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] discards 5cd208d8311 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 609d79d32f4 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 328ede7d02d 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0d268e76f16 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new daea9f6d3c9 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 68ef9d0f029 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 7845b90663a 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 2c9b1269f52 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 80372c445f0 16: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 7c422764657 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 629fe62fced 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 64c01b3b1a0 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 002310744a5 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 313069dd94c 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 [...] new f5194dbf17e 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 [...] new 931e9d44e0c 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gd [...] new 0d130726e4b 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new aea447d0ba3 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 4c146d99226 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gd [...] new 0836f310f9a 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gl [...] new 14b2de3cfc3 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 2b8ac279acf 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gd [...] new c9c8e345b81 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 2df1635b6d4 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gl [...] new 50f3403c486 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 5d4d6954975 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 988d119d265 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gd [...] new 0b50e1d2d41 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new ec5acba8420 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gd [...] new e93790ac024 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gd [...] new c5591821927 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gd [...] new 3529e67d699 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 125414c7dca 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gl [...] new ff3daba0ee9 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gl [...] new 9399dfe36c3 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 0cbfbb5feeb 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gd [...] new 0bcaf6aa8ff 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 9ddaf0597de 45: onsuccess: #815: 1: Success after binutils: 6 commits new a746905495b 46: onsuccess: #818: 1: Success after binutils: 10 commits new 81035bac135 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 924573e0579 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 2bc25c9490d 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new dd4b782ee76 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gd [...] new 3f6e601b853 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new ba4ce4ecc02 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new e024a04b1ef 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 720604bd56e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 5fbe73a6f6e 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 05eb35fe097 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 69c2d43292a 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gl [...] new cbf5caa80fd 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gd [...] new 6aab360fe87 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gl [...] new d7ffb32cc35 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gd [...] new ba0ebacdd57 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gl [...] new 3be1905610d 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gl [...] new 6862b820aa4 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gd [...] new 715e8c2b5f6 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gl [...] new 897535f094b 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 37135c1ef27 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gd [...] new 8febcb7c6e8 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gl [...] new b61696035eb 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 749fe408fae 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gd [...] new 2b935d22eae 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gd [...] new 218c0b13885 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gl [...] new 0a1423d3faf 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gl [...] new ad5f27ac3af 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gl [...] new 4ded441e9ae 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gl [...] new ca386b00a91 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gl [...] new a0248cb10a2 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gd [...] new 3501880ca1c 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gl [...] new dbd53fe0bdd 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gl [...] new ad689a66bec 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 94d097e886e 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new c3ee17c2309 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 9d32300f39e 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gl [...] new 93f21ff56ec 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gd [...] new 6492f92fe75 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gd [...] new 52ac3e5e32c 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gl [...] new 42d23dce2e6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gl [...] new 2b0a15cebf8 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gl [...] new 6a95846b7c1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gl [...] new b161d46695c 89: onsuccess: #864: 1: Success after binutils: 25 commits new 4b8214179b3 90: onsuccess: #867: 1: Success after binutils: 4 commits new a264b76a612 91: onsuccess: #870: 1: Success after binutils: 5 commits new 019f079c263 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gl [...] new 1634ca93137 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gd [...] new 5fb134668f5 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gd [...] new 856671d1cff 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gl [...] new ad6c27cba24 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gd [...] new c9d0275b3c8 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gd [...] new 595d6f488bf 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gd [...] new 9422f2ef293 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 3ac76410979 100: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 615adda481d 101: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new c70c0c709fc 102: onsuccess: #883: 1: Success after binutils/gcc/linux/g [...] new 2cbf3aa4dba 103: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new df116a7650f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 63e6b1064a4 105: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 92859fcf654 106: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new ead2954b29d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new fae0e07e10a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 04c27f7f45f 109: onsuccess: #890: 1: Success after binutils/gcc/linux/g [...] new 4f1e7ad92cc 110: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 14bdc94f7a8 111: onsuccess: #893: 1: Success after binutils/gcc/linux: [...] new 190e3a240cc 112: onsuccess: #896: 1: Success after binutils: 24 commits new d5c76dfc2ba 113: onsuccess: #898: 1: Success after linux: 3 commits

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 (0c77dc65cda) \ 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 1684 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 38996 -> 40012 bytes 04-build_abe-gcc/console.log.xz | Bin 213780 -> 216424 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8416 -> 8916 bytes 07-build_abe-glibc/console.log.xz | Bin 244392 -> 247268 bytes 08-build_abe-gdb/console.log.xz | Bin 38840 -> 40748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 4000 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2132 -> 2156 bytes 11-check_regression/console.log.xz | Bin 8496 -> 12208 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 44 +- 11-check_regression/mail-body.txt | 153 +- 11-check_regression/results.compare | 85 +- 11-check_regression/results.compare2 | 2816 ++++++++++-- 11-check_regression/results.regressions | 85 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 155 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 85 +- sumfiles/gdb.log.xz | Bin 1922068 -> 1864344 bytes sumfiles/gdb.sum | 7132 ++++++++++++++----------------- 27 files changed, 6219 insertions(+), 4424 deletions(-)