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 f56655e522 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 00eae5d429 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 130d759bea 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards a49d8b5cca 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 5a232307fc 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 6fb81a7475 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 5d9c5a0346 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 3c03ce0abf 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 78919de56b 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards e5136e4a91 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 84db295d90 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 766256f569 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 42e09a50d5 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 0ae65a8573 121: onsuccess: #908: 1: Success after glibc: 2 commits discards da9c9194b9 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 9043783658 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards a40be81abf 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards dda55f09d8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 592be5fc71 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 65a9447ba4 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 50aad0f7da 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 113a5b9f3a 113: onsuccess: #898: 1: Success after linux: 3 commits discards 1075d76c03 112: onsuccess: #896: 1: Success after binutils: 24 commits discards fe8bfd4bb9 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 92e8d75a47 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 7d5ef32906 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards a466ac6044 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 29f3d2193e 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 3b91df0fac 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards f9d17ff77b 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 90c5cfcec0 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 05603ed60f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards d43309a5ad 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 0a765102e5 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 7367b6b662 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards ca177dd7ed 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 8ac7d63128 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 9cae039c8f 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 29671dcef4 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 462b543a0a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 27f2f4984d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 4e350257dc 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 3d5ef7ce93 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 2f489dc0b0 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 25de77d846 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 1a8fcc5af3 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 5af3e40b58 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 776bdcb426 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards af60008051 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards f40c728049 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards d7971cbcae 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 27859207ca 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards d159c61773 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 7fd197b84e 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards e93a5bf2c1 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards bce70e48e8 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards fb6a1808e5 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards ac659c73ef 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 50d51704e1 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 92339940a5 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 965aa33c10 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 8c57c05577 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 4c59e9a17d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 891a9fcf92 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 9d503c5324 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards f1201a1cf9 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards a1e465e38e 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 927a789536 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 319730190b 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 00a30f56be 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 2c85e33936 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 196552824c 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 08f5a2f9b6 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 51420a0bf5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards a9322f3f14 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 9367767e0d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards acc77825dd 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 94ab8edfba 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards e0821bd8a2 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards c833528eb2 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 67c213c5e5 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 19729fb678 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 9e1dd78839 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 748eba5376 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards f9f80fdaab 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 27cc38f2a5 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 3a9937f8e9 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 309c0985a5 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 67cdbd9d3a 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 05162e51fe 45: onsuccess: #815: 1: Success after binutils: 6 commits discards cb8fc3a9c7 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards af953f6716 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards 128a613184 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards e914666456 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards fc95d82d93 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 8069d9e521 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 3625ac3e52 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 7fdf542255 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 69d1a781c1 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 7fd0a42a71 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 65390a9d1a 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 6aa4b14fb0 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new ed8008ebd0 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 07b51480d7 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 9ef29c2ac7 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new fffe6a9d30 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 9da9ac6dbd 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new e75692f868 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new cd1632c617 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new b14461f8c7 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new f35474b15f 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new ae8e473a02 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new a385df332a 45: onsuccess: #815: 1: Success after binutils: 6 commits new c68c1ea5fc 46: onsuccess: #818: 1: Success after binutils: 10 commits new 8bb5a1c336 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 2430412568 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new c5b9aad5be 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new b34f3513c4 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new bdf5e8d9d5 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 08cd2e39e1 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new cac8a6ad99 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 499bc522ee 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 068ad5785b 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 8a8e94bc12 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a6e3d2b88d 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 77ffd255a7 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new bfc135694d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 0ffa101099 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 64cc5f74ef 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 084cc73ea9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 2c9f55a5d9 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 14699d351c 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new b4b5c29425 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ce0e53f5e9 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 651b997ffe 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 918b8cb2bf 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 7daa429e82 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 8ed8fbd24f 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 7f030193f8 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 0aa28805a7 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new ccca4bdc6d 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new be8e37d585 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new b9a7f781dd 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 5c576ba5d4 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 56b1c4ca41 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new f52068877a 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new f733d8b75e 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new e2eab12db7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new e052ac5f1b 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 3567d1e301 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 0232e09115 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new a81e9363a6 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 680c219548 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 8aa5c1082e 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new f33f458b24 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new cb619f07a0 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 9caa578d02 89: onsuccess: #864: 1: Success after binutils: 25 commits new 762bfceebc 90: onsuccess: #867: 1: Success after binutils: 4 commits new 7fcfb916e8 91: onsuccess: #870: 1: Success after binutils: 5 commits new 212fddafd7 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 910d9f240e 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new e0d695a214 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new db44f2d0c9 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 0aacf8b463 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 3bb7a851c9 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 259871e4a3 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new db181db2a9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 82bda93607 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 580d5cdd1a 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new c34f24b49f 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 5e57e863ba 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 45f2109c68 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new d0f26d0bae 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 2fdcf76ade 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 9df0cbc193 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new 96cbb99403 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 83ebdf922b 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 53c0d69d39 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 341ceaa38b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new e5e9de9185 112: onsuccess: #896: 1: Success after binutils: 24 commits new f0a7fb62c1 113: onsuccess: #898: 1: Success after linux: 3 commits new 72d12662cf 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 6da539c1c4 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new d41905908c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 34b05783b6 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 7fba3c1d40 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 274b41bf43 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new ee6c829dff 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5b151456fc 121: onsuccess: #908: 1: Success after glibc: 2 commits new 8074b299c5 122: onsuccess: #909: 1: Success after linux: 2753 commits new f3b01d7e42 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new dc40399b93 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new fe5cefe794 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 4258dff709 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new a8dfa82225 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 840a095038 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 7834bd6939 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 1ca2958d11 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new d1ff07599b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 131058b1a6 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 93fd6aed58 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 25131db109 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 50c374cb11 135: onsuccess: #922: 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 (f56655e522) \ 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 1752 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40640 -> 39988 bytes 04-build_abe-gcc/console.log.xz | Bin 216412 -> 216204 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8328 bytes 07-build_abe-glibc/console.log.xz | Bin 244836 -> 244616 bytes 08-build_abe-gdb/console.log.xz | Bin 39420 -> 39472 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2112 -> 2024 bytes 11-check_regression/console.log.xz | Bin 20900 -> 19208 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 25 +- 11-check_regression/mail-body.txt | 174 +- 11-check_regression/results.compare | 96 +- 11-check_regression/results.compare2 | 938 +-- 11-check_regression/results.regressions | 96 +- 12-update_baseline/console.log | 40 +- 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 | 176 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 96 +- sumfiles/gdb.log.xz | Bin 1948056 -> 1898308 bytes sumfiles/gdb.sum | 10578 ++++++------------------------ 30 files changed, 2625 insertions(+), 9644 deletions(-)