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 7511fcafcb 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 2cb949ac40 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 8ca0eed5ba 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 7b5a798f21 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards 2fefbfdd02 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 59ae46fa50 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards b121c22bd0 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards b5cd28c2a4 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 64c3f16f7e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 3f14b0556a 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 11335d6cf7 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards d84f60da3e 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards 4c885c611d 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 7dc708d799 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 370d6cc05a 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards 2bcb633774 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards cdd2ef8b2a 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards a468984311 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 19421c3e33 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 8818e5f450 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 9bc717445a 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 969b4a52c8 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 5ebbcce9d4 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards b74a46fe2e 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 9bc81d371e 124: onsuccess: #657: 1: Success after glibc: 2 commits discards dc3a4ba053 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 84ed399237 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 11863243fc 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 985f5afbca 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 5e3c95a932 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards af2d71e1f8 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 8c1f7152a0 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards d79b46df70 116: onsuccess: #647: 1: Success after linux: 3 commits discards 08eca66200 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 1736656da1 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 6eb45fe7ef 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards f2559f12b9 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards ce55053d15 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards c5f2178f82 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards e8388a622b 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards 31eccf61bc 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 5aa7a01543 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards cc711c6cec 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 720d79cea9 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards aa49d1a5ac 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 2996fea12a 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards 5bed7d88ca 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 318f7604f1 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards e73b2c20dc 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards 7f2b306ccf 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 23608160be 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 7a22b63ad2 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards e82cd56b62 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 11a057c99b 95: onsuccess: #619: 1: Success after binutils: 5 commits discards c6e12e76dc 94: onsuccess: #616: 1: Success after binutils: 2 commits discards ddb68d4dbd 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 6ff92c0199 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards d136de67a7 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards 9c505bb132 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards aaed99857d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 0af16a71ef 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards 68dae38554 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards 8cba9b60cf 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 150ea84d21 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 6c4377a6be 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 14b6c3c3ed 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 5b017755b2 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards b14ee641fa 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 68ffb98291 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards ff1e49cb2e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards 6872fc40e2 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards adace39a47 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards aefee677b8 76: onsuccess: #592: 1: Success after linux: 63 commits discards 1da32a27bf 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 5942062597 74: onsuccess: #590: 1: Success after binutils: 16 commits discards e40b8070a3 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards 2190d02429 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards 4d810b0975 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 488ffbd38f 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards afb46ec876 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards 76a7e3dbb3 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards cdc8e3dcd0 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 970909764e 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards c4ca303352 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 359cc8f564 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 27a6a86cd2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards f64d84a9a0 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 7f021669fd 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 1bf8390ef0 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 4112ca3b30 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards dbde31beb8 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards e70c3da73b 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 16fab75f6d 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 17f3847a39 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards 0950c77a7d 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards 3845bff3a4 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards a27baf4498 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards 7dceb31606 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards e6e2a56301 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards 1113d5c2a5 49: onsuccess: #562: 1: Success after binutils: 9 commits discards f218414ecf 48: onsuccess: #559: 1: Success after binutils: 6 commits new dea5212486 48: onsuccess: #559: 1: Success after binutils: 6 commits new f2f9a32438 49: onsuccess: #562: 1: Success after binutils: 9 commits new d12a4b34fc 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new 82ff3c7c79 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 29445af624 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new bda206a040 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 3951e07ae2 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new 651dd347b3 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 8b4b9fd9b9 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new ed51ba3735 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new 61da56fe21 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 6675d63655 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new 70c51aeb9a 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 15d8369590 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 90a8d8547f 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new a921425aca 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 4d031ada17 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new 10b5430342 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 49787ac233 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 1b15149740 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 58a28be3fb 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 1b16c4a7b9 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new f2a2d70029 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 427943c82f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new f43a13125b 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new c6cfdb8568 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new c59e93ba87 74: onsuccess: #590: 1: Success after binutils: 16 commits new 21e7c1e04e 75: onsuccess: #591: 1: Success after gcc: 25 commits new 1ff3901591 76: onsuccess: #592: 1: Success after linux: 63 commits new e10a689312 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new e381e90f3b 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 08d847b40e 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 1e33408cb1 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 656b35d998 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 98b6317ef0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new eb95da2b63 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 35a94324d0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new cce2c2b32f 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 3baeefa3e7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 4119b4faf6 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 86fb5c78af 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new f92111fc71 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 0eff5e3409 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new 4f2ebe1be2 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new 4e5234ea41 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new 28cfb0c4c9 93: onsuccess: #613: 1: Success after binutils: 19 commits new 275e87e503 94: onsuccess: #616: 1: Success after binutils: 2 commits new f8cf6ce7cb 95: onsuccess: #619: 1: Success after binutils: 5 commits new ba9a3e8237 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 32fa88338f 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 723ce5f84b 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new ca4f56cf60 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new c9d840be87 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new 30e7645e98 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new a7b2174a15 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 6e63afe1f0 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 98ad6fb2c4 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new adcd0543cb 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new f9439deb26 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 6dc0a56ebd 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new f20e33f173 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new e612a54c64 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new ca520f765e 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new a1c22ceef2 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new a84d611504 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 3d1dd73832 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 418dbf47b7 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 9c62034470 115: onsuccess: #645: 1: Success after binutils: 27 commits new 965e599d85 116: onsuccess: #647: 1: Success after linux: 3 commits new 77386678ef 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 20d79c8247 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new a29309395c 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 943d7865b1 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new c8c2eec6e2 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 0951b0ceea 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new d773a6f889 123: onsuccess: #655: 1: Success after binutils: 22 commits new 93eef8075c 124: onsuccess: #657: 1: Success after glibc: 2 commits new 660d8cd3f5 125: onsuccess: #658: 1: Success after linux: 3224 commits new 5890482986 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 921d220da7 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new a2b0df4dce 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new bea5aba815 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 8e6b7fa9ff 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 9e605b4eac 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 73adfdd010 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new ac087c2575 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new ef9447a9fe 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new 30864f7b66 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new e4a4e49e08 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new ce4a1ffc40 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 2494e2e71c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 67e3fc7c7f 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new ae942da606 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new ef9a745953 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new 9f2096a760 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new dfa9a1868e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new 75e23eee8d 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new df5f4fb8d8 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 9c7cfff0a6 146: onsuccess: #680: 1: Success after binutils: 20 commits new 07d6e89092 147: onsuccess: #681: 1: Success after gcc: 6 commits new c9cc9a823e 148: onsuccess: #683: 1: Success after glibc: 9 commits new 7c7b237566 149: onsuccess: #684: 1: Success after linux: 10 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 (7511fcafcb) \ 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 1712 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39824 -> 40684 bytes 04-build_abe-gcc/console.log.xz | Bin 214236 -> 217104 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8852 bytes 07-build_abe-glibc/console.log.xz | Bin 245132 -> 244588 bytes 08-build_abe-gdb/console.log.xz | Bin 40092 -> 40152 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2264 -> 2192 bytes 11-check_regression/console.log.xz | Bin 4700 -> 4844 bytes 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 64 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++---- sumfiles/binutils.log.xz | Bin 63052 -> 63096 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83852 -> 83880 bytes sumfiles/gas.sum | 2 +- sumfiles/ld.log.xz | Bin 122188 -> 122168 bytes sumfiles/ld.sum | 2 +- 24 files changed, 50 insertions(+), 50 deletions(-)