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 332f18e093 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards f54de475c3 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 81f951ce76 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 963d80c91c 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 5300b76615 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards 0a250310f4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards b3387dacd4 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards c96d14d5c6 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 925fef68f4 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 49253c69f1 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards a73f745772 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 54df76f2ed 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards b3b548a36a 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 8ec3a36feb 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 009e5ddbd2 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards 2dbb581ddb 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 0f6eee1034 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 7491e7fd68 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 2247a2a66e 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards ef6f603342 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 0fd9c070c3 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 8f29698dad 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 2beb06f5b1 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards e0887fda76 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 365059444d 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 155edcc2b7 120: onsuccess: #906: 1: Success after binutils: 29 commits discards f18763c681 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 18251104d4 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards e905885766 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards c330ff002c 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards f475a8ff9a 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards ccad635f1f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards fe672f2974 113: onsuccess: #898: 1: Success after linux: 3 commits discards 56789bbd1d 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 94aaee1235 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards c071dc1602 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards b0d9eba425 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 0910ef01fa 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards ed20520f84 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 37c1d17bc8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards e889922c43 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards aadeb4c382 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards d049de4381 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards a2eb5ced73 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards d41d473f0c 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 1bb9c96c5e 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 78af0ed760 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 43994a6784 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards 46ac6e6559 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 1df40ffc20 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 68807b2e36 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 606ae8d3e6 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards 836ce03bba 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards f86da65c74 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards fe1a0a3fd7 91: onsuccess: #870: 1: Success after binutils: 5 commits discards e3ccfe8281 90: onsuccess: #867: 1: Success after binutils: 4 commits discards 18e325c140 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 3d5c98ac05 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards 83a762685f 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards e1273942a2 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards feb2d55a1a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 681ea63580 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards a403cd538a 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 1bf5b687b9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 34ff2295c3 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards a82d468516 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards aad1273d7e 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 3b7d202a6e 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards f5a9aaae75 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 2e644e1577 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards e3e4842f1e 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards c2a4f4a4c6 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 04f80bb9c5 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards a9539501b1 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 1a90ebd434 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 7d6fc380d7 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards 8eafec6dd3 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards a70455a4d5 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards a11efc9d2e 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards f3138c29e3 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards 4a8e25dc24 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards df61512736 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards 1f8b768d43 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards 11d7d65de9 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 8b58a394fd 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards 659963a3dc 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards 24a4bdd077 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 67a120183c 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards 02710a927c 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards cb9db5cfc2 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 62602b2dd3 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 193610389b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards f4aae7dca4 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 3e18a062c4 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards d162fa0c96 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 91bfbd2168 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards ecb1b27fb3 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards a3b5b262cd 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 0eace92d8a 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f188a86f71 46: onsuccess: #818: 1: Success after binutils: 10 commits discards 829faae66c 45: onsuccess: #815: 1: Success after binutils: 6 commits new f688c4036d 45: onsuccess: #815: 1: Success after binutils: 6 commits new 6aa95cc51c 46: onsuccess: #818: 1: Success after binutils: 10 commits new 5e2794b58d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 13579ac3a3 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new d8a96d82c5 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 91df0cb0ea 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new b613a311ba 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new c7cc414daa 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0106cdbc02 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 6cfc813ef6 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 43fae98a34 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new f903b5ab4f 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new eef375f170 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new bf57cb238d 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 49a41b903a 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 4c2908ca40 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 2b22ab08dd 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 2a8ac47cfe 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 873729b524 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new b5820f67bf 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new c1f7640d6f 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 066811401d 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new 9a15029d4b 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 8375e35fb8 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new cb3dc4dc86 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new a4c5e39fec 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new 4eb2d3d8bb 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new a8c944f24e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 83a435502e 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new d75c5e6139 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new 5790abb50e 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 67ef381ed0 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 8206e1449b 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 9a9ae2e53c 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new d95e6ec157 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new ba5cd6075c 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 911b607760 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 65f713bdf0 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new 0785efbcfc 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new abf75e0108 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 795480e05e 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 57e5895956 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 0b7d4d7948 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new fe4f1e30e4 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 3b23938b1f 89: onsuccess: #864: 1: Success after binutils: 25 commits new 4b7a6ccecc 90: onsuccess: #867: 1: Success after binutils: 4 commits new b36bc624dd 91: onsuccess: #870: 1: Success after binutils: 5 commits new e38471c0a6 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new abf4b833cb 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 820e65673c 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 43342411cc 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new f86a257d43 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new f191cb8150 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new ababc41f2c 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new bb28318add 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new 46410a1db0 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 6331106e80 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 8c0ee729c6 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 8b43b1d9d3 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new 74c15abd4f 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new b53401d772 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 5897516604 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new cca46daf55 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new aec8d68d70 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new e485d8683c 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 52bf1d20ff 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 4c1f6d591b 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 3484c0135c 112: onsuccess: #896: 1: Success after binutils: 24 commits new b3358cfa6b 113: onsuccess: #898: 1: Success after linux: 3 commits new 4ce2c47242 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new 4efa6a1457 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new 4499a596dc 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new ca535733dd 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 289fe3f635 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new d8f3e68ee6 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 4bf4e68561 120: onsuccess: #906: 1: Success after binutils: 29 commits new 0b27034e87 121: onsuccess: #908: 1: Success after glibc: 2 commits new 8eabe239ef 122: onsuccess: #909: 1: Success after linux: 2753 commits new 4346bd34a5 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new ca59dc066f 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new 3ffa2a16c4 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new dde09683a9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 4c1bff13d4 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new 2360d9d00f 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new b5e29c4276 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new e3fc945f3f 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new d073870fb8 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 381c2f1291 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new 5f7505301b 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new b9d246865f 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new f39059f9c1 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new 09513c21d9 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new e081f7f283 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new 9ac3560aa8 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 0c11dde529 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new d3923b19c4 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new ebb7f1c1bc 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 6bcfc9de66 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 83879ad096 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 578ca90dac 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new ac8f106374 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new fe03f25ee8 146: onsuccess: #939: 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 (332f18e093) \ 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 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 39688 -> 40748 bytes 04-build_abe-gcc/console.log.xz | Bin 214916 -> 215432 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8956 -> 9096 bytes 07-build_abe-glibc/console.log.xz | Bin 245528 -> 244904 bytes 08-build_abe-gdb/console.log.xz | Bin 39516 -> 39412 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2196 -> 2032 bytes 11-check_regression/console.log.xz | Bin 21344 -> 12416 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 36 +- 11-check_regression/mail-body.txt | 168 +- 11-check_regression/results.compare | 78 +- 11-check_regression/results.compare2 | 8383 +++++++++---------------------- 11-check_regression/results.regressions | 78 +- 12-update_baseline/console.log | 44 +- 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 | 170 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 78 +- sumfiles/gdb.log.xz | Bin 1892492 -> 1878724 bytes sumfiles/gdb.sum | 6514 +++++++++++++++--------- 31 files changed, 6716 insertions(+), 8887 deletions(-)