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 0b9449ee15 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards 4ff645ce46 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards 6be3a32c38 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards e99d20901f 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 5722825e3c 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 09afdca385 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 81d246afdb 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards a12532e432 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 0deff86ae9 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards 4f9ad2fea3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 932741ee99 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards b88be52cbb 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 205ac1e117 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 122e1e2f8e 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 7cccb00f05 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards a124243cac 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards fa4cab6774 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 3762f2bc8c 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 829215181e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 2a81ff9b2f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards cbd50a0e69 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 61200c72b4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 9bac34cd10 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 9d002000c2 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards feb19cd2a0 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 391f3c50ef 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards c33b52387a 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 33a5280c6b 121: onsuccess: #908: 1: Success after glibc: 2 commits discards d2e23d6ec8 120: onsuccess: #906: 1: Success after binutils: 29 commits discards b95a17bf59 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 193e8c1812 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards f249fed3c0 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 465459731f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards d21dc68933 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 8c72cc3db4 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards de46a03c66 113: onsuccess: #898: 1: Success after linux: 3 commits discards 207d8465ae 112: onsuccess: #896: 1: Success after binutils: 24 commits discards fa7ad87178 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 8f8fedb760 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 7de4f9dff1 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards fe6c12317a 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards b7a8c83bdb 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 4253e7f0b0 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 795c067a37 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards be5de47b3c 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards f996a2dcbd 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards 4ea480aa33 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards f80c6a11a6 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards f207ecd916 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 35ab3afba7 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards e4d4280ac5 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 1974253dbb 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards d6023bf03e 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards ab41f409c4 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 6b8f444707 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 0bf4d3b203 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards ccc6ebb164 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 7093cd1d0b 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 71c7d42fcb 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 46adca6010 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 59a8de3e5a 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 978c2beaa3 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards b13dffb014 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards e3096cf15f 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards d908ab7ad1 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 1856b49a09 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 26b0af4086 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 09653b3fda 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 7577d93e2b 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards f89a7e3d39 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards ad660e1c89 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 3a0f7ec3cc 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 24d49181d0 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 8e2bce589f 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 62eb65a016 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 8e215d928b 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards b6e6d4c936 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards f34f9d5ffd 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards b0cad6e257 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards bccdf9392b 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 8df1b17634 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 46b62cca26 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 7273cf3211 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 447d7622d6 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 09c3ccacf6 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 431018d686 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards a55ed8a3f6 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards ff75fe6e05 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 6599d93f05 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 4902b26096 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 6388cb8ca0 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 47744fd9c1 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards c458e4176d 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards e987d6c2d2 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 0d50d2c42f 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 6cb8ed61f1 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 05e70916c6 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards c5262aa4e0 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 34738f7f6f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 9d4e4c4bd4 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards ca607a08b9 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 333711d9cd 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new f694ed202a 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new a009eab05e 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 03e178be76 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 579ebb9ec7 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 7657ea4b6c 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 89999775a6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 0e81824920 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new b98759d839 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new ebc500e271 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new a537ac8bbf 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new e0806ddd6c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new c9e58a64de 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 472c6c743e 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 10017896bc 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 85ba129c92 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new bd7db32bdd 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 93d91bf5d1 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new d7188a95fd 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new c3c37b37b9 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 090d032a9d 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new f61c413bff 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 522808d437 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 3b3be3274d 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new cbea667507 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new c9324a8464 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new cfe9effdaa 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 76cdcfda75 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 458b0449f2 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new e324765df2 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 6d3bee41ae 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 45e74e3f48 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 9c63645623 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new edc714fed9 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new cccbf1867e 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 7309693ef7 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 9a2837cc56 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 88091d892e 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 6ae3c67a02 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 88874202ee 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 6a431cdeb1 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 847de2701f 89: onsuccess: #864: 1: Success after binutils: 25 commits new d4525c947d 90: onsuccess: #867: 1: Success after binutils: 4 commits new 26f2bb520f 91: onsuccess: #870: 1: Success after binutils: 5 commits new ffdc05debe 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 86d2620f36 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 01d9fccd82 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 0d3f184373 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new b1b180b79c 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new d660c92a70 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 3a9320ead8 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new 16e4368bff 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 30fa44c961 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new e7340df980 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 3f0bb88385 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new c76d8ddbb2 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new effe0850f9 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 7e7726f2de 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 12711b62e4 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 98021a9e4b 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 8438746f9f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d374d8923a 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new a260756662 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 4af2cb16cc 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new bb8ed9aac0 112: onsuccess: #896: 1: Success after binutils: 24 commits new 4a656e3659 113: onsuccess: #898: 1: Success after linux: 3 commits new cfc7e121f7 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new bc87c5b63a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 040780f0f4 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 3a0407d5b9 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new cb025972d9 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 2c6aae4c63 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 50637038ea 120: onsuccess: #906: 1: Success after binutils: 29 commits new c34ae00436 121: onsuccess: #908: 1: Success after glibc: 2 commits new 7b50946fc6 122: onsuccess: #909: 1: Success after linux: 2753 commits new 3a1d4b8c96 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 5fcecb7a18 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 0e560b4062 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 5a84fd142a 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 0a714afbe1 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new c1760776c7 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 5f58f51f5b 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new e909420a85 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 559298a9e1 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 9db2e11f6c 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 2e5c325952 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new c3380ba73b 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 7fba665186 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 0122bbbeaf 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new c1c1259757 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 63d4bba45d 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 3ae3e649b0 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 306ed5e3de 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 764c7381c7 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new e5d3ed460d 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 8fdd82b3bd 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new dbfe631456 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 8cd89a1528 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new 43b58da191 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new cc9e327f5e 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 3d5db1bc0f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new 627e99e7e5 149: onsuccess: #942: 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 (0b9449ee15) \ 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 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39608 -> 39572 bytes 04-build_abe-gcc/console.log.xz | Bin 214728 -> 214256 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8956 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 244644 -> 244300 bytes 08-build_abe-gdb/console.log.xz | Bin 39672 -> 39520 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2036 -> 2156 bytes 11-check_regression/console.log.xz | Bin 6684 -> 22700 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 28 +- 11-check_regression/mail-body.txt | 104 +- 11-check_regression/results.compare | 55 +- 11-check_regression/results.compare2 | 7230 ++++++++++++++++++- 11-check_regression/results.regressions | 55 +- 12-update_baseline/console.log | 38 +- 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 | 106 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 55 +- sumfiles/gdb.log.xz | Bin 1955396 -> 1944064 bytes sumfiles/gdb.sum | 11424 ++++++------------------------ 31 files changed, 9664 insertions(+), 9487 deletions(-)