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-arm in repository toolchain/ci/base-artifacts.
discards c6040a069725 138: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] discards 055c28c48065 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 1 [...] discards 100d9741f195 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 232aa9bffc3d 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards b1361cb71804 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] discards 1e9232ea6f42 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] discards 41c169b638b4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] discards ce102ca87f57 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] discards b374e3a0a5e0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] discards 97745457480f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards 9f112fb62d00 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 4f050e7a53b9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 3ef9d22e309b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 8c4b04317c61 125: onsuccess: #614: 1: Success after linux: 12 commits discards 4da7d59234a9 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 7776a06838b2 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards dbfc9580f7fe 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 6b6660a8cbdc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards afb1d74b59bc 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards 63ec48f479ad 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 2caaef4d9da5 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards b995a54f9704 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] discards d8a68ca2208f 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 2873d7a3c07b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 93dc1922c6a4 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards 40498f6f981c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards a7532b0dce44 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] discards b42afc267fe1 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] discards 356da61c7e78 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards c85e1c204037 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 43de1781d4e9 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 1b924bb7925c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards ecc48ca78242 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards 755283976299 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards 5dfeec1867e2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 3d41eab4a7a7 103: onsuccess: #589: 1: Success after binutils: 3 commits discards cdddeece6fa1 102: onsuccess: #586: 1: Success after binutils: 5 commits discards fbb921661bde 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] discards 856a8a9d1091 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] discards c2a96bbfa3de 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards 9974a968ca84 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards c1df7c0cb2fb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards 44852b9586b9 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 5db14b300c75 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 083635c536d9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 59abaa52834f 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 0020b0282378 92: onsuccess: #575: 1: Success after linux: 34 commits discards 34c456e3fcd0 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 5df8f35e4ae0 90: onsuccess: #572: 1: Success after binutils: 15 commits discards ba064eb833d6 89: onsuccess: #570: 1: Success after linux: 11 commits discards e69fec1f0c35 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 0d7869706046 87: onsuccess: #567: 1: Success after binutils: 8 commits discards ca2f44e5551a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 62f5285fef27 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards ada295523679 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 4670caad4c15 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards c953c65bd34e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards be9d63ee1653 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 4039d93b4613 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 9d8250914dae 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards 4969c4987c0d 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards 4ac67986ec76 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards f366bfae6ef1 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards 34eb6c90fa09 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] discards f04df20df3ad 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 87ec573da85e 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards ef8c83d72b62 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 9129b19335b7 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 0295a6ff14c2 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 7a088a61be01 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards f19f15b0e29c 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 5c9bda26b314 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 9f561d8b4551 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards ed8ac92a9f32 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards ac2bbdbdd223 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 25c14d31b4d2 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards c33c21170e12 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 3826e4095448 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards 7ffee6857f59 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 3ee67d6dc856 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 5dbf49842518 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] discards 43c27c3b731b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] discards 7ba4ef4c9d57 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards a45a45eb9871 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards 1d8f9d7c4a85 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards cd3752a100ce 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 4a98c0feae03 52: onsuccess: #528: 1: Success after binutils: 8 commits discards a02a2e8b14ea 51: onsuccess: #525: 1: Success after binutils: 8 commits discards e76a662bc935 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] discards d2a7676ad20c 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] discards 8b5598525e97 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] discards 5e2aad779bc3 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] discards 5475f8735f10 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 45b4e6c5e521 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] discards ad126c2c3c69 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 2b59be65afd2 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards e48aa63a16ed 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards 8568d196a717 41: onsuccess: #514: 1: Success after linux: 64 commits discards 4e7e6def6aca 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] discards 96c12d27b67f 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 6e8e2a5f33c8 38: onsuccess: #508: 1: Success after binutils: 3 commits new 2d065fb282eb 38: onsuccess: #508: 1: Success after binutils: 3 commits new 1ea40eda8cf8 39: onsuccess: #511: 1: Success after binutils: 8 commits new 1d30943c804a 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] new 335100e686f8 41: onsuccess: #514: 1: Success after linux: 64 commits new 7bd227bc02cc 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new dbaf1f1f9b7c 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 05fa1e7b9136 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 67f771cb6192 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] new a66ac10da244 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 68ce37e110e5 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] new d0cbc59bed82 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] new 2a7ac1baff94 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] new 7e5e0a5e89f4 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] new c4fbe2b0ccab 51: onsuccess: #525: 1: Success after binutils: 8 commits new bc48da4b6e16 52: onsuccess: #528: 1: Success after binutils: 8 commits new e4bf311de9e3 53: onsuccess: #531: 1: Success after binutils: 12 commits new cbcf3c90efd3 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new 880495ecec8d 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new ff27b8ad07d8 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new e89fadd5e89f 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] new d14aee5266a2 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new 47ccd1d705b3 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 29d1ce91f444 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new bc489d4897e6 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new ebcec729113d 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new c3d4130015b9 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new f4020a61789a 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 01e565adfdd5 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 0d8e3105ee7f 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new f2d4aab95ecd 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 830a4ba92878 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 6548a2ed5cd1 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 0fc48c5274ef 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new dc098f8189ea 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new f633870196a0 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 6b2463e22099 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 2f73678867a0 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 4a15220c8cd6 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] new 74b5eb501c0c 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 5f19f6d91dc8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 31a4623dedbd 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new edc1884ed3df 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new ef052d6ae44a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new a28b092120da 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 0ec5be12cfce 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 3c9f2dae7f7d 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new afbac1392ee2 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 114eec73246a 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new a572e4cd8a4c 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new da762d766542 87: onsuccess: #567: 1: Success after binutils: 8 commits new 4cb308e88a00 88: onsuccess: #569: 1: Success after glibc: 10 commits new e0e93e46ecef 89: onsuccess: #570: 1: Success after linux: 11 commits new 42aff413421e 90: onsuccess: #572: 1: Success after binutils: 15 commits new 033e8fb57e7a 91: onsuccess: #574: 1: Success after glibc: 3 commits new 1de75128aad2 92: onsuccess: #575: 1: Success after linux: 34 commits new 09a6477d04ec 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 073cefcdc9d3 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new fd8d9d55dfda 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 85985bf71aa7 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 928a55a40bca 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new f106060165e2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new ad64a034196d 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 8337b82aad49 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] new f6ec28a9fc73 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] new da51d2152318 102: onsuccess: #586: 1: Success after binutils: 5 commits new a6ed9bc753e0 103: onsuccess: #589: 1: Success after binutils: 3 commits new e00d5f8daa81 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 24104032e734 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 9ea941995a94 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new a88516416ef3 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 7f7efa361bf9 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new 2687a296233c 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new bfbc0bfa7509 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new acd6a89fa792 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] new d550a2cb0938 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] new 65aab1a39cc5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new 992c82bbd659 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new 4553efce3f8d 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 2823851c7d86 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 65309dff44d4 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] new 8a131676881b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 4e692740f7cd 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new 92f1cc887584 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 4e337aa06026 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new 7476edeb6fb5 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 6687fe3169a7 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new efaccbb78751 124: onsuccess: #612: 1: Success after binutils: 18 commits new aa4f5a6e04cd 125: onsuccess: #614: 1: Success after linux: 12 commits new e23596a42e39 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 753aaa092bd8 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 46164bc90896 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 11e8ac1862bf 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new 51ae77f1b520 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] new 214e3c3d1651 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] new 35bff9dcc57e 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] new 7d910d584a94 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] new 36ef04ed3570 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] new 2132a24530dd 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 54c8117fa074 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new e36dfd346353 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 1 [...] new d7b9d9f8c551 138: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] new dfbf7be137dd 139: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...]
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 (c6040a069725) \ 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 1728 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 54480 -> 53736 bytes 04-build_abe-gcc/console.log.xz | Bin 237368 -> 238704 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9048 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 235180 -> 238564 bytes 08-build_abe-gdb/console.log.xz | Bin 52056 -> 52160 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3844 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2304 -> 2368 bytes 11-check_regression/console.log.xz | Bin 15212 -> 13152 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 57 +- 11-check_regression/mail-body.txt | 187 +- 11-check_regression/results.compare | 91 +- 11-check_regression/results.compare2 | 5586 +++++++++-------------- 11-check_regression/results.regressions | 91 +- 12-update_baseline/console.log | 66 +- 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 | 189 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 91 +- sumfiles/gdb.log.xz | Bin 1797748 -> 1835104 bytes sumfiles/gdb.sum | 7328 ++++++++++++++++++++----------- 31 files changed, 7330 insertions(+), 6410 deletions(-)