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 2da2a874d3 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 241ca87bd7 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 1abbe412c6 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 98305c9ef5 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 41344a1884 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 57293da1e3 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 2946e340b2 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 011bafe4d5 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 0fff60485b 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 104366af7a 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 7f6f0fa49f 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 5df70f0d3f 102: onsuccess: #527: 1: Success after binutils: 5 commits discards af67ccc406 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 370efb876c 100: onsuccess: #521: 1: Success after binutils: 10 commits discards fbd304f1d3 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 261f823001 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards af58afa303 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 5a2b213215 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 0db56929c3 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 448c6a59bd 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 6cf5d6e636 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 8ef383990b 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards a2799ec5c6 91: onsuccess: #511: 1: Success after linux: 27 commits discards 9da125fd54 90: onsuccess: #510: 1: Success after glibc: 5 commits discards d79cedbb66 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 23dfe6c939 88: onsuccess: #506: 1: Success after linux: 34 commits discards e79f0ad660 87: onsuccess: #505: 1: Success after glibc: 7 commits discards b1db87504c 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 01f1b12269 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards ff144f6f4e 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 56a44ec816 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards bb94677be9 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards ac71e306e5 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 11725ea71b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 565f3391e1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 80e3dff5ae 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards a3230942c7 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 16e754a6bc 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 4270b44cd5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards be50382bd0 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 1845c5cdd1 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 0e0a363b0c 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards fde9aea884 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards cf6cab1004 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 98315f5d8e 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards d116666a72 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 0a62762944 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 704f13f49a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 0654e99cb5 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 966beb909f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards abca15e34d 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 15c217e3cc 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards c225aca832 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards a89d2669f1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 1073819ed8 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 5cb1a91e1f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards bea153cfb8 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 05bc661b0b 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 1dcacc6179 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 1bd21cca49 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards dd8708e10c 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 72124428ae 52: onsuccess: #467: 1: Success after binutils: 9 commits discards d62a74877f 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 1013ed546a 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 02def14d88 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards d7f384a65f 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards e41e02a4e0 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 014f550953 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 953ef68973 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 2a5c5cb5ac 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards d4af562055 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 6704172777 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 7229d95f8c 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 2fc8712088 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards f723279882 39: onsuccess: #447: 1: Success after binutils: 5 commits discards ccb24fe611 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 250eb14def 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 5ff3dba10e 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 51b3f45ca3 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards c42b92a495 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards ddefb3c785 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards d21675eb2d 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 5e62372465 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 94e3d41500 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards e2c35fc059 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards bcfaa76ced 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards db7e8efb9c 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 0cc8216441 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 2f6cb335f9 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards dba748bf0d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 37c14886c4 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 308fb2907b 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 232b3f28e0 21: onsuccess: 1: Successful build after linux: 79 commits discards a7f6839efa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd11b285b4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c050777855 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bd0521ce6a 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d160ed4eed 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c4fba5c321 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e5715cb871 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3ed2097a8 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 96c7b73790 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0489ea685f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 521108100e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c929ae917d 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 053acf2229 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new eea1b7a250 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 38815af82f 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6903b0f5a4 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e5c95807ad 21: onsuccess: 1: Successful build after linux: 79 commits new b02d5fc829 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 41b6f2fa6d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 0c2ff3aad7 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 05ac285d35 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 48e252ad05 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 0ad16437bd 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 2389b257a1 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 9b59272f7d 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new ad0052b50c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 2b444d61d0 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new cdcca4cda8 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 3f02517dbe 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 6da9afa820 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 02cb21ff68 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 6f505f3b6c 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new d6a94d17e8 37: onsuccess: #443: 1: Success after binutils: 2 commits new c3dc95126c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 9784f76983 39: onsuccess: #447: 1: Success after binutils: 5 commits new 2775deedb6 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 243079b657 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 9bace4fdc6 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new a7df4f81a9 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new f41dc030f5 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 0657dd3c07 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 52ce7bd2d0 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 05dfbe61d4 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new d8de576c1d 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 7db112db40 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 94343e8440 50: onsuccess: #461: 1: Success after binutils: 12 commits new 4188166c81 51: onsuccess: #464: 1: Success after binutils: 6 commits new d3741e630b 52: onsuccess: #467: 1: Success after binutils: 9 commits new e349d2ed10 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new be17401897 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 14a6484763 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 0272968c72 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new b17bd5ea69 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new d91e0cdf4f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new e682b30f49 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 0d5d2a01dd 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 03a5789de5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 8ee1e6bb05 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new e3794ea9b1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new d65fe3ec5f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 11e7c16b0f 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new d346da63ea 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 7533069b05 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 9ea205e052 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 22bb55c2d0 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 8049a77da7 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 872c1447ff 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 2dc550c897 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new a1c0e496eb 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new ba29a86892 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new de182c8995 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 563b6a3c47 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 0c79f2ca2c 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 16dc08a108 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 1282e84a32 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new a4f5eed08e 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 363d9b0745 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new fd5e258080 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 678c7c17c0 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ec6ec91d91 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new d016c0725e 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 41b46ce621 86: onsuccess: #503: 1: Success after binutils: 12 commits new 814570d907 87: onsuccess: #505: 1: Success after glibc: 7 commits new 198e156da8 88: onsuccess: #506: 1: Success after linux: 34 commits new 5f0e3eb8d6 89: onsuccess: #508: 1: Success after binutils: 12 commits new c1e5c88040 90: onsuccess: #510: 1: Success after glibc: 5 commits new 2fad2365d5 91: onsuccess: #511: 1: Success after linux: 27 commits new 51ba86d720 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 1e3f4f938d 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 40b8aedc7b 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 9c227887d0 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 4e1c4ff2f4 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 10fa29495f 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new ef4a43b8fd 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 2d2bfa11ac 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 19170cd14f 100: onsuccess: #521: 1: Success after binutils: 10 commits new e7f9fe1afe 101: onsuccess: #524: 1: Success after binutils: 2 commits new 9d477bcbb4 102: onsuccess: #527: 1: Success after binutils: 5 commits new 04f9e7675d 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new c41e09355e 104: onsuccess: #530: 1: Success after gcc: 7 commits new 06a68a9b73 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new bf3985b794 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new b11bc1b826 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 42348654df 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 0b8f89ef74 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 33d9721450 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new df65621665 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 31c44aacf3 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new 9a352d6083 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new d1bc973eb9 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...]

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 (2da2a874d3) \ 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 1724 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 53584 -> 52796 bytes 04-build_abe-gcc/console.log.xz | Bin 234572 -> 233608 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9548 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 234808 -> 234684 bytes 08-build_abe-gdb/console.log.xz | Bin 51352 -> 52280 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2628 -> 2780 bytes 11-check_regression/console.log.xz | Bin 5844 -> 5768 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_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 62680 -> 62392 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98084 -> 98036 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131524 -> 131548 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 404 insertions(+), 404 deletions(-)