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 23d9c24e76 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards fcba92118d 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards aec1e8e03e 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 0056005bae 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 6450215908 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards a191a8e1ba 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 28b91095f6 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 96b8238e9f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 49d117b28b 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 24da19c36d 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 3ba9532d5d 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 6de2c48a53 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 80287a1876 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 9063dd1ec5 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards c9b843c6a9 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 6005c9196e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 80c0c45811 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards a77c5d4ece 113: onsuccess: #898: 1: Success after linux: 3 commits discards 5f4157fd1e 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 7dc4c21d01 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 3246c4b02d 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 1cf1d4affb 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 4b2b37b25b 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards cf069cbd41 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards cdd3a27e21 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5085acb4bc 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 935dbb7542 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards dea110e190 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 4615dcf0e1 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7b112b7091 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards b351338e93 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 1159e20b59 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 5f1ad5b550 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 51f956fa49 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 99473a8b53 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards e1243a8da4 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards d12f1bd346 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 277bf3c4b6 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 394c0d9266 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 06c948b6e8 91: onsuccess: #870: 1: Success after binutils: 5 commits discards b397fef286 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 390a647d1d 89: onsuccess: #864: 1: Success after binutils: 25 commits discards cf6e7a6717 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 5f1b7d1363 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 1d6610fec9 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards e98ab9c30a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 4ca7c16ede 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 9506482f1d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 20dab2066b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards a99b1d35ca 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 24055d96d1 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 00a0b88307 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 6781554a88 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards e8d2aad774 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 8cacd2cb8b 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards b88fadb182 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 1b3095cc79 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards bd42af191b 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards a4106c4143 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards fccefa529a 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 3da5b66125 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 8168861347 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards e3ebdd1093 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 2ad9c941b6 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards a1284860c6 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 080cb85adc 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ef7ac46f8f 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 4bfa5abae3 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 66c3043bd3 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 07d2e72ab5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 90485d274d 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 0e1468380f 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 5fd3c2b40e 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 014cf35b4b 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 3979a037e5 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 618b19a2cc 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 7c417386c1 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 62382a4d3c 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 07b0bdecda 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 2d6069bcda 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 21c4d1d237 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards b334683b6a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 4f90ce2479 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards b606d0740e 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 71546ac3c7 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 978e4e7c13 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 8231c66150 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 69d0fa4108 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 23e002e57f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards fb7667ef5a 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 5e9ad08c06 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards ab2bb2ae6c 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards c4582d06ca 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 6fe5f36095 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 9fafddeadf 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards b24e358b05 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards d38f62bfeb 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards e7e00262a6 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 762fb7d41c 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards fcbfff623e 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards 6de8811a42 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new f25db29d3a 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 20b5093ebb 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new 21bf83b6fe 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 4d0bc121d0 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 699f1c7aa2 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new bd8199ec72 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new b54fd89e5e 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 80cc4a2e3a 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new c4a7c166a2 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 3b16700b78 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new a62cef7509 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new b291a1e804 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 69789c866f 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 3326efef5e 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new bb0708751b 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 25b2e8e93e 45: onsuccess: #815: 1: Success after binutils: 6 commits new b060b4c02c 46: onsuccess: #818: 1: Success after binutils: 10 commits new 73f37ee634 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 2978683100 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 9576bef942 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 9ed1fe759f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new cd380c7d04 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 5c83b56c6f 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new fe60a8fc41 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new c02405897e 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 66d533cdfa 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 9fec3d9bd1 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a460414523 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 11cb2ee18b 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 4a96b50952 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 32728acc41 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 7e98896d5d 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 9db0f172d9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new d100257934 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 8480b3f529 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new f61652fcd6 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 5b9cf9bc50 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 4beb021f84 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new f0744a8e6a 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 4c159e91a8 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 521c25cac4 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 28cc87bd16 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 9410760e9b 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 0b83945a9c 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new a753c3c68b 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 44c26028b8 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new a352837242 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 218e7aed04 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 58b2793408 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 459c053f7f 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 8ed86fdeb7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 5f242ea3df 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 2e65a5b720 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 18e1671a6c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new a824e1bc86 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 2f9936b642 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 826c00b9ad 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 5a7ac9e4e3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new f0ccae1beb 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new a072671a14 89: onsuccess: #864: 1: Success after binutils: 25 commits new 8feb52e079 90: onsuccess: #867: 1: Success after binutils: 4 commits new 9c859d421a 91: onsuccess: #870: 1: Success after binutils: 5 commits new d9a5acce01 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 9643a1bcf5 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 08541fd055 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 0d87b013bc 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new e844c256f5 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new a8d3efb453 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new ef168c51bb 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new f24ea4dbf6 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new d9aa027f3e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new a735ab0aae 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new f4c6c1d200 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new f91d183ab7 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new d5e535e51d 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 0c2f0350da 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 1f2a546fd9 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 8b148611c8 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 754689aac0 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 1034c0f6e0 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 52c1fdb53e 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 95be9af82a 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new ff0d021276 112: onsuccess: #896: 1: Success after binutils: 24 commits new 8ebe270575 113: onsuccess: #898: 1: Success after linux: 3 commits new eaa4e12348 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 1986d992a3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new fa4043d955 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 40e9a1bb5d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new ee7c3c4dd0 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 6c6f60c128 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 65bcaeda62 120: onsuccess: #906: 1: Success after binutils: 29 commits new f577900930 121: onsuccess: #908: 1: Success after glibc: 2 commits new 17ec99acd8 122: onsuccess: #909: 1: Success after linux: 2753 commits new 5af9a7f77f 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 9aaba25af3 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 2b7d0fa59d 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 442d96edc2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 7241c59c1c 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 33aed7791b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 1e01531c53 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 57ecc9fb9e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new e8323e5666 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...]
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 (23d9c24e76) \ 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 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 40108 -> 40824 bytes 04-build_abe-gcc/console.log.xz | Bin 217264 -> 215472 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 244668 -> 245556 bytes 08-build_abe-gdb/console.log.xz | Bin 39124 -> 39752 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2284 -> 2128 bytes 11-check_regression/console.log.xz | Bin 19652 -> 13524 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 66 +- 11-check_regression/mail-body.txt | 225 +- 11-check_regression/results.compare | 106 +- 11-check_regression/results.compare2 | 5870 ++++++++----------------- 11-check_regression/results.regressions | 108 +- 12-update_baseline/console.log | 42 +- 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 | 227 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 108 +- sumfiles/gdb.log.xz | Bin 1927284 -> 1956904 bytes sumfiles/gdb.sum | 7289 ++++++++++--------------------- 31 files changed, 4460 insertions(+), 9635 deletions(-)