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_binutils/master-arm in repository toolchain/ci/base-artifacts.

discards f4c63db5e3 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 8c7520995b 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 57c2437e3b 100: onsuccess: #521: 1: Success after binutils: 10 commits discards aaeba419ef 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 15d9859c6e 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 2392881092 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards af520a1496 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards ddd9bae991 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards edde6dddd8 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 016b80c424 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards c8d287b24d 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards db872b583c 91: onsuccess: #511: 1: Success after linux: 27 commits discards 8212827aad 90: onsuccess: #510: 1: Success after glibc: 5 commits discards d9c54f0258 89: onsuccess: #508: 1: Success after binutils: 12 commits discards f23cc67c8f 88: onsuccess: #506: 1: Success after linux: 34 commits discards ab6eaca20f 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 152a7562d0 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 7042d3355a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards b44e86a2af 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards c246bc8907 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards ce4ec1cfb7 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 2d9ee5b2d3 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d9523af140 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards a47801432f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 35008fab77 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 3ee1ba3ea8 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 9f3bd6841c 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 3b164ffbef 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 129d0996be 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 8066feea11 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 95a01b11a3 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 94e24ee30f 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 9e72b75cd3 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 2f536f2812 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 6ebff0dec5 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 37a11cf4c1 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards c85b334353 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards c9d976099b 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 913735cb14 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards bf411b97d4 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 693f66f9a9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards f76e29e8bd 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards c48595b2bd 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards f5b3464335 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 13aa38525e 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 9e774d7647 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 145d32ef0d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 2244f8f8cb 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 8c5e88ae0c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards c8491190b5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 058088da88 52: onsuccess: #467: 1: Success after binutils: 9 commits discards c9f5e7941b 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 6a078d7aa1 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 16e1d06a2f 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards c290746073 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 9b10387565 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards ac0305f710 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 1047ad4756 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards a64294ba36 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 3f7775d4b0 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 091561f41f 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 78509d1cfe 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards f7147372d5 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 7474c543d0 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 9b3ef471eb 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards cba4e21449 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 994a07d4fa 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 072c740d53 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards b5f2698c21 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 6393f4cdee 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 8322194978 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards dfbc7b50d3 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 599a22e69a 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 7112616d1d 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 3592780831 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 7e503bdb02 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 9d78cfeed2 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 12812f7d73 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 5e32853e71 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 4601a79c10 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 5ceae8cac0 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a6f76425e8 21: onsuccess: 1: Successful build after linux: 79 commits discards 78ee892fec 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 934c410ddd 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe87497ff6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b2228e3d7e 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1bd3feb0e4 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc17a8fcf3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce12390a33 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 281a451058 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e7c148b8b0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8e7c076251 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards caae9173d6 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3bba6cb86 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5a84c4bf58 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 44a611f4ac 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8142dd1c64 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 253267125b 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards caa062a71f 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6653052042 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8a32a5e073 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 991e62dba9 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6a31cd0981 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cce1a31c31 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 46f5b975a8 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new a5e1013381 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 40b8d47773 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 95e3d67ac3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fe1b70fb57 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 75126fc9b3 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d41bf13ed4 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f155f8aed 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc09414952 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 70057033f0 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 53124c383b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b7c513c2c 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f1d571929e 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 584d1eb4ed 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 55a81c1fc8 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bece752b79 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2704e46a0a 21: onsuccess: 1: Successful build after linux: 79 commits new 4e09fd348b 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53dee40fa9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new eb9b2725b1 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new a9662f5457 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new df6a83e116 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 59c578fabf 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 8124461c7f 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 1ff06668e6 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 944c615913 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 623545539e 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new aa0dc9e044 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 416890ada3 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 4e1e81ecb2 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 54008a08e6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 638811da99 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new ae58d26d97 37: onsuccess: #443: 1: Success after binutils: 2 commits new 728e265140 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new bb7703e8d1 39: onsuccess: #447: 1: Success after binutils: 5 commits new de0b711a74 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 515eee1195 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 20e989fd38 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 4e988a5686 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new b4576c0c6d 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new cb7024ee0b 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new f62c40e6d9 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new b3c2bb16fd 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 9e2611e795 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 6a573d404c 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new d36a7ed311 50: onsuccess: #461: 1: Success after binutils: 12 commits new 3534f6c2de 51: onsuccess: #464: 1: Success after binutils: 6 commits new fe74caf74a 52: onsuccess: #467: 1: Success after binutils: 9 commits new 397ee8aca5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 284f6ea497 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 9955f27fb9 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new efed2e5493 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 5ec3023b3a 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 532dfb1401 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new e670ea99bc 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new a1df7d656d 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 060aa45107 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new b746e69b62 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 9114fab29d 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 439eae1ea2 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 277ae56897 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 0e6be98d63 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 39ce2e638d 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 0290be894b 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new d9e2a35db3 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 08a5d4a616 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 03cac2eb80 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new de940e7bff 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 43d73c37b1 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new acba51cc47 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 54ef0a0879 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 207732a32e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new ce2bb066df 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 15fdb2bcc7 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 0e5a32675e 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 346dcb7c4f 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new d0c030e535 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new f171625652 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 21dfdcf4c2 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 05d8a2f75c 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 2bfdb70f51 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 0d05c33136 86: onsuccess: #503: 1: Success after binutils: 12 commits new 69ef52633c 87: onsuccess: #505: 1: Success after glibc: 7 commits new 33b51d2482 88: onsuccess: #506: 1: Success after linux: 34 commits new 9e79d8a2a3 89: onsuccess: #508: 1: Success after binutils: 12 commits new e780b333d8 90: onsuccess: #510: 1: Success after glibc: 5 commits new 59bef7dbe3 91: onsuccess: #511: 1: Success after linux: 27 commits new e616f97b5d 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 454dee972e 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new c416b9fbdb 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 66a61bcb81 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 37f05d99f0 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 7b6045c49a 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new a4cc560623 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new d102ac9acd 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 53761f254d 100: onsuccess: #521: 1: Success after binutils: 10 commits new bf7c1c1761 101: onsuccess: #524: 1: Success after binutils: 2 commits new 46e2321990 102: onsuccess: #527: 1: Success after binutils: 5 commits new 0397b5e6cd 103: onsuccess: #529: 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 (f4c63db5e3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]

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 1620 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 51160 -> 53460 bytes 04-build_abe-gcc/console.log.xz | Bin 233916 -> 236744 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9692 -> 9096 bytes 07-build_abe-glibc/console.log.xz | Bin 235008 -> 238984 bytes 08-build_abe-gdb/console.log.xz | Bin 51028 -> 53180 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3924 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2272 -> 2104 bytes 11-check_regression/console.log.xz | Bin 4700 -> 6536 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 30 ++- 12-update_baseline/console.log | 40 ++-- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62476 -> 62220 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 98040 -> 98036 bytes sumfiles/gas.sum | 273 +++++++++++----------- sumfiles/ld.log.xz | Bin 131440 -> 131508 bytes sumfiles/ld.sum | 348 +++++++++++++++-------------- 30 files changed, 415 insertions(+), 398 deletions(-)