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 1d10eb2498 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 6fdd69bc5a 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 767a7344e1 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 3da7b16f4f 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 8586b96e10 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 30cbb7331a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 1d7f3ae02b 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards b716337bfe 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 6ad7ce02d0 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 97c1ef5645 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards fe78b4f604 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 15815579aa 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 7055407483 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 8cdad4d68e 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards a1a8836b53 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 5df4c22a4d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 7b1e435fdc 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards bdd0db69c5 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards d836f3e348 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 2fcc4eb341 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 1e23f92498 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards d7ec0328f0 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 776f1d926a 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 87814db997 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards bd2ad99921 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 8a2deff504 122: onsuccess: #909: 1: Success after linux: 2753 commits discards b7a3d66729 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 2a47b6e522 120: onsuccess: #906: 1: Success after binutils: 29 commits discards b12b80ff12 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards d1819bc5d6 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards aa1ecad50c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards a543065a87 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 57f010a21e 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 1fd9a59024 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 6de4ed739c 113: onsuccess: #898: 1: Success after linux: 3 commits discards a183108446 112: onsuccess: #896: 1: Success after binutils: 24 commits discards b3adc0c077 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards e82dbd8fc1 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 34c9cde550 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards f3b9ebf783 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 734f492b65 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards e6c2d8104c 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards fa9504677e 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards e667110b49 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 33949fe896 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards b4357ae7e9 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 731df110f3 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards d46a42543f 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 037d9f17b9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards fc124c5dc9 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards c19cecedc7 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards b01462b252 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards ef715665eb 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 2558e9c15f 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 1c542b3a73 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 9901652063 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards fc6a49e47b 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 41ad0344c4 90: onsuccess: #867: 1: Success after binutils: 4 commits discards ff1c057ff8 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 4e50d6e885 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards ea42bbffb1 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 013be9ca33 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 627d541b08 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards dd38c2f34b 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards f5348e013d 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards dddb7d428b 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 8d670b3dcc 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 33de531b98 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards ffaa991b24 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 022cb51616 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 66de83bcb5 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 1a6b9fa6c9 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 63ada244b5 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards a720292c00 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards f952e183be 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 7c04f40b7f 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 2ca2fa624c 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards f75beb87fa 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards e9b5626258 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards ddbeda52a7 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards ce8c5cee51 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 15c006fe46 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 0986041317 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards e5228cafc2 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 3d27880c4f 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 25d5c90035 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards e4ffc42d40 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 98ce7c58a7 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 6591898e1c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 9c0d81ee11 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards bda7abd0f2 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards cd815bcc0b 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards f00e690c68 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 5cf0b3b7c1 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 7f98bd9a5a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 0779ff87e5 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9f8629030b 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 30d26e6fdb 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards f24877565a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 2413a0f79f 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards ce155d39ef 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new f2f3ec7fcb 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new ca607a08b9 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 9d4e4c4bd4 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 34738f7f6f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new c5262aa4e0 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 05e70916c6 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 6cb8ed61f1 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 0d50d2c42f 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new e987d6c2d2 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new c458e4176d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 47744fd9c1 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 6388cb8ca0 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 4902b26096 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 6599d93f05 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new ff75fe6e05 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new a55ed8a3f6 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 431018d686 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 09c3ccacf6 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 447d7622d6 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 7273cf3211 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 46b62cca26 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 8df1b17634 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new bccdf9392b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new b0cad6e257 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new f34f9d5ffd 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new b6e6d4c936 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 8e215d928b 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 62eb65a016 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 8e2bce589f 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 24d49181d0 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 3a0f7ec3cc 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new ad660e1c89 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new f89a7e3d39 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 7577d93e2b 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 09653b3fda 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 26b0af4086 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 1856b49a09 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new d908ab7ad1 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new e3096cf15f 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new b13dffb014 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 978c2beaa3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 59a8de3e5a 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 46adca6010 89: onsuccess: #864: 1: Success after binutils: 25 commits new 71c7d42fcb 90: onsuccess: #867: 1: Success after binutils: 4 commits new 7093cd1d0b 91: onsuccess: #870: 1: Success after binutils: 5 commits new ccc6ebb164 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 0bf4d3b203 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 6b8f444707 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new ab41f409c4 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new d6023bf03e 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 1974253dbb 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new e4d4280ac5 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 35ab3afba7 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new f207ecd916 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new f80c6a11a6 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 4ea480aa33 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new f996a2dcbd 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new be5de47b3c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 795c067a37 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 4253e7f0b0 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new b7a8c83bdb 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new fe6c12317a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 7de4f9dff1 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 8f8fedb760 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new fa7ad87178 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 207d8465ae 112: onsuccess: #896: 1: Success after binutils: 24 commits new de46a03c66 113: onsuccess: #898: 1: Success after linux: 3 commits new 8c72cc3db4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new d21dc68933 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 465459731f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new f249fed3c0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 193e8c1812 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new b95a17bf59 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new d2e23d6ec8 120: onsuccess: #906: 1: Success after binutils: 29 commits new 33a5280c6b 121: onsuccess: #908: 1: Success after glibc: 2 commits new c33b52387a 122: onsuccess: #909: 1: Success after linux: 2753 commits new 391f3c50ef 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new feb19cd2a0 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 9d002000c2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 9bac34cd10 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 61200c72b4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new cbd50a0e69 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 2a81ff9b2f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 829215181e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 3762f2bc8c 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new fa4cab6774 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new a124243cac 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 7cccb00f05 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 122e1e2f8e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 205ac1e117 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new b88be52cbb 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 932741ee99 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 4f9ad2fea3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 0deff86ae9 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new a12532e432 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 81d246afdb 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 09afdca385 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 5722825e3c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new e99d20901f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 6be3a32c38 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 4ff645ce46 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 0b9449ee15 148: onsuccess: #941: 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 (1d10eb2498) \ 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 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39344 -> 39608 bytes 04-build_abe-gcc/console.log.xz | Bin 216140 -> 214728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8956 bytes 07-build_abe-glibc/console.log.xz | Bin 243980 -> 244644 bytes 08-build_abe-gdb/console.log.xz | Bin 39624 -> 39672 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2084 -> 2036 bytes 11-check_regression/console.log.xz | Bin 7080 -> 6684 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 26 +- 11-check_regression/mail-body.txt | 115 +- 11-check_regression/results.compare | 49 +- 11-check_regression/results.compare2 | 159 +- 11-check_regression/results.regressions | 49 +- 12-update_baseline/console.log | 62 +- 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 | 117 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 49 +- sumfiles/gdb.log.xz | Bin 1962648 -> 1955396 bytes sumfiles/gdb.sum | 4299 ++++++++++++++++--------------- 30 files changed, 2442 insertions(+), 2531 deletions(-)