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 a1903b9b4a83 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 47416f335950 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards a3fc1c47e4b2 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 706b4a87883e 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards b82bdb210711 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 6c1726e7ba8d 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 3152c5e6e3f3 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 5abfc670c809 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards e2a1f8c46f2c 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 711afa31ecfb 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 75db6854d5c3 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 73bad9b0f7ce 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 16969cb602c4 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 00d32adce0ff 212: force: #24: 1: Success after binutils: 2 commits discards c0788a3cb544 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards e77e8ab5fcd5 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 39a8d88cd51c 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards afca99c3285d 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 47b7f199518f 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 52c740f52c2b 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards b1252b02fd22 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 6e89a52d4f8d 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 0f9b3a76f061 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards f3d9b373ed25 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 0d850165d63f 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards cf2cc9d5ec9c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 7fed33629d7b 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards c6125acace68 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 96d587f1f674 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 0bc050e3d0e3 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 7dae5ea7dc35 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 4b60307afc5c 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 6f626b772baa 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 021316163d93 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards fba9ad56082c 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 0a47a64ef5e8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards f2e2b8eab67c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards bffe5ab40d18 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards db0fb1d468cb 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards 91ab5c3e4ef5 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards 5396845a2abc 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards dff4dc479d8b 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 49bfbfe2e483 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards f65e3f35c6dd 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards 8706922574ae 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards d66b9742af56 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 1c8be0a8b8d8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards 7df937eb266c 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards aa166bc44bb6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards 655e0b348a52 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards f357427a7912 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards c3101800b537 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards 982a4e44ce20 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards 2fe82c32faf6 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards 3bafdc7edf9b 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards 09e33224b006 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards c55a7787c3c6 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 45dcc8b0d914 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards f3d99d8a5057 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards 32f22f2be76f 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards 8c52a6650391 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards b2f5acbf9a8f 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards e683604cc011 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards be1b6f1fea70 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards aaffd3892e5c 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards c87c8e14e09a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 29836e6fa710 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards f4dc3d789b30 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 8f9ff5e7c7f2 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 0a521acd07dc 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards e47876fe0be1 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards c34f7b4dd51a 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards cfa86c731c38 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards c3425788dbd5 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards 4ba834cacf3c 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards 06897d9d7a81 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards 66b91dfed7a7 149: onsuccess: #684: 1: Success after linux: 10 commits discards 5bbd06549dec 148: onsuccess: #683: 1: Success after glibc: 9 commits discards d79500085f2a 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 062696f35f49 146: onsuccess: #680: 1: Success after binutils: 20 commits discards d6ffad1466ac 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards 843268ec9cac 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards b5f50c7a8db9 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards b8e0b9429120 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 2939e812fcc9 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards 7a4a27bd5f32 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards 2b8241702d32 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards c41da763e576 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards ba33cf98be39 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards 3879cbbb924d 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards efdf7547c05c 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards e55f8090bfdf 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards d01d719cab01 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 0366390cd95f 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 67961e97970e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 4291e805bb8a 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 508b685dca6a 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards c8441788e989 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 7708984b1851 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 84074b33af0a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards f9bfc1cfb47e 125: onsuccess: #658: 1: Success after linux: 3224 commits new 8d0a5a2d670f 125: onsuccess: #658: 1: Success after linux: 3224 commits new 6286f409f9ec 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 13959ba9d0d5 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 8abacdcdbfa7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new cae20cf216b7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 371c14ef2009 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 82db390c850b 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 4c67973cd002 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new f22532fbc70d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new c060e720cc1e 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new 61ee2c65128b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new 8992ec749a04 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 8dccce2fe855 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new 8b3aa950eb42 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 20d6a67792ec 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new f8122c5f9d54 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 8cb515d70d0a 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new 183e0bbed0be 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 05911190ffa1 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 7eed9855e447 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new d6b65f039f71 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new 79dbbc438675 146: onsuccess: #680: 1: Success after binutils: 20 commits new 9ca22acdfcd4 147: onsuccess: #681: 1: Success after gcc: 6 commits new 60b32882f4b5 148: onsuccess: #683: 1: Success after glibc: 9 commits new 3d7aa492fcce 149: onsuccess: #684: 1: Success after linux: 10 commits new 1ae13cb11aa6 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new 470d7d1e2563 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new 4f5d4315d8a1 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new 96c18b97387b 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new 729979446472 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new 7d6dd4f0ae40 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 9d0314fc3ff3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new 8da4558a1add 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new ccbca671e21d 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new afc525c5bea4 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 9407f7531019 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new cc6bed519f28 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new 78322ff1899d 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new 2805740df6b3 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new 27074672d9ff 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new d3f47cf1fb5f 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new e94c85e7f409 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new b9e94adf4459 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new 8b85cbdbf70b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 390195895b20 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new 65bd90d78e96 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new c0b396734e19 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new d2231b39c57f 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new fc873720eccf 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new c205ae92fa33 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new 8b8ebd9159c7 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new ba51cfb1aa63 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new dfd0595177b7 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new fda6363bc5ed 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 9c6bf28e34e8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 2811bf9646e8 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new 9733f67971d1 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 0bb84065bc73 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 40c88845b870 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new 8ae64a14686b 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new b929b31f0311 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new dd1f7e45a1ae 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new a37254db7cb4 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new 83cfcdf4aa10 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new c822c09bdc88 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new f80e05a4ebc4 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new ad47e65835c3 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 44fa27ebe7dd 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 91b373c9e832 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 6a4952fd92c6 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new e6126fe9c1db 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new b8c3c986b998 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 25cee20e1b5f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 5a791f692b5e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 6d997d48b880 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 9ae870628dd9 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new b78f49f50335 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new a7a9a6dd7955 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 2c02ad76d6f8 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 483b7c50ddcc 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new ff506c14123a 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 50665656aa0d 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 9d53d513718d 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 5d54f8dd85d3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 8439265ca1f9 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new fb8f8764a940 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new a0a77261af6b 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 7471f8f927b5 212: force: #24: 1: Success after binutils: 2 commits new 6c0a229e327c 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new e5baa2a57808 214: onsuccess: #26: 1: Success after binutils: 12 commits new b1cb544f7233 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new c137d2c24d20 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 35a05c944f66 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 6f7186d2c1f7 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 13258bd572bb 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new ecb336fa466a 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 7c544160e5d4 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new ba64dad01df2 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new fc6e9018dfab 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 621be34b00d4 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new e9c19f9bed03 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 22bcdca72944 226: onsuccess: #42: 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 (a1903b9b4a83) \ 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 2104 -> 2092 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 35556 -> 35004 bytes 04-build_abe-gcc/console.log.xz | Bin 202368 -> 204000 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8400 -> 8880 bytes 07-build_abe-glibc/console.log.xz | Bin 240476 -> 240516 bytes 08-build_abe-gdb/console.log.xz | Bin 35408 -> 34692 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3784 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2944 -> 2100 bytes 11-check_regression/console.log.xz | Bin 5400 -> 4984 bytes 11-check_regression/results.compare | 10 +- 11-check_regression/results.compare2 | 157 ++--------------------------- 12-update_baseline/console.log | 42 ++++---- 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 | 49 +++++---- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +++---- manifest.sh | 36 +++---- sumfiles/binutils.log.xz | Bin 63032 -> 63000 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150784 -> 150812 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122556 -> 122632 bytes sumfiles/ld.sum | 7 +- 30 files changed, 111 insertions(+), 248 deletions(-)