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 9deb4efad1 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 9e56407166 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 6715519179 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards ce6cf8501f 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 8ff84b6f35 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 3b7bb100da 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards ffd9a2b057 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 39c39d7cfc 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 04b25d442f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 76f46abded 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 67710ce1ac 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards e3d17fb640 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 62953eeb3d 125: onsuccess: #658: 1: Success after linux: 3224 commits discards c600faaaa4 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 4e18886145 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 597a490f42 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 6d4b001424 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 2dfc7715c6 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 5acff57975 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 454572f218 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 65f49b34d8 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 3683ecb4ec 116: onsuccess: #647: 1: Success after linux: 3 commits discards 2071d79275 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 9c13fba1f8 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 5a3c993bb2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 666e6bc02b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 22e1d89c78 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards f57e1d41f0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 65d147d274 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 1dff22dc89 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards b8d5710462 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 6de7f8ec4d 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 63af4a87cf 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards aad75c6437 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 251bde6693 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 244124d045 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 909dec2259 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards cf32cd2414 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards a3a240346b 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 288dfbc529 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards c87068a598 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 7976e3e606 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 46914b40a5 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 3b5d75e10f 94: onsuccess: #616: 1: Success after binutils: 2 commits discards dc0feccd7c 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 0d6ce8cf13 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 44a32b80af 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards b297f07352 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards c2bc6ede92 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards d25cb172f2 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards d72240a2eb 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards b560c0c141 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards dc0875e14a 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards c7924e2987 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 8c10a36af7 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 069903b6c0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 4973af3048 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 5280bc8fd1 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 8cdfe4855c 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 9b549465da 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 4154ed50da 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 1e889424ef 76: onsuccess: #592: 1: Success after linux: 63 commits discards 054e509168 75: onsuccess: #591: 1: Success after gcc: 25 commits discards bc505d035f 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 56f0617cbc 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 8dbb4c0ee6 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 7f1a144f3c 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 512b513f33 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards b275f24175 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards d90b031620 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 01520a48c9 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards cbe388af4b 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 30cb4980fb 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards ca57995b2f 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 000ddfcafe 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards fbf796f977 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 6bd8a030b9 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 3bf0285e47 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 36268041dc 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 313223e15b 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards e3ca238c4d 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 89cddb85d7 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards b0990e2b16 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 02e414a92f 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 5937517002 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 1fc92bd9e4 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 78fc5f2967 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards ff68ef2003 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards caac32843d 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 67d4a50fb5 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 59d529825e 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 1921b6b06e 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 0f78e1bfce 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards d02e261a46 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards ce36a5ae9c 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 2f02594b84 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 505060969e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 0f677e3fe7 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards e3492257b2 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 084b870875 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 7ffadd827a 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new fad29493ab 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 3c011327e2 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 629562d77d 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 37b3d8fe53 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new bffb62fbb8 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 0be958c6db 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 6484b93557 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 953a8caf56 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 78d23e5fe5 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 51db3b0061 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 66d2749721 47: onsuccess: #556: 1: Success after binutils: 12 commits new a3ea6ef046 48: onsuccess: #559: 1: Success after binutils: 6 commits new 35e073676b 49: onsuccess: #562: 1: Success after binutils: 9 commits new 6c1bda815d 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new dfbeb20a0e 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new e9bf68409d 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new d839aceb7f 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 97a1deab53 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 15afdb196c 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 33ca6ce724 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 63c12d7aa0 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 194268fbb9 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new e08c07c71f 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 88213676dc 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 69e439dd4c 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 575cb8e98f 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new c40189e85b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new f60824194e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 1d21a4656d 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 9926739444 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 6f7e847216 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new eba85484bd 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 3edd7fde3b 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new c1e27673af 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new e76ec4c095 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 3128b4e93e 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 77ab7ba3ca 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new 94bf7f230c 74: onsuccess: #590: 1: Success after binutils: 16 commits new 699a5075a2 75: onsuccess: #591: 1: Success after gcc: 25 commits new ccca523b0e 76: onsuccess: #592: 1: Success after linux: 63 commits new 6f851cae6d 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 14ece39e3c 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 1df688e429 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new a094f75d07 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new d2594728e5 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 043441799b 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new c752ee836d 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 6f10155cc5 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new bd5a19cdbb 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 5222602635 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new a88f5e0e9c 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 721386a1d2 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new e53c18171a 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 9554afae19 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 66286a7bee 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new a9ba5cab89 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 719291c3a7 93: onsuccess: #613: 1: Success after binutils: 19 commits new 367da88d0b 94: onsuccess: #616: 1: Success after binutils: 2 commits new 9affa4bd01 95: onsuccess: #619: 1: Success after binutils: 5 commits new 493ddf29dc 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new b9cf242b81 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 09fe9d74bc 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new c676ef1672 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new 293d7eebad 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new f11b04fc5d 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new fc3646f29f 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new ecf0a40ff2 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new fce2f0a86b 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 17b865ba83 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 9cab87b8e5 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 6e4d616430 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 3a6e515d88 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 3164323db9 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new 805ed92e0f 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new e0c19078b7 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new a04685e8ef 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 07eb6e009a 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new ba55ef9e95 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new bc4599291b 115: onsuccess: #645: 1: Success after binutils: 27 commits new 0332591b2e 116: onsuccess: #647: 1: Success after linux: 3 commits new 63d3e32a21 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 4fe8dc98d6 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new ad857bdfc2 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 6e1d68f128 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 3bbd12dd48 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new a8e8e38699 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 0f59ca65df 123: onsuccess: #655: 1: Success after binutils: 22 commits new 31c95002ee 124: onsuccess: #657: 1: Success after glibc: 2 commits new 52ee116423 125: onsuccess: #658: 1: Success after linux: 3224 commits new 03787139a3 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 1f9251c1f8 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new fe3d6b1300 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new dcb4f27ec4 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 0afe12d258 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 095a208f16 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new cb7b16bd18 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 043f02e238 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 7f2ecc8a35 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new b33edeaa1a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 8fccfebd14 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new ed5692733b 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new c2f7547bee 138: onsuccess: #671: 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 (9deb4efad1) \ 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 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 40412 -> 40336 bytes 04-build_abe-gcc/console.log.xz | Bin 214772 -> 214928 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8316 bytes 07-build_abe-glibc/console.log.xz | Bin 245320 -> 245180 bytes 08-build_abe-gdb/console.log.xz | Bin 39672 -> 39476 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2432 -> 2068 bytes 11-check_regression/console.log.xz | Bin 5432 -> 5400 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 | 32 +-- sumfiles/binutils.log.xz | Bin 63300 -> 63252 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83960 -> 83952 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122432 -> 122432 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 402 insertions(+), 402 deletions(-)