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 f04a1b2242b 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 209a736c382 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 9016603c17a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards f80a0a0eb48 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a5370248c64 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 59e3dd0eee1 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards b323b635bae 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a92d0474ec5 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4401043f144 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 2e9def60a69 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 736b5e11289 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f527aa9bd37 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 1ecf64dc557 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9d6abc13914 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 5d510f55c45 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 0a1dbb64ffa 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards b72675f69e0 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2e0a44ea326 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 4cac053f674 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 209c967fb3c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 8d53324202c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 93478f4cbf0 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 09d1e8850ab 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards b67a6c62d58 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 603d022fb35 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 7c455328ead 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 446cb4a9170 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 26bd381e44e 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 47b836e454f 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards a93c0412159 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards d67eb53d48c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards e7e53121eac 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 0f628e37c07 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards 13a45721489 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 5c75cd2833e 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards c518ebc32ad 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards a9af9a10957 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards f282cb92073 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards e46d2397497 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards d9935f4f281 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 4be6e223384 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards f937d41f4b4 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards e4a3ba4e07b 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards e3c5804b85a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards a2f61fdc9f1 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 091a565963b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 8122cd047c2 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 3b65f03dfcc 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards d8c06223758 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 49047d8d493 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 6a6887cbcab 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards da2f9b1c8e4 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 7f5301d1e21 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 678f154f8b5 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards a9e17486551 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards ac9401aedd3 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 4996308895a 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 321753a6bbb 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 851f0654447 149: onsuccess: #684: 1: Success after linux: 10 commits discards 1882cd84ac9 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 08be507fbdb 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 3b8e5119221 146: onsuccess: #680: 1: Success after binutils: 20 commits discards b7e270d1465 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards ad6a89d50b5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards b5e6fb24ac5 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 480c757b765 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards e7ed53c0631 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards a70a7e5b8d3 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 3a19bf86822 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 9efda7da527 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 87600297d66 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 483d7290a3a 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 3f5a39f67e6 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 0c336812b6c 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 9048c328eac 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards b59e74b0e82 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards a6683d53d90 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 4634992d4e2 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards ee57d58b333 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards edfe3b2f1f5 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 3bb527dabac 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b0c449207cf 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 633bfb81836 125: onsuccess: #658: 1: Success after linux: 3224 commits discards b2607178f52 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 23b5fd0f983 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 935a0db1e30 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 043af4275a8 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ffeec69d8be 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards fa3d518873c 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 6999375d9b9 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards f3d1bd78689 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards b44eea2d65b 116: onsuccess: #647: 1: Success after linux: 3 commits discards bd5b82ed3af 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 30680226388 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 1a3e156f37b 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards c1112999e83 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 308cdc0ab0e 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 78b1a31fa6e 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 90113ed583f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 853c65f9952 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards d35d011d546 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 1fbe5d54d53 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 611291b48fa 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 466d8568f7f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new f3397a3e92c 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 5196f25fb6e 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new e4b3fff9dd3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 1f802382b9d 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new f8213ca93ba 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 1f8ed6e118e 115: onsuccess: #645: 1: Success after binutils: 27 commits new 3f7da9ab580 116: onsuccess: #647: 1: Success after linux: 3 commits new ebed2cd09e9 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new c0149f08cc5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new f122715a048 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 915fe4f72fd 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 534d58b2829 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 2a6361ae108 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 0b856a42089 123: onsuccess: #655: 1: Success after binutils: 22 commits new d406054d25a 124: onsuccess: #657: 1: Success after glibc: 2 commits new 5e442368f22 125: onsuccess: #658: 1: Success after linux: 3224 commits new 87a4e32c8bb 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 4d2747d656c 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 564ecb14ff2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new aee043a0ead 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 6a88c997040 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 215459c3fac 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new e9bbea3e8ae 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 306fd965e0c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c52b3a6c4b4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 5c3be21610b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new bf9e1902806 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 36e92d04807 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 01c3cfb30dc 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new d773774fecb 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 1728e496188 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new a79f4dc52c2 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new d3d4456a55f 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 7d18a7f0867 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ae09a89492d 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 79f5215ca41 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 1aeaac5dc9f 146: onsuccess: #680: 1: Success after binutils: 20 commits new 7fbb7b30d56 147: onsuccess: #681: 1: Success after gcc: 6 commits new d4d75c87286 148: onsuccess: #683: 1: Success after glibc: 9 commits new b73da87c597 149: onsuccess: #684: 1: Success after linux: 10 commits new 2857f233865 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 9d823c85f45 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 90b41997756 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 690c018d936 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new f0759c04b97 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new e765053fcb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 27cc924c5dd 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 0129cc459a5 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new da5654e0d54 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 6391bd774c6 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new a65f7a4fb15 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 50948fec34c 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new b5eb9462576 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 2c6f58d6c03 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 8860f6f514a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 210d8210db8 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new c1affd1e835 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new ad7680a1195 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new b8c4bc60599 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new c2e16d523c2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 4f05d041770 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 15b52ae4275 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new da711585b79 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 6fbcc76badc 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new fa5da74a72f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 547aec28713 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 126f8ac15c7 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 0cd69df1f39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 4ffbf9f1777 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 7d67a5359ac 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new ddb7ad522cd 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new e0725da3d64 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 82c9bc5d6e5 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new fd8642737d6 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 24eebbebc2c 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 83f6f5d4409 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 1ea67267f96 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 5c463acfdfb 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 5826ad2e9d5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 019277b6298 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 5b86e20aff8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 9e7486edf59 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new fc9ec55fd3c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 4c3e086f16d 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 0160ef2eab5 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 91e61b543af 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f185faae621 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a5d20ff98c9 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 4100b880516 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0982cca8d2f 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 6b262eada56 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 35ff8571f00 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 575bd77bd8e 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new f9a376b341e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 994d58cb560 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7db776d2096 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 52174616fa4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 52a98099d8c 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new e10f8ff1868 208: onsuccess: #18: 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 (f04a1b2242b) \ 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 1756 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 38760 -> 38660 bytes 04-build_abe-gcc/console.log.xz | Bin 203688 -> 203552 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8228 bytes 07-build_abe-glibc/console.log.xz | Bin 244508 -> 244156 bytes 08-build_abe-gdb/console.log.xz | Bin 38460 -> 38348 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3768 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2036 -> 2028 bytes 11-check_regression/console.log.xz | Bin 5852 -> 5880 bytes 11-check_regression/results.compare2 | 4 +-- 12-update_baseline/console.log | 44 ++++++++++++++--------------- 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 | 36 +++++++++++------------ sumfiles/binutils.log.xz | Bin 63032 -> 62776 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83964 -> 83940 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122248 -> 122244 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 56 insertions(+), 56 deletions(-)