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 af716e19fd5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards c026a271f8b 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2ff72004847 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8cdadcc895d 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a11403548d7 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7ff757ac3a7 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 58a94eadcb5 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 64a9790922c 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 3af4bf5bc80 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 04c29df9987 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards dc51ee6d8f3 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards a7f727458e8 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 680ae47d940 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 29b66d5f4e4 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e70cde63af0 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards d59cbdf341a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 84a87449206 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a7c5a2de321 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 8d38f806b19 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 82d1ab8df3f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 886b8cd64b4 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 2d6fbadce8d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 01f5d006d81 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 28e52003ab5 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 3461cb4132a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 0a372e36cca 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards c74bb61c07e 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 84c5d0c50f0 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a50afe04a17 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 821bf1e85f5 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 9d88bf4c954 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c7b539f0baa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards c8d19d32d98 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 77ab896dca6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 65867653194 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 806a7f6e4ce 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 44dad49bb01 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards f2a54f7d512 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards eae2c091b4e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 38b5cfa8844 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 7bc4954f3c7 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 08118875317 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 53a610eb98b 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards d65a25635cf 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 9c9d0790af8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 6d76e340e4e 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 42b0383d27f 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 30876f336e1 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 12fc8ae6287 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 5ace0be972d 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards f2a0617d2c0 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards dbde0515768 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards c253560fb40 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards a1d754a18be 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 9f4a6171ecd 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards feab433e55b 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards ef056c4d06d 162: onsuccess: #624: 1: Success after linux: 10 commits discards 21c3578cb8e 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 86100fcfe80 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 5d9de2e1fc4 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 732d11b11fa 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b86c88ad357 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards d75bac08921 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards c0c0d120761 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 4da3a5c0b64 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 62dd1088b7f 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 1fb90cda08a 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards de4571e62bc 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 1acab586009 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 3894348dde7 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e852da2f910 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 99639a5f87e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 3a20e291639 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d419ec76184 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards fa8ae4cb8a6 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards f1357cc2625 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 81b009148ac 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 3b42427d76e 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1043f04fba7 140: onsuccess: #600: 1: Success after gcc: 23 commits discards c0cd8e0da97 139: onsuccess: #599: 1: Success after binutils: 10 commits discards d5d9dc55f41 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 6048b166d49 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 670e2011b0e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 351cdb7a0ea 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards fa847811c18 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 213be7776c3 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 120e7a35e61 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards f020ba99062 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 1e641e0d6d5 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards fcd9feb2d59 129: onsuccess: #588: 1: Success after linux: 4 commits discards 2fbf90150db 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 1b106822e8a 127: onsuccess: #584: 1: Success after linux: 21 commits discards e1d04d8d8fe 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 15944a63e8d 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 190426b7957 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards b0edd102251 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 62983a4c4a0 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards c56a3610f34 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 697a6fbb6c1 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 8382f8c1486 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards fd239d27ffd 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 0c51c472089 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new cfb655ef490 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new ef6d8f8d0ef 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 1d5824386cf 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 0aa1ebb9954 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 46fffa6c17c 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 0620abc6c06 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 8342936b560 125: onsuccess: #581: 1: Success after binutils: 4 commits new b938f39d5ab 126: onsuccess: #582: 1: Success after gcc: 9 commits new 42bd41dbc18 127: onsuccess: #584: 1: Success after linux: 21 commits new a8aa1d07949 128: onsuccess: #586: 1: Success after binutils: 22 commits new c8523aa23b2 129: onsuccess: #588: 1: Success after linux: 4 commits new 69243f9374d 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new e7d6e79f906 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 7e49b681aeb 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 6f0ce6810ca 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 640e14a5bd0 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e4903e2d9c4 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new caf7aa9245b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 5ee1cb3d91a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 7c5e657f4a7 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 3b8bef384fc 139: onsuccess: #599: 1: Success after binutils: 10 commits new 6132b01ff33 140: onsuccess: #600: 1: Success after gcc: 23 commits new 55d90a58878 141: onsuccess: #601: 1: Success after linux: 794 commits new 0c52b0e0f2b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new c00f888b38e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 9f38e9196c3 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 04ab3d3fc25 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new a7a3b463fd9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 38271c1b3b7 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 9418acde8cb 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8be14e2f977 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 9785175a85e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 690b21cb6bd 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 1dcf09fdee2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 9f47d0b0d6d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 5cb8e9c216a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 156d6a0244f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 5ce7773ed4d 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 12ae768cc9d 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 31c4d614f94 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 9cc2ff634a2 159: onsuccess: #620: 1: Success after binutils: 12 commits new d2cb038865a 160: onsuccess: #621: 1: Success after gcc: 11 commits new f4a89ead038 161: onsuccess: #623: 1: Success after glibc: 9 commits new e7723bc76b9 162: onsuccess: #624: 1: Success after linux: 10 commits new 488b770cec2 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 3a4e7765095 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 2c448f93f39 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 379e26b79d2 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 44647e79ad1 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c81a62f690e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 621080c9374 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 126aa838282 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new c034cd59fd5 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new dad92ea003d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 447c705182d 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 61d0e62eb2b 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 2325312203d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 946ae980893 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9b94350307f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 426b4e769b2 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 54f1fffc059 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a5698fbc66c 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new a0279c85b57 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 01d6c97dab6 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 236cd21132f 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new a51dca2bbe5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new b3eb09d6222 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b315aa5ae0f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 4cfd0c9d6c4 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7ae91b84b54 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ba0128dc836 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new d4204f9046c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e2da92a8ebc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 37d5a06fbd5 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 5414b02684e 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 51cc3a14c2e 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new f7fa7575b90 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 0c4a78f6368 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 8872bb396ff 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new ffb6157ff86 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 19c67288121 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a8337fa300f 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new da5a49f5ff9 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 1d326d6987d 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new e6a31d6c479 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 28eef3235e1 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new c81664abb0f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4e5090eef5f 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3cada1a7aa4 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 9012c6bce13 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new acde37f4c64 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 55be940504e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new eeba28d1707 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new ad3c3b65901 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d67a1aac957 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new acadcb64a22 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 5336a0188a4 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new bdebf1cbbf5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c5609fbae8f 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2ecde34ff92 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 5391a592858 219: onsuccess: #16: 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 (af716e19fd5) \ 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 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 53088 -> 52484 bytes 04-build_abe-gcc/console.log.xz | Bin 237580 -> 237308 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 235604 -> 235656 bytes 08-build_abe-gdb/console.log.xz | Bin 50168 -> 51332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3768 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2608 -> 3080 bytes 11-check_regression/console.log.xz | Bin 6944 -> 7120 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 172 ++++++++------- 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 | 36 ++-- sumfiles/g++.log.xz | Bin 2891988 -> 2905124 bytes sumfiles/g++.sum | 146 ++++++++----- sumfiles/gcc.log.xz | Bin 2440428 -> 2468624 bytes sumfiles/gcc.sum | 379 ++++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 950696 -> 957524 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233916 -> 234156 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465420 -> 473876 bytes sumfiles/libstdc++.sum | 14 +- 38 files changed, 497 insertions(+), 410 deletions(-)