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_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards 91f0ef4d9d5 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards c00188ab422 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 7ea61a84ac3 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 21512539caa 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 97f5dff61f4 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 83cbdcb388a 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 8feffd36943 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards fe43959f5cb 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 5638b958bdb 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 3827c4ea7a8 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 9b14bff75dc 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards bd81668e605 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 77e017d986c 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 65322b6199e 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a78ffa9a51a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards edd3f9d9be1 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a67c54b4135 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 9f9480b2492 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards ca7f266278f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards eeb80354958 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 2a3c32fc899 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 224806be59a 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4a8a1c56a6a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 5c2efc539e5 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 3312e70dec4 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 24766e16615 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards bfec3ab7cba 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 2e19203b599 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards fd90c29ba83 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8932ba46f20 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards e0c6eace7c0 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ec6a8088f51 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards d828c6c4902 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 74a896074b6 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards ec25051e00c 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 3d1d822f1cd 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 80f1817f2e2 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 58fc608ce1d 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards edc6a586053 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 6cad601c96b 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards cfa91c30e7a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 1ca0459d75c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 9d3ec2e7b52 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 92f73a6807c 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 471000ffcc0 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards b3ce97dabe1 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 70164bc6bc4 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 1e9959a1d68 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards ebda24cbb80 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 51b6a1ec951 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 898e848d2e5 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 32dd703c7d5 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards b05abe8ea87 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 3891800c1b6 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards b10da6e3e92 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 7b3917c145e 162: onsuccess: #624: 1: Success after linux: 10 commits discards 80abb6c75f4 161: onsuccess: #623: 1: Success after glibc: 9 commits discards c12f199f3cd 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 00da0d11324 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 90627ee64ca 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d6e18d2d305 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 5c4891fa2e4 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 2464f836e77 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 03961e9ea5f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards f8b691b8d87 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 5223cf4cf4c 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 99a1310a8ba 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards a8ef6bb7efe 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards ba791182e1e 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 3347507e7f5 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 02ea173b15c 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 35f27f4d5ba 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c4a46b026c2 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 8f63df13b7c 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 3d689f0280f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 1d4cbf24c5c 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 2e5bffd86c3 141: onsuccess: #601: 1: Success after linux: 794 commits discards d98314456d4 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 4fda99d9f8a 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 71e0838f4dd 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 92fcf6d5567 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 37048d84d24 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 5901e62b1ee 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5afdc065621 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 3fc84bf619d 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards f289565be29 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards f02d0bea3dc 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards e3eb78005ad 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 66b35ddeff8 129: onsuccess: #588: 1: Success after linux: 4 commits discards 1c4af3f321d 128: onsuccess: #586: 1: Success after binutils: 22 commits discards f928f555564 127: onsuccess: #584: 1: Success after linux: 21 commits discards 72c96665d05 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 22484fc1c74 125: onsuccess: #581: 1: Success after binutils: 4 commits discards e7091543f8b 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards a1e79ead498 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 507bdb0c642 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards d4932d43bc7 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 2558b7dfb61 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 32adbc9904c 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 36b409ba7c8 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards cd1f9bc31c4 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 078753b4254 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new fd239d27ffd 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 8382f8c1486 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 697a6fbb6c1 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new c56a3610f34 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 62983a4c4a0 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new b0edd102251 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 190426b7957 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 15944a63e8d 125: onsuccess: #581: 1: Success after binutils: 4 commits new e1d04d8d8fe 126: onsuccess: #582: 1: Success after gcc: 9 commits new 1b106822e8a 127: onsuccess: #584: 1: Success after linux: 21 commits new 2fbf90150db 128: onsuccess: #586: 1: Success after binutils: 22 commits new fcd9feb2d59 129: onsuccess: #588: 1: Success after linux: 4 commits new 1e641e0d6d5 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new f020ba99062 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 120e7a35e61 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 213be7776c3 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new fa847811c18 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 351cdb7a0ea 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 670e2011b0e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 6048b166d49 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new d5d9dc55f41 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new c0cd8e0da97 139: onsuccess: #599: 1: Success after binutils: 10 commits new 1043f04fba7 140: onsuccess: #600: 1: Success after gcc: 23 commits new 3b42427d76e 141: onsuccess: #601: 1: Success after linux: 794 commits new 81b009148ac 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new f1357cc2625 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new fa8ae4cb8a6 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new d419ec76184 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 3a20e291639 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 99639a5f87e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new e852da2f910 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 3894348dde7 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 1acab586009 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new de4571e62bc 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 1fb90cda08a 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 62dd1088b7f 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 4da3a5c0b64 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new c0c0d120761 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new d75bac08921 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new b86c88ad357 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 732d11b11fa 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 5d9de2e1fc4 159: onsuccess: #620: 1: Success after binutils: 12 commits new 86100fcfe80 160: onsuccess: #621: 1: Success after gcc: 11 commits new 21c3578cb8e 161: onsuccess: #623: 1: Success after glibc: 9 commits new ef056c4d06d 162: onsuccess: #624: 1: Success after linux: 10 commits new feab433e55b 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 9f4a6171ecd 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new a1d754a18be 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c253560fb40 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new dbde0515768 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new f2a0617d2c0 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 5ace0be972d 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 12fc8ae6287 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 30876f336e1 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 42b0383d27f 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 6d76e340e4e 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 9c9d0790af8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new d65a25635cf 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 53a610eb98b 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 08118875317 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 7bc4954f3c7 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 38b5cfa8844 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new eae2c091b4e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new f2a54f7d512 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 44dad49bb01 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 806a7f6e4ce 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 65867653194 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 77ab896dca6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new c8d19d32d98 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new c7b539f0baa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 9d88bf4c954 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 821bf1e85f5 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a50afe04a17 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 84c5d0c50f0 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new c74bb61c07e 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 0a372e36cca 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 3461cb4132a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 28e52003ab5 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 01f5d006d81 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 2d6fbadce8d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 886b8cd64b4 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 82d1ab8df3f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 8d38f806b19 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new a7c5a2de321 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 84a87449206 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new d59cbdf341a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new e70cde63af0 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 29b66d5f4e4 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 680ae47d940 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new a7f727458e8 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new dc51ee6d8f3 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 04c29df9987 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 3af4bf5bc80 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 64a9790922c 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 58a94eadcb5 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7ff757ac3a7 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new a11403548d7 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 8cdadcc895d 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2ff72004847 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c026a271f8b 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new af716e19fd5 218: onsuccess: #15: 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 (91f0ef4d9d5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 52852 -> 53088 bytes 04-build_abe-gcc/console.log.xz | Bin 236152 -> 237580 bytes 06-build_abe-linux/console.log.xz | Bin 10100 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 235808 -> 235604 bytes 08-build_abe-gdb/console.log.xz | Bin 51524 -> 50168 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3744 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2536 -> 2608 bytes 11-check_regression/console.log.xz | Bin 6888 -> 6944 bytes 11-check_regression/results.compare2 | 145 +++++++++++++++++----------------- 12-update_baseline/console.log | 62 +++++++-------- 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 | 38 ++++----- sumfiles/g++.log.xz | Bin 2861652 -> 2891988 bytes sumfiles/g++.sum | 29 +++++-- sumfiles/gcc.log.xz | Bin 2470068 -> 2440428 bytes sumfiles/gcc.sum | 31 +++++++- sumfiles/gfortran.log.xz | Bin 957728 -> 950696 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2276 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233896 -> 233916 bytes sumfiles/libgomp.sum | 10 ++- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 468468 -> 465420 bytes 35 files changed, 195 insertions(+), 144 deletions(-)