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 8d9ae47cae 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 8f33200114 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 682bdbc084 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 17cd5ddcbc 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards e3c897f5a0 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 1f43b2ec89 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 0d1235f86e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 154e8b788f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 52a6a2f43b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards cd7eba8bd4 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards ef4df572f6 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 5cfdca7e0d 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 413eb1e68c 124: onsuccess: #657: 1: Success after glibc: 2 commits discards c5b5ed639b 123: onsuccess: #655: 1: Success after binutils: 22 commits discards c34fd91250 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 6158df72f7 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 195731f74d 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 62e81aa999 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 58a44b5743 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 563b895c4c 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 1f2af69ba9 116: onsuccess: #647: 1: Success after linux: 3 commits discards a5fbd63a1a 115: onsuccess: #645: 1: Success after binutils: 27 commits discards a3662a259b 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards aa32dc3b00 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards ed185c76c1 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 81b46d208f 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards 650740c37a 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards 6385c21d04 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards efd8762615 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 2a371c291c 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards 77abe96bde 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 6a9bbe52f5 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards 68b56dde5d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 2108af3784 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards fe55abc9b7 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards e81c8a8d43 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards e49d10d212 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 1fcd54900d 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 7cc2abaade 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 53595245de 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards ca91a44faf 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 7696cc6882 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 2329f412e5 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 592b20fb55 93: onsuccess: #613: 1: Success after binutils: 19 commits discards e7953cb441 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards d52c81d9d2 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 03b2bb2d3a 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards f7681f99e5 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 23de990663 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 128b4192de 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 547f8b6d9d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 96b742e544 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards d04ac08571 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 85d15b46fe 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards c167d09c63 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards 3844f71c91 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 926ec60fc2 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards 90dd9ca551 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards fc7b4a4840 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 1ea33216bb 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards a698691518 76: onsuccess: #592: 1: Success after linux: 63 commits discards fe9a93c3a0 75: onsuccess: #591: 1: Success after gcc: 25 commits discards a1fe79a464 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 71c595df44 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 7058374be4 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 190d03f97f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 15f6cf42f5 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards fc1a5b0990 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards dff8e32d0f 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards 90c7a46ef4 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 35a1b0d5cc 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards f11cbb8c05 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards ec367dba46 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 1cbe240e9b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 9a2cfd0c9c 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 4819f2cd97 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 98b49b1986 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards b21c6c6ad8 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards 3e7fb19e13 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards 0e2e22ca9a 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 6541789a25 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 28d7e49ebb 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 4a5a75840a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 4f7b2b4dca 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 0b9775c7f6 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 07cc27cd50 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards fddf3464a9 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 50fe525993 49: onsuccess: #562: 1: Success after binutils: 9 commits discards b7e3411aeb 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 4cb4d139b0 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 0c3b2ba99d 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 5f97d42d99 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards 866a3602de 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 09f6e2d656 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 3f2ed08596 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 400f2f861b 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 5927ee3b42 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 81d6817ebc 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards d6e36f5302 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 7fc8101444 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 8601bd2def 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 9e55d4399c 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 7ffadd827a 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new 084b870875 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e3492257b2 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new 0f677e3fe7 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 505060969e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 2f02594b84 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new ce36a5ae9c 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new d02e261a46 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 0f78e1bfce 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 1921b6b06e 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new 59d529825e 47: onsuccess: #556: 1: Success after binutils: 12 commits new 67d4a50fb5 48: onsuccess: #559: 1: Success after binutils: 6 commits new caac32843d 49: onsuccess: #562: 1: Success after binutils: 9 commits new ff68ef2003 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 78fc5f2967 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 1fc92bd9e4 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new 5937517002 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 02e414a92f 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new b0990e2b16 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 89cddb85d7 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new e3ca238c4d 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 313223e15b 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 36268041dc 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 3bf0285e47 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 6bd8a030b9 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new fbf796f977 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 000ddfcafe 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new ca57995b2f 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 30cb4980fb 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new cbe388af4b 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 01520a48c9 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new d90b031620 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new b275f24175 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new 512b513f33 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 7f1a144f3c 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 8dbb4c0ee6 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 56f0617cbc 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new bc505d035f 74: onsuccess: #590: 1: Success after binutils: 16 commits new 054e509168 75: onsuccess: #591: 1: Success after gcc: 25 commits new 1e889424ef 76: onsuccess: #592: 1: Success after linux: 63 commits new 4154ed50da 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 9b549465da 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 8cdfe4855c 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 5280bc8fd1 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 4973af3048 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 069903b6c0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new 8c10a36af7 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new c7924e2987 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new dc0875e14a 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new b560c0c141 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new d72240a2eb 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new d25cb172f2 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new c2bc6ede92 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new b297f07352 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 44a32b80af 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 0d6ce8cf13 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new dc0feccd7c 93: onsuccess: #613: 1: Success after binutils: 19 commits new 3b5d75e10f 94: onsuccess: #616: 1: Success after binutils: 2 commits new 46914b40a5 95: onsuccess: #619: 1: Success after binutils: 5 commits new 7976e3e606 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new c87068a598 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 288dfbc529 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new a3a240346b 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new cf32cd2414 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 909dec2259 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new 244124d045 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 251bde6693 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new aad75c6437 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new 63af4a87cf 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 6de7f8ec4d 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new b8d5710462 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new 1dff22dc89 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new 65d147d274 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new f57e1d41f0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 22e1d89c78 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 666e6bc02b 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 5a3c993bb2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 9c13fba1f8 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 2071d79275 115: onsuccess: #645: 1: Success after binutils: 27 commits new 3683ecb4ec 116: onsuccess: #647: 1: Success after linux: 3 commits new 65f49b34d8 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 454572f218 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 5acff57975 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 2dfc7715c6 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 6d4b001424 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 597a490f42 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 4e18886145 123: onsuccess: #655: 1: Success after binutils: 22 commits new c600faaaa4 124: onsuccess: #657: 1: Success after glibc: 2 commits new 62953eeb3d 125: onsuccess: #658: 1: Success after linux: 3224 commits new e3d17fb640 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 67710ce1ac 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 76f46abded 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 04b25d442f 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 39c39d7cfc 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new ffd9a2b057 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 3b7bb100da 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 8ff84b6f35 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new ce6cf8501f 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 6715519179 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 9e56407166 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 9deb4efad1 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits
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 (8d9ae47cae) \ 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 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40228 -> 40412 bytes 04-build_abe-gcc/console.log.xz | Bin 216552 -> 214772 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 245092 -> 245320 bytes 08-build_abe-gdb/console.log.xz | Bin 39568 -> 39672 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3880 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2316 -> 2432 bytes 11-check_regression/console.log.xz | Bin 5780 -> 5432 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +-- sumfiles/binutils.log.xz | Bin 62956 -> 63300 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83900 -> 83960 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122380 -> 122432 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 28 files changed, 400 insertions(+), 400 deletions(-)