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-arm in repository toolchain/ci/base-artifacts.
discards 24939d7399b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards dcb4611e441 125: onsuccess: #614: 1: Success after linux: 12 commits discards f783b53cacf 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 0d8fd60c6af 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 1f2ce773c2b 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 128e180e757 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 3774bc07ad0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 4013e6d9c47 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c78829e023e 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 8fcaa7d67c3 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards dbeaf6ee6e8 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards dd228c55477 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards c2aa79d3c44 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 4a0768078b4 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 40302044d3b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards a78ca4b2bfd 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards 3c827c3719a 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards f4c56dc46ed 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 88e4ef157f6 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 361933ca91c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards daf8b5028c6 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 74543d7030d 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards f9c0e9c8605 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 6b342b8e43a 103: onsuccess: #589: 1: Success after binutils: 3 commits discards e228da7664e 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 353dcbdfa30 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] discards d09e5ea4114 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 0b5cff3b834 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] discards f40568ba851 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 7413673e59a 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] discards cbc7a5ba071 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] discards 3e2fca1d912 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 241c426474b 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards 6dac530f13e 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 8cc0ad2aceb 92: onsuccess: #575: 1: Success after linux: 34 commits discards b3df343b232 91: onsuccess: #574: 1: Success after glibc: 3 commits discards c5daad35675 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 466ed49950e 89: onsuccess: #570: 1: Success after linux: 11 commits discards 51e21bf4c68 88: onsuccess: #569: 1: Success after glibc: 10 commits discards a3c4ac0108a 87: onsuccess: #567: 1: Success after binutils: 8 commits discards bb8f387ac41 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards ddc92c2bc26 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards f385af29c52 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards f6094551b2a 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] discards d099f32a3f7 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] discards 7f1bab49804 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 74cb63641fd 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] discards 0e1840b3c62 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards 2b9a7fc100c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] discards b501ae6b249 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards d94b4a20240 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] discards b1f1a68d13c 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] discards dc9596acf14 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 4fd107a46d8 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 9e5d7f9070c 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 6003971da44 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards fb45b239dc1 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 032f92b951b 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] discards b0950c6e782 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards c0c1e158a99 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 431c70b3e1c 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 0a7b8b026a2 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards 32a957dfae0 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards d866b14e41f 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 78e8c8d09cc 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards b2df72d257f 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards 9be9296b692 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] discards e556f53d73b 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 2147becc140 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 9d271c8eb3b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] discards 820dd996ba4 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards c647fbaf669 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 9d577255e2c 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] discards 1f2e857b3da 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 047d394264f 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 87a351b4724 51: onsuccess: #525: 1: Success after binutils: 8 commits discards f4e41a77dde 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] discards 1524a01b3cc 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] discards 6c09cebdc64 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] discards d7d03a4743f 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] discards 1345198dd40 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] discards 221bd1ca9d9 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] discards 54de9aded57 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] discards e28810a6b20 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] discards 0d7d10aa60d 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] discards 95bfd86a77e 41: onsuccess: #514: 1: Success after linux: 64 commits discards f0152e5e7ed 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] discards c3a95370d6e 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 1be76f92b5e 38: onsuccess: #508: 1: Success after binutils: 3 commits discards e721a661479 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 9add084f946 36: onsuccess: #505: 1: Success after glibc: 3 commits discards b70e9cd17e4 35: onsuccess: #503: 1: Success after binutils: 11 commits discards cde3d054a6a 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 259fe58e164 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] discards 96e662a15b6 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards c3e222cfe43 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 81091679873 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 4a255702ff0 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards f8cdcf50688 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] discards 4c38f04728d 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] discards e689639b43b 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new 284f4d5d81f 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gl [...] new c8b3970c8da 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gl [...] new dd9957fdf0c 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gd [...] new 3ae7e646857 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new ebe8b26f622 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new ac31468dfe1 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 4ac0d4e11ec 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 6336ab8b148 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gd [...] new edc3299bc4e 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new a2d3ecdc6af 35: onsuccess: #503: 1: Success after binutils: 11 commits new b0c2869c595 36: onsuccess: #505: 1: Success after glibc: 3 commits new 9209b336ed9 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65 [...] new db30feb0485 38: onsuccess: #508: 1: Success after binutils: 3 commits new 1265f3740c3 39: onsuccess: #511: 1: Success after binutils: 8 commits new bbdd880b179 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g [...] new d2848274c4b 41: onsuccess: #514: 1: Success after linux: 64 commits new a0e67ab1bda 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gl [...] new ad679065eb5 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gl [...] new 78d2af408ad 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gl [...] new e907136af55 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gd [...] new 63b4cd18f70 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gl [...] new 54c452a96f6 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gd [...] new fa03b02958d 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gl [...] new e5aefe94915 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gl [...] new 4c587fe9ce2 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gd [...] new ccca732e3f2 51: onsuccess: #525: 1: Success after binutils: 8 commits new 28999ee0dce 52: onsuccess: #528: 1: Success after binutils: 8 commits new a243679d40e 53: onsuccess: #531: 1: Success after binutils: 12 commits new dc8a128c331 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gl [...] new e4c2d67a9d7 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 8995a6e2d40 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 9251431d905 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gl [...] new cb70bbb98ec 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 50003c43af5 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 53ebb0444c8 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gl [...] new 3bac0b689fd 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new fe6e846c27b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 5830af80960 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new b0f4a6a0182 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 005afc7b27e 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new 6dc0750916b 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new dfae4953443 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 85059d960f1 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new c8d85cb00a6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gl [...] new 1d30d3408b2 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 17049668238 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new cb6a98d3595 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 08350f9afbb 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 72a5c579d7b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 62b53789c6d 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gd [...] new 6de74ca9fc9 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gl [...] new e1160453018 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new c45fd36274f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gd [...] new 765ab459eaa 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 6d7abb7f8e5 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gl [...] new ab6ed98406c 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 38854cefa81 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gl [...] new 40ac4db1867 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gl [...] new af8adf3e05d 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 510271a441c 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 34fa97ca2c0 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new a0322a48bbb 87: onsuccess: #567: 1: Success after binutils: 8 commits new 4b2f5919a57 88: onsuccess: #569: 1: Success after glibc: 10 commits new 247cf96fe78 89: onsuccess: #570: 1: Success after linux: 11 commits new 733b7295cc5 90: onsuccess: #572: 1: Success after binutils: 15 commits new 88366a17d6e 91: onsuccess: #574: 1: Success after glibc: 3 commits new 365c3cb1bdf 92: onsuccess: #575: 1: Success after linux: 34 commits new a88ade51fd0 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 9f4c43160d9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new c332ed06598 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 2190d569d8a 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gd [...] new b025e2ca802 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gl [...] new 192fd653300 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new b9d545d9268 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gl [...] new b8521d4897a 100: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 0fd51bc4b25 101: onsuccess: #584: 1: Success after binutils/gcc/linux/g [...] new e36dc05bcb4 102: onsuccess: #586: 1: Success after binutils: 5 commits new 907719d01cd 103: onsuccess: #589: 1: Success after binutils: 3 commits new eaad4b49c73 104: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new bcf010d75d0 105: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 53d561c4d21 106: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 6cd10592337 107: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new debc72401f3 108: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new bc5a550b975 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new f31fd64e318 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new c138a901fb4 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new d5869ad2fc3 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 305897747d2 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 7f422d8c1df 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 4124ca8f15b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new dee890956ed 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 78dbb507892 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new c8bdeeaf38b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 6bdee3981a6 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new b695b094c76 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new cb098a8151e 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 3e5f3dd98ab 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d3383d55057 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 86225bfbc89 124: onsuccess: #612: 1: Success after binutils: 18 commits new 135485a0693 125: onsuccess: #614: 1: Success after linux: 12 commits new 453d02c14dc 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 2c2374dfd66 127: onsuccess: #616: 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 (24939d7399b) \ 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 1776 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 53520 -> 53764 bytes 04-build_abe-gcc/console.log.xz | Bin 237224 -> 236120 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 236768 -> 235240 bytes 08-build_abe-gdb/console.log.xz | Bin 51768 -> 52000 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2196 -> 2392 bytes 11-check_regression/console.log.xz | Bin 13244 -> 20092 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 38 +- 11-check_regression/mail-body.txt | 204 +- 11-check_regression/results.compare | 96 +- 11-check_regression/results.compare2 | 3351 +++++++++-- 11-check_regression/results.regressions | 92 +- 12-update_baseline/console.log | 48 +- 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 | 206 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 92 +- sumfiles/gdb.log.xz | Bin 1747888 -> 1808684 bytes sumfiles/gdb.sum | 9713 +++++++++++++++---------------- 31 files changed, 7696 insertions(+), 6200 deletions(-)