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 8a7e5638eb 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 88865af0f5 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards dab0f8bee2 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 9a7485ae02 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 003e9be1ed 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 84a092ca05 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 2ad2eb4da6 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards fd291e0cc8 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 5bca96dcd6 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 2db9990854 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 8892194822 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 4a0a11c4c5 122: onsuccess: #909: 1: Success after linux: 2753 commits discards ba487c8e97 121: onsuccess: #908: 1: Success after glibc: 2 commits discards ab2ce7f7c1 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 468ad398ac 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 72e5cd99da 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards e25e70e578 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards f0905de8e2 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards a74a7a8e85 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards e825b4db1c 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 7bce1241e2 113: onsuccess: #898: 1: Success after linux: 3 commits discards ebd99c52ef 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 13874d9830 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 8e536331b7 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 9cab28564d 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 3d6d25e1df 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 0f7339b33a 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards b0c6043cf2 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards ea9ed9177f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 1382698080 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 99295083d9 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards f9255c8a77 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 0b837d3e2c 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 00586328e9 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 961c3e3294 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards ce1b0071d2 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 9d47ceb450 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards d9a09daa08 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 6459b1141f 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 22b7114139 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 77b8569a10 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 4d4bfbc641 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 85db247b43 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 7bd931fb9b 90: onsuccess: #867: 1: Success after binutils: 4 commits discards f88357dd53 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 84724da6c2 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 7beb3bfc21 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 832d22066c 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards f784fd962d 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 6865804544 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards 3c686f6b1c 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 1947663a07 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 77d7020c4c 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards df24cacd03 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards fd1d4004f1 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 7495188efb 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 58a24f747d 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 0ed589d7a8 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 3e42962f19 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards e68f506aae 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards fc8de97424 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards c2d5d6adfc 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 6a7f10335b 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 0d43054df1 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 9dec99e855 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards f6f5acfd6c 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 930045b55e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 3cad2a8cc1 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 064d5186df 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 06ea9588c0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 0469a5eecf 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 4852bf0939 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 295329a512 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards e5687c83d4 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 45dd63501c 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards ada639dee8 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards fd715cbe9b 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards d8ac8549c7 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 011e34d103 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 1f530e82ed 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards f07a23f22d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards f0fa8f8c53 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 934b2bee3d 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards d1530ba187 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards 8b44584c47 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 1dd3937455 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards a16d07208c 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 992990f438 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 52f63c5428 45: onsuccess: #815: 1: Success after binutils: 6 commits discards ed631d59af 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d53e4a557d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards f970eabcf1 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards eb3a7829fa 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards 78116184c9 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 5b124b0eb4 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 22232eb256 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 889bd0632f 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards 0d2b218f4f 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards c1696056e9 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards b3bb80352e 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards 9d4a7e8d7b 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new bc4c1dceee 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 65390a9d1a 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 7fd0a42a71 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 69d1a781c1 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new 7fdf542255 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new 3625ac3e52 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new 8069d9e521 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new fc95d82d93 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new e914666456 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 128a613184 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new af953f6716 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new cb8fc3a9c7 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 05162e51fe 45: onsuccess: #815: 1: Success after binutils: 6 commits new 67cdbd9d3a 46: onsuccess: #818: 1: Success after binutils: 10 commits new 309c0985a5 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 3a9937f8e9 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 27cc38f2a5 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new f9f80fdaab 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 748eba5376 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9e1dd78839 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 19729fb678 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 67c213c5e5 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new c833528eb2 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e0821bd8a2 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 94ab8edfba 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new acc77825dd 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 9367767e0d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new a9322f3f14 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 51420a0bf5 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 08f5a2f9b6 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 196552824c 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 2c85e33936 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new 00a30f56be 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 319730190b 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 927a789536 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new a1e465e38e 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new f1201a1cf9 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 9d503c5324 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 891a9fcf92 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 4c59e9a17d 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 8c57c05577 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 965aa33c10 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 92339940a5 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 50d51704e1 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new ac659c73ef 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new fb6a1808e5 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new bce70e48e8 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new e93a5bf2c1 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 7fd197b84e 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new d159c61773 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 27859207ca 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new d7971cbcae 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new f40c728049 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new af60008051 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 776bdcb426 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 5af3e40b58 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 1a8fcc5af3 89: onsuccess: #864: 1: Success after binutils: 25 commits new 25de77d846 90: onsuccess: #867: 1: Success after binutils: 4 commits new 2f489dc0b0 91: onsuccess: #870: 1: Success after binutils: 5 commits new 3d5ef7ce93 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 4e350257dc 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 27f2f4984d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 462b543a0a 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 29671dcef4 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 9cae039c8f 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 8ac7d63128 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new ca177dd7ed 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 7367b6b662 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 0a765102e5 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new d43309a5ad 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 05603ed60f 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 90c5cfcec0 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new f9d17ff77b 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 3b91df0fac 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 29f3d2193e 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new a466ac6044 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 7d5ef32906 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 92e8d75a47 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new fe8bfd4bb9 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 1075d76c03 112: onsuccess: #896: 1: Success after binutils: 24 commits new 113a5b9f3a 113: onsuccess: #898: 1: Success after linux: 3 commits new 50aad0f7da 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 65a9447ba4 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 592be5fc71 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new dda55f09d8 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new a40be81abf 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 9043783658 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new da9c9194b9 120: onsuccess: #906: 1: Success after binutils: 29 commits new 0ae65a8573 121: onsuccess: #908: 1: Success after glibc: 2 commits new 42e09a50d5 122: onsuccess: #909: 1: Success after linux: 2753 commits new 766256f569 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 84db295d90 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new e5136e4a91 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 78919de56b 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 3c03ce0abf 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 5d9c5a0346 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 6fb81a7475 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new 5a232307fc 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new a49d8b5cca 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 130d759bea 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 00eae5d429 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new f56655e522 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits
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 (8a7e5638eb) \ 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 1744 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 40100 -> 40640 bytes 04-build_abe-gcc/console.log.xz | Bin 216240 -> 216412 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 245652 -> 244836 bytes 08-build_abe-gdb/console.log.xz | Bin 39596 -> 39420 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2272 -> 2112 bytes 11-check_regression/console.log.xz | Bin 12764 -> 20900 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 31 +- 11-check_regression/mail-body.txt | 204 +- 11-check_regression/results.compare | 108 +- 11-check_regression/results.compare2 | 4579 +++++++++++++++++++- 11-check_regression/results.regressions | 108 +- 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 206 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 108 +- sumfiles/gdb.log.xz | Bin 1886960 -> 1948056 bytes sumfiles/gdb.sum | 6995 ++++++++++++++++++++++++++++++- 28 files changed, 11694 insertions(+), 723 deletions(-)