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 fe03f25ee8 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards ac8f106374 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 578ca90dac 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 83879ad096 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 6bcfc9de66 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards ebb7f1c1bc 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards d3923b19c4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 0c11dde529 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 9ac3560aa8 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards e081f7f283 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 09513c21d9 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards f39059f9c1 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards b9d246865f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 5f7505301b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 381c2f1291 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards d073870fb8 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards e3fc945f3f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards b5e29c4276 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 2360d9d00f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 4c1bff13d4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards dde09683a9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 3ffa2a16c4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards ca59dc066f 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 4346bd34a5 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 8eabe239ef 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 0b27034e87 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 4bf4e68561 120: onsuccess: #906: 1: Success after binutils: 29 commits discards d8f3e68ee6 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 289fe3f635 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards ca535733dd 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 4499a596dc 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 4efa6a1457 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 4ce2c47242 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards b3358cfa6b 113: onsuccess: #898: 1: Success after linux: 3 commits discards 3484c0135c 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 4c1f6d591b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 52bf1d20ff 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards e485d8683c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards aec8d68d70 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards cca46daf55 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 5897516604 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards b53401d772 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 74c15abd4f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 8b43b1d9d3 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 8c0ee729c6 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 6331106e80 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 46410a1db0 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards bb28318add 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards ababc41f2c 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards f191cb8150 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards f86a257d43 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 43342411cc 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 820e65673c 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards abf4b833cb 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards e38471c0a6 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards b36bc624dd 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 4b7a6ccecc 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 3b23938b1f 89: onsuccess: #864: 1: Success after binutils: 25 commits discards fe4f1e30e4 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 0b7d4d7948 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 57e5895956 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 795480e05e 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards abf75e0108 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 0785efbcfc 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 65f713bdf0 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 911b607760 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards ba5cd6075c 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards d95e6ec157 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 9a9ae2e53c 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 8206e1449b 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 67ef381ed0 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 5790abb50e 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards d75c5e6139 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 83a435502e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards a8c944f24e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 4eb2d3d8bb 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards a4c5e39fec 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards cb3dc4dc86 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 8375e35fb8 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 9a15029d4b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 066811401d 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards c1f7640d6f 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards b5820f67bf 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 873729b524 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 2a8ac47cfe 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 2b22ab08dd 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 4c2908ca40 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 49a41b903a 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards bf57cb238d 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards eef375f170 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards f903b5ab4f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 43fae98a34 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 6cfc813ef6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 0106cdbc02 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards c7cc414daa 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards b613a311ba 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 91df0cb0ea 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards d8a96d82c5 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 13579ac3a3 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 5e2794b58d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 6aa95cc51c 46: onsuccess: #818: 1: Success after binutils: 10 commits new b6a21a31a5 46: onsuccess: #818: 1: Success after binutils: 10 commits new ce155d39ef 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 2413a0f79f 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new f24877565a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 30d26e6fdb 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 9f8629030b 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 0779ff87e5 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 7f98bd9a5a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 5cf0b3b7c1 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new f00e690c68 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new cd815bcc0b 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new bda7abd0f2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 9c0d81ee11 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 6591898e1c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 98ce7c58a7 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new e4ffc42d40 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 25d5c90035 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 3d27880c4f 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new e5228cafc2 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 0986041317 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 15c006fe46 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new ce8c5cee51 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new ddbeda52a7 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new e9b5626258 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new f75beb87fa 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 2ca2fa624c 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 7c04f40b7f 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new f952e183be 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new a720292c00 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 63ada244b5 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 1a6b9fa6c9 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 66de83bcb5 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 022cb51616 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new ffaa991b24 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 33de531b98 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 8d670b3dcc 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new dddb7d428b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new f5348e013d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new dd38c2f34b 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 627d541b08 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 013be9ca33 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ea42bbffb1 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 4e50d6e885 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new ff1c057ff8 89: onsuccess: #864: 1: Success after binutils: 25 commits new 41ad0344c4 90: onsuccess: #867: 1: Success after binutils: 4 commits new fc6a49e47b 91: onsuccess: #870: 1: Success after binutils: 5 commits new 9901652063 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 1c542b3a73 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 2558e9c15f 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new ef715665eb 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new b01462b252 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new c19cecedc7 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new fc124c5dc9 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 037d9f17b9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new d46a42543f 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 731df110f3 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new b4357ae7e9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 33949fe896 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new e667110b49 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new fa9504677e 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new e6c2d8104c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 734f492b65 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new f3b9ebf783 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 34c9cde550 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new e82dbd8fc1 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new b3adc0c077 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new a183108446 112: onsuccess: #896: 1: Success after binutils: 24 commits new 6de4ed739c 113: onsuccess: #898: 1: Success after linux: 3 commits new 1fd9a59024 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 57f010a21e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new a543065a87 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new aa1ecad50c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new d1819bc5d6 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new b12b80ff12 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 2a47b6e522 120: onsuccess: #906: 1: Success after binutils: 29 commits new b7a3d66729 121: onsuccess: #908: 1: Success after glibc: 2 commits new 8a2deff504 122: onsuccess: #909: 1: Success after linux: 2753 commits new bd2ad99921 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 87814db997 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 776f1d926a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new d7ec0328f0 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 1e23f92498 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 2fcc4eb341 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new d836f3e348 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new bdd0db69c5 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 7b1e435fdc 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 5df4c22a4d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new a1a8836b53 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 8cdad4d68e 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 7055407483 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 15815579aa 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new fe78b4f604 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 97c1ef5645 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 6ad7ce02d0 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new b716337bfe 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 1d7f3ae02b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 30cbb7331a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 8586b96e10 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 3da7b16f4f 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 767a7344e1 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 6fdd69bc5a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 1d10eb2498 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...]

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 (fe03f25ee8) \ 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 1788 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 40748 -> 39344 bytes 04-build_abe-gcc/console.log.xz | Bin 215432 -> 216140 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9096 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 244904 -> 243980 bytes 08-build_abe-gdb/console.log.xz | Bin 39412 -> 39624 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2032 -> 2084 bytes 11-check_regression/console.log.xz | Bin 12416 -> 7080 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 20 +- 11-check_regression/mail-body.txt | 144 +- 11-check_regression/results.compare | 66 +- 11-check_regression/results.compare2 | 2346 +---------------- 11-check_regression/results.regressions | 66 +- 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 146 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 66 +- sumfiles/gdb.log.xz | Bin 1878724 -> 1962648 bytes sumfiles/gdb.sum | 4326 ++++++++++++++++--------------- 30 files changed, 2465 insertions(+), 4807 deletions(-)