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 73ad7a096667 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 1 [...] discards deee451d6beb 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 989401c654dd 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 8fc191085379 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] discards 8e88ada1239a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] discards 8af2f9948013 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] discards db056d89f401 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] discards b6b52713b0c8 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] discards a9d6bb01fd62 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] discards e04192f29499 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 34bb89ce0bc5 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 6552daddfccc 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 2dc24fd96709 125: onsuccess: #614: 1: Success after linux: 12 commits discards 777f695eb49e 124: onsuccess: #612: 1: Success after binutils: 18 commits discards ee8925abf2cb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards f8d6a6e528fc 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards 90b82079de57 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards 2a3c4e272bea 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards ec4efbdc991e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 7223d393ee6f 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards d7aeec9c40e1 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] discards b68ad0f923d0 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 40a71d6547bd 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards c1e500ea9e27 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] discards 25b744bf1730 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] discards e9e0216f9832 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] discards 7673cfca600b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] discards 90af7f2e0b3c 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards aeaeacac12c8 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 53a27273aa08 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 58057a3dcf33 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 9961e4affc16 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards 9d2ef79331c6 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards e983b50b5903 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 51db3811ce18 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 89e71f9c1bcf 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 59c8772f8ce3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] discards 1205fc736a0b 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] discards 79b416f2b24a 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards fc5bcff757dc 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards 90ea17655d48 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards ad4869e04fb2 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 36f9d86d026f 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 3ddc5a004689 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 7050c95b2bc7 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards e598b2ff3d3e 92: onsuccess: #575: 1: Success after linux: 34 commits discards 3eccb6076e75 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 5e40c8360427 90: onsuccess: #572: 1: Success after binutils: 15 commits discards fb5127aa46b8 89: onsuccess: #570: 1: Success after linux: 11 commits discards aa05f4cc9d0b 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 1b008fdc8f98 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 503d0dda13c4 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards e902966d6951 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards d08f3b0cbd4a 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards caf19bfe1a57 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards e5e78138cfc3 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 63572995cec9 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 8ce574a8337c 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] discards 228fa8e2a5dc 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] discards c9da5d93e999 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] discards bcf86cc3ccd6 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] discards 0aa897eee5ff 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] discards de23a18f753d 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] discards 5490f9a887e8 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards f56e7de8014f 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 5a65c3a229b3 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 6218b4dce9be 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards b2e8d4608fa3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 52873c42bc9e 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards bd9d95553be2 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards cf46e002ef8a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards fac769de6f0e 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 83792d4a43dd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] discards c338c1e8051f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards bec57b5cf334 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 1fbaa127f2bb 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 50ab7de426b4 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards d0ae92ac7711 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards 139bb5e093e7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards e1cbaca80a1d 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] discards c68e1c24cda6 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] discards 583038f94fd8 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] discards b7d647c55cd1 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] discards b1760338235a 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] discards b1469f6598a7 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 0dfa61522a40 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 9c5327970635 51: onsuccess: #525: 1: Success after binutils: 8 commits discards d7bb9a248b29 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] discards d74b8dd02650 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] discards 2ee8910e3de1 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] discards c73952eedbc9 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] discards 88eda296cd6c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards f3b0e53eb396 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] discards 93cd72b88a71 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards dad64e4e178c 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 46d629e44944 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards 03cf51095d29 41: onsuccess: #514: 1: Success after linux: 64 commits discards 9db18993ec43 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] discards 06981c62d604 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 947bdf4f0a1a 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 566a42a05d68 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb6 [...] new c4a23ff0247d 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb6 [...] new 6e8e2a5f33c8 38: onsuccess: #508: 1: Success after binutils: 3 commits new 96c12d27b67f 39: onsuccess: #511: 1: Success after binutils: 8 commits new 4e7e6def6aca 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121- [...] new 8568d196a717 41: onsuccess: #514: 1: Success after linux: 64 commits new e48aa63a16ed 42: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new 2b59be65afd2 43: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new ad126c2c3c69 44: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 45b4e6c5e521 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/g [...] new 5475f8735f10 46: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 5e2aad779bc3 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/g [...] new 8b5598525e97 48: onsuccess: #521: 1: Success after binutils/gcc/linux/g [...] new d2a7676ad20c 49: onsuccess: #522: 1: Success after binutils/gcc/linux/g [...] new e76a662bc935 50: onsuccess: #523: 1: Success after binutils/gcc/linux/g [...] new a02a2e8b14ea 51: onsuccess: #525: 1: Success after binutils: 8 commits new 4a98c0feae03 52: onsuccess: #528: 1: Success after binutils: 8 commits new cd3752a100ce 53: onsuccess: #531: 1: Success after binutils: 12 commits new 1d8f9d7c4a85 54: onsuccess: #533: 1: Success after binutils/gcc/linux/g [...] new a45a45eb9871 55: onsuccess: #534: 1: Success after binutils/gcc/linux/g [...] new 7ba4ef4c9d57 56: onsuccess: #535: 1: Success after binutils/gcc/linux/g [...] new 43c27c3b731b 57: onsuccess: #536: 1: Success after binutils/gcc/linux/g [...] new 5dbf49842518 58: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new 3ee67d6dc856 59: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 7ffee6857f59 60: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 3826e4095448 61: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new c33c21170e12 62: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 25c14d31b4d2 63: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new ac2bbdbdd223 64: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new ed8ac92a9f32 65: onsuccess: #544: 1: Success after binutils/gcc/linux/g [...] new 9f561d8b4551 66: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 5c9bda26b314 67: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new f19f15b0e29c 68: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 7a088a61be01 69: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 0295a6ff14c2 70: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 9129b19335b7 71: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new ef8c83d72b62 72: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 87ec573da85e 73: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new f04df20df3ad 74: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 34eb6c90fa09 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/g [...] new f366bfae6ef1 76: onsuccess: #555: 1: Success after binutils/gcc/linux/g [...] new 4ac67986ec76 77: onsuccess: #556: 1: Success after binutils/gcc/linux/g [...] new 4969c4987c0d 78: onsuccess: #557: 1: Success after binutils/gcc/linux/g [...] new 9d8250914dae 79: onsuccess: #558: 1: Success after binutils/gcc/linux/g [...] new 4039d93b4613 80: onsuccess: #559: 1: Success after binutils/gcc/linux/g [...] new be9d63ee1653 81: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new c953c65bd34e 82: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 4670caad4c15 83: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new ada295523679 84: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 62f5285fef27 85: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new ca2f44e5551a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 0d7869706046 87: onsuccess: #567: 1: Success after binutils: 8 commits new e69fec1f0c35 88: onsuccess: #569: 1: Success after glibc: 10 commits new ba064eb833d6 89: onsuccess: #570: 1: Success after linux: 11 commits new 5df8f35e4ae0 90: onsuccess: #572: 1: Success after binutils: 15 commits new 34c456e3fcd0 91: onsuccess: #574: 1: Success after glibc: 3 commits new 0020b0282378 92: onsuccess: #575: 1: Success after linux: 34 commits new 59abaa52834f 93: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 083635c536d9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 5db14b300c75 95: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 44852b9586b9 96: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new c1df7c0cb2fb 97: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new 9974a968ca84 98: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new c2a96bbfa3de 99: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 856a8a9d1091 100: onsuccess: #583: 1: Success after binutils/gcc/linux/ [...] new fbb921661bde 101: onsuccess: #584: 1: Success after binutils/gcc/linux/ [...] new cdddeece6fa1 102: onsuccess: #586: 1: Success after binutils: 5 commits new 3d41eab4a7a7 103: onsuccess: #589: 1: Success after binutils: 3 commits new 5dfeec1867e2 104: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 755283976299 105: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new ecc48ca78242 106: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 1b924bb7925c 107: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 43de1781d4e9 108: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new c85e1c204037 109: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 356da61c7e78 110: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new b42afc267fe1 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 4 [...] new a7532b0dce44 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 6 [...] new 40498f6f981c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/ [...] new 93dc1922c6a4 114: onsuccess: #601: 1: Success after binutils/gcc/linux/ [...] new 2873d7a3c07b 115: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new d8a68ca2208f 116: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new b995a54f9704 117: onsuccess: #604: 1: Success after binutils/gcc/linux/ [...] new 2caaef4d9da5 118: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 63ec48f479ad 119: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new afb1d74b59bc 120: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 6b6660a8cbdc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new dbfc9580f7fe 122: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 7776a06838b2 123: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 4da7d59234a9 124: onsuccess: #612: 1: Success after binutils: 18 commits new 8c4b04317c61 125: onsuccess: #614: 1: Success after linux: 12 commits new 3ef9d22e309b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 4f050e7a53b9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new 9f112fb62d00 128: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 97745457480f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/ [...] new b374e3a0a5e0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/ [...] new ce102ca87f57 131: onsuccess: #621: 1: Success after binutils/gcc/linux/ [...] new 41c169b638b4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/ [...] new 1e9232ea6f42 133: onsuccess: #623: 1: Success after binutils/gcc/linux/ [...] new b1361cb71804 134: onsuccess: #624: 1: Success after binutils/gcc/linux/ [...] new 232aa9bffc3d 135: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 100d9741f195 136: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new 055c28c48065 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 1 [...] new c6040a069725 138: onsuccess: #628: 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 (73ad7a096667) \ 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 1736 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 53120 -> 54480 bytes 04-build_abe-gcc/console.log.xz | Bin 235504 -> 237368 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 9048 bytes 07-build_abe-glibc/console.log.xz | Bin 235180 -> 235180 bytes 08-build_abe-gdb/console.log.xz | Bin 52004 -> 52056 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2256 -> 2304 bytes 11-check_regression/console.log.xz | Bin 13576 -> 15212 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 33 +- 11-check_regression/mail-body.txt | 203 +- 11-check_regression/results.compare | 94 +- 11-check_regression/results.compare2 | 4617 +++++++++------- 11-check_regression/results.regressions | 96 +- 12-update_baseline/console.log | 36 +- 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 | 205 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 96 +- sumfiles/gdb.log.xz | Bin 1781480 -> 1797748 bytes sumfiles/gdb.sum | 8748 +++++++++++++++++++++---------- 31 files changed, 8845 insertions(+), 5337 deletions(-)