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

discards d4b81d4dfd 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards c2d84f23ed 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 4dce76280c 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards da402600f8 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 7f125b857a 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards febcfc6702 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards b03f433be7 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards e86f527ad7 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 4a61cc5fb1 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 0f65e783fe 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 7c7a684879 123: onsuccess: #655: 1: Success after binutils: 22 commits discards e427a60a3a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards d93b7228f9 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 4bef52ad3b 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 8f34749dc5 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 78c36eb813 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards ae19356323 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards f554926291 116: onsuccess: #647: 1: Success after linux: 3 commits discards bf46dd9318 115: onsuccess: #645: 1: Success after binutils: 27 commits discards f0ecb74733 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards b7d3e7c506 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 3660e391fd 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 7e786110e0 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards bc1975f254 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards e975058422 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards a95cefb7ce 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards ce4a7f60a4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 54966f88b0 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards bee4d02852 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 7c4c562614 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 80718b3871 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards d954066905 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards cbc6d3dc67 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards bc017ee48f 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 32be8a7840 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards eaa7d66588 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 6067889da5 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 9445db8f95 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards a76c7b6143 95: onsuccess: #619: 1: Success after binutils: 5 commits discards dabc6fd9a4 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d5ff6eeb14 93: onsuccess: #613: 1: Success after binutils: 19 commits discards fe6c6b23b9 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards c067c61083 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 6a5b7a4c6f 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 38bdd0956e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 936c9e3f6f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 8cc5d113f4 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 7a8dd91ed7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards a3ba799949 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 9c6d03106a 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards c43bd4cf7b 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 111c63ff9b 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 69422aeda8 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 8eaa64b80c 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 5e4f3723e5 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 75e497c2f4 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 9e0f3d630e 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 7ef4804898 76: onsuccess: #592: 1: Success after linux: 63 commits discards 7fcdd7b567 75: onsuccess: #591: 1: Success after gcc: 25 commits discards edf84bb125 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 267d263901 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 4ee8685827 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 94e7860f55 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards afba553da7 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 7be1371160 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 6f9159f65e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 6e2ffd2f4f 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 6d366f0156 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards f42f487a6b 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 39bcf8bc6d 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 29d9d37982 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 1c452feac1 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 678a197e91 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards e4062e6a8a 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 84450c3958 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards c0978c9194 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 0b6fdff899 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 54ad5726ef 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards a74ad1f576 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 1eeddb7089 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards eadda13e4a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 12e86e6e5c 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards cadbce5c76 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 9b9a0d124f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards e020ba8520 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 75f5243334 48: onsuccess: #559: 1: Success after binutils: 6 commits discards ccc65e6af6 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 707aade7b8 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards c3cd0279c2 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards ac9a3f41f0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 6d9277ce2e 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 49e357be4e 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 11da8c439a 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards efcc537f7f 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 4ac49e3301 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards bdaca1ebb6 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards c0f181a071 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards df63520056 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 5afa6f222c 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards d59ee2f4a0 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 2d1e9e93b4 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 78eab242a9 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 52b17bf385 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new ea01afa7c1 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 48642056de 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new af05189923 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 52df095adb 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 9707bb0a72 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 5703edaab0 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new d48a4df265 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 1f0a6240ad 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new e2add1c622 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 8a2bb16755 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new fbc6c58590 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 90aad0f5ef 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 15085824b1 47: onsuccess: #556: 1: Success after binutils: 12 commits new b1f4ed2dd0 48: onsuccess: #559: 1: Success after binutils: 6 commits new fe01618077 49: onsuccess: #562: 1: Success after binutils: 9 commits new c31311dd0b 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new ff881a53eb 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 69b9a4777d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 9f3368247a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 2da207a054 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new dbe5747d00 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new e4ea18cfd6 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new f814f14a3a 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 8332972283 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 8f7c9b214f 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new e5989ca0b8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 854945ff34 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 7939de9af1 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 8eb9f23c01 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 9f745c7214 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 7a6b628568 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 6d828e31bf 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new e44150cb47 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new f1cec5919e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new d8e25d942e 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new c537113a3d 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 3b15203050 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 1361519581 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new b748c78b3a 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new cd4f632097 74: onsuccess: #590: 1: Success after binutils: 16 commits new 8423cb50d1 75: onsuccess: #591: 1: Success after gcc: 25 commits new 4c323b86f9 76: onsuccess: #592: 1: Success after linux: 63 commits new 36aaec8156 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 191a9dddb8 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new ef1adaa220 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new eb906644e5 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 4c597407e7 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new b5076d794c 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 2511e201bd 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new ff83bc5097 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new 7264140b1c 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 381bd5191d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 86b4cfc5a7 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 70517e4be3 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 6680525412 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new fc23d5be55 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 16f7c4120e 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new b41a1a7b61 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 9615c4116e 93: onsuccess: #613: 1: Success after binutils: 19 commits new 7cf341aaa5 94: onsuccess: #616: 1: Success after binutils: 2 commits new 47f2b84cf1 95: onsuccess: #619: 1: Success after binutils: 5 commits new f030360a98 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 182d4d59a2 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new b82cba040a 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 4ab9c4f26e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 6869959874 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new fcd4675464 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new b78e9c39e7 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 0e90992c3b 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 65b736fe68 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 82279f6561 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 31245ae96e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 68417ef9f7 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 0d21bd20e4 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new ce0985d439 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new ddf1c1707b 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new b28f064f31 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new f9c18b6ecb 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new e5b9271d88 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 5f07585e98 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 6153548ee5 115: onsuccess: #645: 1: Success after binutils: 27 commits new 2741c3033f 116: onsuccess: #647: 1: Success after linux: 3 commits new 24d7a1bcb9 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 3c768b157c 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new d7bc6b7106 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 01b0b1f513 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new dfab622e23 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new d9681b3df5 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 179287660e 123: onsuccess: #655: 1: Success after binutils: 22 commits new d35975e7c7 124: onsuccess: #657: 1: Success after glibc: 2 commits new fd074b933d 125: onsuccess: #658: 1: Success after linux: 3224 commits new ff841a06c9 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new eebe88ae19 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 4e311db3b2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 1257af1114 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new dca76cd63d 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 2eaf221c96 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 24cfd67505 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 4a626a5956 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 253c89a97d 134: onsuccess: #667: 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 (d4b81d4dfd) \ 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 1740 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40144 -> 40796 bytes 04-build_abe-gcc/console.log.xz | Bin 216348 -> 214284 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 244724 -> 245304 bytes 08-build_abe-gdb/console.log.xz | Bin 39464 -> 39844 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2200 -> 2176 bytes 11-check_regression/console.log.xz | Bin 6040 -> 6124 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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 | 38 ++-- sumfiles/binutils.log.xz | Bin 63148 -> 63324 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83828 -> 83856 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122320 -> 122512 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 393 insertions(+), 393 deletions(-)