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 cfdb4b7071c 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f3467ba4783 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d261fcf0f41 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 90cf9ad568f 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 33616b01cf3 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6cf3b242729 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 01429442a1c 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f4e341b0682 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 15cae539984 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards d6cc45cf224 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 5059292aa37 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 75cad3356f8 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0d519000c11 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 26cbaf8bacc 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 8fb5083a79f 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 766cb4a81c6 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 7e9d6c8a607 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards eaa175d881f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 0a9923da220 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards de5f5ff1c8d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9203227e03e 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 82e6de196df 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards daa94fcc292 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards f0b4aeb1fa8 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 28111226d97 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 3d2980643dc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 5a2ec8f3858 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 847676ff275 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards dfe5e995b9c 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 486a60f0aa9 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 6dac198c13b 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 518b562b61b 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 591ca15ed3b 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 5ae2b0d035f 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards bb020664177 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards ee966625583 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 9b1bbdc329e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 021ba4a9473 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 354bf10f098 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 62dc1606d36 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 89e38fd281c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 5c51a3b26cd 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards afac687eaeb 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 501ca8be407 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards caab44bcb6d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards a0f01329b19 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards aeb1e9aced2 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 3fe69412eda 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 1c2033edcd1 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 4b0a3b08ef3 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 31350486a99 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards f084587947f 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards aaa93417897 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d3ae8fed80f 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 02f0542d13d 162: onsuccess: #624: 1: Success after linux: 10 commits discards 0beecb5a7e8 161: onsuccess: #623: 1: Success after glibc: 9 commits discards b0b273a9227 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 7c34d7102ba 159: onsuccess: #620: 1: Success after binutils: 12 commits discards fa0e8ecf55d 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 51c7650d878 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards c44829765c9 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ec3180e1439 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards ee3fc706e60 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 3281ec5ee6f 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards d05455c1161 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards ef81746bca5 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 191f26e723f 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 64bce9ea9dc 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 4e7c34ba97d 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 0eced4c380c 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards da6e9b5ec5a 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards eb1aedd50f6 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 0e953b43e51 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 105ecd7d8dc 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards aaaeeda05a8 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 022b6b541c7 141: onsuccess: #601: 1: Success after linux: 794 commits discards e3fcae08090 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 5589c772999 139: onsuccess: #599: 1: Success after binutils: 10 commits discards f708b89afa6 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 8045fd3488f 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards adccb1672b5 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards f87b0e17fe0 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 25b4798e0e5 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 00b640ae893 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 0ca00f50f74 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 483ee0e455a 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 62993043368 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards f71d933bb9f 129: onsuccess: #588: 1: Success after linux: 4 commits discards 674b2ebaa13 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 4d9015b8754 127: onsuccess: #584: 1: Success after linux: 21 commits discards ccc39023cba 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 7128d3fc683 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 5843583ed32 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 3e33bfdee43 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 9ecfe706cc5 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards b9560341d2a 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 4b647bdbe62 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 52c9e27a1dd 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 5a1c7a598bc 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 1a72fd53ac0 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 92de0ae8a72 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new a95853d0651 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new cd1f9bc31c4 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 36b409ba7c8 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 32adbc9904c 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 2558b7dfb61 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new d4932d43bc7 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 507bdb0c642 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new a1e79ead498 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new e7091543f8b 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 22484fc1c74 125: onsuccess: #581: 1: Success after binutils: 4 commits new 72c96665d05 126: onsuccess: #582: 1: Success after gcc: 9 commits new f928f555564 127: onsuccess: #584: 1: Success after linux: 21 commits new 1c4af3f321d 128: onsuccess: #586: 1: Success after binutils: 22 commits new 66b35ddeff8 129: onsuccess: #588: 1: Success after linux: 4 commits new e3eb78005ad 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new f02d0bea3dc 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new f289565be29 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 3fc84bf619d 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 5afdc065621 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 5901e62b1ee 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 37048d84d24 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 92fcf6d5567 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 71e0838f4dd 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4fda99d9f8a 139: onsuccess: #599: 1: Success after binutils: 10 commits new d98314456d4 140: onsuccess: #600: 1: Success after gcc: 23 commits new 2e5bffd86c3 141: onsuccess: #601: 1: Success after linux: 794 commits new 1d4cbf24c5c 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3d689f0280f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 8f63df13b7c 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new c4a46b026c2 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 35f27f4d5ba 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 02ea173b15c 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3347507e7f5 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new ba791182e1e 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new a8ef6bb7efe 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 99a1310a8ba 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 5223cf4cf4c 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new f8b691b8d87 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 03961e9ea5f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 2464f836e77 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 5c4891fa2e4 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d6e18d2d305 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 90627ee64ca 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 00da0d11324 159: onsuccess: #620: 1: Success after binutils: 12 commits new c12f199f3cd 160: onsuccess: #621: 1: Success after gcc: 11 commits new 80abb6c75f4 161: onsuccess: #623: 1: Success after glibc: 9 commits new 7b3917c145e 162: onsuccess: #624: 1: Success after linux: 10 commits new b10da6e3e92 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 3891800c1b6 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new b05abe8ea87 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 32dd703c7d5 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 898e848d2e5 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 51b6a1ec951 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new ebda24cbb80 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 1e9959a1d68 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 70164bc6bc4 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new b3ce97dabe1 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 471000ffcc0 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 92f73a6807c 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 9d3ec2e7b52 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 1ca0459d75c 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new cfa91c30e7a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 6cad601c96b 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new edc6a586053 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 58fc608ce1d 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 80f1817f2e2 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 3d1d822f1cd 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new ec25051e00c 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 74a896074b6 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new d828c6c4902 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new ec6a8088f51 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new e0c6eace7c0 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8932ba46f20 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new fd90c29ba83 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 2e19203b599 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new bfec3ab7cba 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 24766e16615 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 3312e70dec4 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 5c2efc539e5 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 4a8a1c56a6a 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 224806be59a 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 2a3c32fc899 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new eeb80354958 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new ca7f266278f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 9f9480b2492 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new a67c54b4135 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new edd3f9d9be1 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a78ffa9a51a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 65322b6199e 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 77e017d986c 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bd81668e605 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 9b14bff75dc 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 3827c4ea7a8 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 5638b958bdb 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new fe43959f5cb 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8feffd36943 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 83cbdcb388a 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 97f5dff61f4 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 21512539caa 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7ea61a84ac3 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c00188ab422 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 91f0ef4d9d5 217: onsuccess: #14: 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 (cfdb4b7071c) \ 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52820 -> 52852 bytes 04-build_abe-gcc/console.log.xz | Bin 237636 -> 236152 bytes 06-build_abe-linux/console.log.xz | Bin 8268 -> 10100 bytes 07-build_abe-glibc/console.log.xz | Bin 235844 -> 235808 bytes 08-build_abe-gdb/console.log.xz | Bin 50532 -> 51524 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3796 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2844 -> 2536 bytes 11-check_regression/console.log.xz | Bin 6660 -> 6888 bytes 11-check_regression/results.compare | 15 ----- 11-check_regression/results.compare2 | 123 ++++++++++++++++++++++------------ 12-update_baseline/console.log | 40 +++++------ 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 2873856 -> 2861652 bytes sumfiles/g++.sum | 49 ++++++++++++-- sumfiles/gcc.log.xz | Bin 2447044 -> 2470068 bytes sumfiles/gcc.sum | 14 ++-- sumfiles/gfortran.log.xz | Bin 957452 -> 957728 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233672 -> 233896 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 470740 -> 468468 bytes 36 files changed, 183 insertions(+), 122 deletions(-)