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 8a868996a2 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 48000fff39 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards b18050e28e 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 944082d039 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards d6481d1aed 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 22845bf622 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards dfb8bd24f1 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 73c68ca10c 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards f3dff46b19 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 91cef9cb38 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards f347b942b3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 2c71c4c32f 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 5e8c010161 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards fe4e97d1d6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 8f72b0b1f6 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards d64a488118 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 88bb9909e1 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards de7fd3c03c 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 60e5a7df27 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards ab4aa4d416 212: force: #24: 1: Success after binutils: 2 commits discards def10a83fa 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 2737c4ab60 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 83a14c2c6b 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 470463d589 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards f28386bb94 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards a882545888 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1b5bfde78f 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 0205eb3a9c 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 7b0b0e2704 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards a000eb015f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards cbc5c60039 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards e1e1352322 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 13a2b4c16e 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 281847a24a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7635033097 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a2c9b469d8 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards d043479864 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 6031607c19 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 42be39a80a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards dff6976434 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 377869f210 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards fc188178d6 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] discards a4ad71f491 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] discards c8fcca39be 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] discards 1718869d74 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] discards 370d8ade33 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] discards a2360cbaef 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] discards 830b0393af 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] discards 2c98fcb45b 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits discards 49d4b63a24 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] discards 9e5c765b6a 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] discards 02c2085ef5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] discards 80926727f9 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] discards e3ace85615 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] discards 2a1195d322 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] discards 19d4e66499 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] discards 96d0aba18b 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] discards cb9a410c15 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] discards 48bd514c15 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] discards 9149031835 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] discards 8bbe5ce923 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] discards 798c63936b 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] discards 84e5c9b6eb 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] discards bf0428a6ae 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] discards f76f54ae2e 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] discards 6bf1947053 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] discards 1a108154e2 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] discards ea23ff756d 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] discards ee7d4db11c 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] discards d6fdfe22fd 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] discards ba993358d7 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] discards 3a7fe8b91b 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 7e89b871f1 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] discards b06ab93d28 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 99a1c7fa6b 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] discards b82df59a82 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] discards fb94f69f9a 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] discards 491b8fec95 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] discards ea438cf888 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] discards 243d677a10 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] discards 3ba523c86f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] discards 52beface80 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] discards ed5f7251be 149: onsuccess: #684: 1: Success after linux: 10 commits discards 6bcc9cf6b6 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 6e508dea88 147: onsuccess: #681: 1: Success after gcc: 6 commits discards c370462dd1 146: onsuccess: #680: 1: Success after binutils: 20 commits discards b858e6981c 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] discards d2ec0ca702 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] discards 1faf22d051 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] discards a128f5b52a 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards eec9717dba 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits discards 1a18bb7221 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits discards 046133f22d 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits discards 936ceff840 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] discards 934d0df149 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits discards e968d26310 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 3c9a46e5d6 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 91b5d9adcb 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] discards c2b399a03b 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] discards 153b7babaa 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 29c4e986bd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new fbd2ce5492 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new 57895c8d55 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 2c83f38c59 133: onsuccess: #666: 1: Success after binutils/gcc/linux/gl [...] new 17deff212c 134: onsuccess: #667: 1: Success after binutils/gcc/linux/gl [...] new da6e477b8a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new a939fbd9e8 136: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new aa9eb063fb 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 commits new 7632b3909c 138: onsuccess: #671: 1: Success after binutils/gcc/linux/gd [...] new 24904764cf 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 commits new 3cdf043a81 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 commits new 44e8fbc74a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 commits new d9c097da68 142: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 2d9c776f53 143: onsuccess: #676: 1: Success after binutils/gcc/linux/gd [...] new e5eebc0a31 144: onsuccess: #677: 1: Success after binutils/gcc/linux/gd [...] new 6ad85cc2c6 145: onsuccess: #678: 1: Success after binutils/gcc/linux/gd [...] new 89e8cef1ed 146: onsuccess: #680: 1: Success after binutils: 20 commits new e854891c7f 147: onsuccess: #681: 1: Success after gcc: 6 commits new 4d4d73b8e0 148: onsuccess: #683: 1: Success after glibc: 9 commits new 91407f18df 149: onsuccess: #684: 1: Success after linux: 10 commits new cf017ec051 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/gd [...] new fea6961227 151: onsuccess: #686: 1: Success after binutils/gcc/linux/gl [...] new 317c20cf30 152: onsuccess: #687: 1: Success after binutils/gcc/linux/gl [...] new 383aa51570 153: onsuccess: #688: 1: Success after binutils/gcc/linux/gl [...] new 7dee843536 154: onsuccess: #689: 1: Success after binutils/gcc/linux/gd [...] new a664026ff8 155: onsuccess: #690: 1: Success after binutils/gcc/linux/gd [...] new 0751169318 156: onsuccess: #691: 1: Success after binutils/gcc/linux/gl [...] new 087f751e14 157: onsuccess: #692: 1: Success after binutils/gcc/linux/gl [...] new 8d3820289a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 36f2e8df81 159: onsuccess: #694: 1: Success after binutils/gcc/linux/gd [...] new 6bcaea35ea 160: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new d0a054b78e 161: onsuccess: #696: 1: Success after binutils/gcc/linux/gl [...] new 272f642f7b 162: onsuccess: #697: 1: Success after binutils/gcc/linux/gd [...] new 3fd322a3fc 163: onsuccess: #698: 1: Success after binutils/gcc/linux/gd [...] new b40b8fd4b2 164: onsuccess: #699: 1: Success after binutils/gcc/linux/gd [...] new b11544051e 165: onsuccess: #700: 1: Success after binutils/gcc/linux/gl [...] new 16147767f2 166: onsuccess: #701: 1: Success after binutils/gcc/linux/gl [...] new 47f0460e29 167: onsuccess: #702: 1: Success after binutils/gcc/linux/gd [...] new c7a1f9f0a0 168: onsuccess: #703: 1: Success after binutils/gcc/linux/gl [...] new af9f89e474 169: onsuccess: #704: 1: Success after binutils/gcc/linux/gd [...] new 4eb13f7e07 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/gd [...] new 92f597c528 171: onsuccess: #706: 1: Success after binutils/gcc/linux/gl [...] new f273d54749 172: onsuccess: #707: 1: Success after binutils/gcc/linux/gl [...] new 9b51db374f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/gl [...] new 38d2c8667b 174: onsuccess: #709: 1: Success after binutils/gcc/linux/gl [...] new a26075dc13 175: onsuccess: #710: 1: Success after binutils/gcc/linux/gl [...] new 5ec36623a9 176: onsuccess: #711: 1: Success after binutils/gcc/linux/gl [...] new 2e329eb72e 177: onsuccess: #712: 1: Success after binutils/gcc/linux/gl [...] new c98d36a617 178: onsuccess: #714: 1: Success after binutils/gcc/linux/gl [...] new 49647ce65c 179: onsuccess: #715: 1: Success after binutils/gcc/linux/gd [...] new fc7f0dffe5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/gl [...] new 993d945a23 181: onsuccess: #717: 1: Success after binutils/gcc/linux/gl [...] new e74f31ce2c 182: onsuccess: #718: 1: Success after binutils/gcc/linux/gl [...] new 7b9edf406f 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 commits new f375e0b0e1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/gl [...] new ce055d8f49 185: onsuccess: #721: 1: Success after binutils/gcc/linux/gl [...] new 685a173ad0 186: onsuccess: #722: 1: Success after binutils/gcc/linux/gd [...] new 15b22ec634 187: onsuccess: #723: 1: Success after binutils/gcc/linux/gl [...] new 79b6b33a8a 188: onsuccess: #724: 1: Success after binutils/gcc/linux/gl [...] new 7aba52637f 189: onsuccess: #725: 1: Success after binutils/gcc/linux/gl [...] new 26902e0746 190: onsuccess: #726: 1: Success after binutils/gcc/linux/gl [...] new 89cf8e672c 191: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 48eefc9c80 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 8d80baccaf 193: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new bf7808cb65 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 45b4af674c 195: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 284b0b26fd 196: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 5e21617ade 197: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 2c3fa75e06 198: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 51c58b8e04 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 0c75958f3e 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 89d23716d5 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 4312b45e56 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 2d394bfd68 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 698013a82b 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1c6f2d1496 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new ef37601577 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 4f47ad4c23 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 129562fc96 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new e9db85c4ef 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new cb841e121c 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 6312b5dcdc 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 2bc7c1237d 212: force: #24: 1: Success after binutils: 2 commits new ab9e227950 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 7a8c2e2464 214: onsuccess: #26: 1: Success after binutils: 12 commits new 7fc16d78ff 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 224274807b 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new f27cbb33d9 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 9aa4561a21 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new a11009ea04 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 9199e09867 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 5b40feedb1 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3e45689b8b 222: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 71ea05475a 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new acb703ad6a 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 1d53dfe55f 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4267a51399 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8b78c70a00 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new cd2849acd4 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 2da0ae8bb8 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new deabb4025a 230: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 2a93ec6bd3 231: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 52eaabd464 232: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...]
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 (8a868996a2) \ 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 2056 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35192 -> 34948 bytes 04-build_abe-gcc/console.log.xz | Bin 203488 -> 203800 bytes 06-build_abe-linux/console.log.xz | Bin 9468 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 241216 -> 240692 bytes 08-build_abe-gdb/console.log.xz | Bin 34908 -> 34720 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3828 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2404 -> 2164 bytes 11-check_regression/console.log.xz | Bin 5124 -> 4880 bytes 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 66 ++++++++++++++--------------- 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/changes-list-long.txt | 56 ++++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++--------- manifest.sh | 38 ++++++++--------- sumfiles/binutils.log.xz | Bin 62992 -> 63136 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150688 -> 150776 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122608 -> 122660 bytes sumfiles/ld.sum | 4 +- 28 files changed, 111 insertions(+), 115 deletions(-)