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 c3479ea69927 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 5b2ff4abe190 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 96de7517a9fc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards f9f4df06261c 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards fc11a232d4b1 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 9b10e501c6af 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 051bedb094dc 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 739079da9ec3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 3d0a625571a3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 5625bd16f505 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards c006043b0ce6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 157498951aac 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 92ac6507ce77 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 0dfec8bc5903 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards a34ca75ac229 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 01143c900a51 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 3a88d06044c6 212: force: #24: 1: Success after binutils: 2 commits discards a9b70b3c0cd3 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 476607b3d615 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 762d86c5a82e 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 7bf34a79f9b1 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 28533e842f30 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards cd73ca51f2b4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 009732f7e383 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 971d855cfd07 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards e4f2ca958626 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards daa6c37b4353 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ba2a9a9d97d7 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 549a1095c64c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 1a4913ab3910 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 0af1a99f6352 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 6f46f329ae4f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 6a67e5d7348d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 879f3e162567 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards cfdb55372c1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 8afba0af14e0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards f6417a8b0135 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 663c8cbca821 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards c394e3bfb62b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards 0600e5be600c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards f4c9971cb576 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards aaf251232397 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards 1ea629ca6d29 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards 52eae46336a1 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards fad378af9df1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 547bd354453e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 28bdf678160e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards b07d06e62d2f 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 7faec62ead26 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 24b150b2a5fe 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards d07fca7149a1 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards 335374cd94b6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards 5167ff319e78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards 7bea3839f387 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards f94e1d68dd2d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards f7866ccb9e54 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards 7eccc0c8db24 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards 07d8ca2dde96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards 4ae57ee91f52 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 1b8337d77bb2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 6d553a239c5c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards 57b5143a2818 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards a5490fa8f20d 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards 280517072a81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards cb74982baf15 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards e1490f6f2bdd 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards f91a0ae498d3 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards c4165a5df61a 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 8649ef5391df 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 8dd67d3436fa 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 5c8cc60279c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards ec05e3fcea36 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 75b181b2845e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards 27a979e37bb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards c555f331c482 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards 8cfa0a7a3dcf 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards dab667874fef 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards 5e2fc803e7c2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards a6d73c187d74 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards f108bda37dd8 149: onsuccess: #684: 1: Success after linux: 10 commits discards 80de2316a9ee 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 52ff11b1c6f8 147: onsuccess: #681: 1: Success after gcc: 6 commits discards c7dbf5f344e7 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 5a727817fb4a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards 83da85c8ca87 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards e89b63bf92d4 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 46146bd99358 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 1077a84494b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards 5e777a8f04d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards ec1856e1cb5e 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards 790ba1f66a49 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 59581f825063 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards ed50c619c728 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 1fa9517392d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards b5857c44b63b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards dffc92e3742e 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 689c28f217b2 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards cc47ff57d7cd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 2854a5b47fa3 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 9d3dfab39fc7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 5cd0b3d954af 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new f13d0080c704 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 846351a1fd65 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 8f358b185dd4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new b008ada3194a 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 31d20fe9930d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new c88976e18105 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new b86a92acf2ad 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new b04f80cf0c42 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new de692f72b262 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 7e54febbcb64 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new 5c6084d88410 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new b58e52972431 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new 46f4fba8b435 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 95bba4743fee 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new 702e0e596edb 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 9185e9ef25a1 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new a6aef6cad6f6 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new cf8cda970e8c 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new 4730eab9c57f 146: onsuccess: #680: 1: Success after binutils: 20 commits new df2a9d50c8a9 147: onsuccess: #681: 1: Success after gcc: 6 commits new 3e0e92a57870 148: onsuccess: #683: 1: Success after glibc: 9 commits new 0d3cd0ee3b85 149: onsuccess: #684: 1: Success after linux: 10 commits new 4d2ddd438307 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new c0b886386ed5 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new 7847cb0f968d 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new 29ad57c95e6d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new aacf1e3445b0 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new fe36e96cb8af 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 05eb218d30f2 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new 116bd3157a8f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new 168a97ea306e 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 77a7b23289f0 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 63e14627e8a0 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new e4fc9c235adf 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new 389239239fb6 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new d81cf55f563b 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new 48dcd4009d75 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 7e2edb5c8044 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new e2d5d19b0aa6 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new 2cd5f0d91919 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new a3f3a9028005 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 74f9e2785237 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new aa39407ef183 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 59a63452dc25 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 628e8f64ad10 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new a4897a41ff2f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new bde7f53796e3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new f718a02b654d 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new 3c045ebf5d39 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 499f6f243709 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new b69474c793f2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 159aca40adc8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 5a11bbbc3d16 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new 67f35e072af5 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 04170f39798d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 8c57bfedb42c 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new bf64d1ce9bc6 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new c1c0d5642f17 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new 0d917a62745b 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new dfd33479463e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new 5a6fcb805b3b 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new ba86421a4596 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new f753faca5c5c 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 17ead7b98077 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 845c624d1b6a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 98c781a0c2be 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 93d1b1a49317 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 765a43e93adc 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new fd5cf3b01eb2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 4059f7fba120 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 58e5a338b37a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new efe51bcb9dcd 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 4ba2dc96c398 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new c645a4090aa5 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 923bd488c80f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 09826850b641 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new a48b788cd3ab 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 86ff93eab152 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 67937e41d005 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new b45711124f37 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 3462e35b8a58 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 91f17edd6d49 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 296a1f94dd84 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new eb2545b6cb56 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 4d7db6fd029d 212: force: #24: 1: Success after binutils: 2 commits new 9395fe56d4d3 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 3e23c69b5712 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0fb55f8adc73 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 2381c30c9b54 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 1b21953ebb54 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 250b8fa5a311 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 264334cea8f3 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 1499b0c92538 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 8df151b5b5f9 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new f3dfafcc7b03 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 97937c2b9569 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 7cb21fc94d6b 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new dba4a56e4e98 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new b5ddab437cb9 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 8d5e03471eeb 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new a45d3e98fe46 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 8c458f29baa1 229: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...]
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 (c3479ea69927) \ 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 2036 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 34864 -> 35512 bytes 04-build_abe-gcc/console.log.xz | Bin 203492 -> 203356 bytes 06-build_abe-linux/console.log.xz | Bin 8168 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 241320 -> 242028 bytes 08-build_abe-gdb/console.log.xz | Bin 34508 -> 35304 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3800 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2100 -> 2784 bytes 11-check_regression/console.log.xz | Bin 4952 -> 5084 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 4 +- 12-update_baseline/console.log | 68 ++++++++++++++--------------- 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 | 59 ++++++++++++------------- mail/last_good.sh | 36 +++++++-------- manifest.sh | 38 ++++++++-------- sumfiles/binutils.log.xz | Bin 62980 -> 62668 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150792 -> 150780 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122660 -> 122616 bytes sumfiles/ld.sum | 4 +- 28 files changed, 115 insertions(+), 116 deletions(-)