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 d0c6f2946e89 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 2b0513291123 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] discards a71366877014 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 2403ad5f3a5d 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards a08f4390987a 141: onsuccess: #601: 1: Success after linux: 794 commits discards 07c482451822 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 3086bb5f304a 139: onsuccess: #599: 1: Success after binutils: 10 commits discards d63c535faed4 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards ac424870118a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 6cb6952c27ef 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards f2800571da1a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards cfa1857c750e 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards 8b5b231a3f0d 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards c5c5ab7af9d8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards a13421bfdd59 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards 5d9347dbdc5b 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards 8ff8a53643a4 129: onsuccess: #588: 1: Success after linux: 4 commits discards 9eee28bca476 128: onsuccess: #586: 1: Success after binutils: 22 commits discards a7cb57716a12 127: onsuccess: #584: 1: Success after linux: 21 commits discards ccf253d5a580 126: onsuccess: #582: 1: Success after gcc: 9 commits discards b32330bbdc58 125: onsuccess: #581: 1: Success after binutils: 4 commits discards f6f06b6ff1d3 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] discards 277148ca71b1 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] discards 2221e86b1cd2 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards cd7a837cac06 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards b566124b2af2 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards 1e22d40805cf 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] discards 938691b39759 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] discards abb14c4c5955 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] discards 23e8c424eda1 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] discards 1e984746d694 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards 13e86efa30b7 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] discards d3a44b79cfa7 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] discards cc7843816dd8 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards b1456ad4b7c9 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 105ac265bd34 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards c9148630102e 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards 2768e22f6ffe 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] discards 56793c40fc61 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 00ba84b7c85c 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards dfd95e86089b 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 8bbf8126d875 104: onsuccess: #558: 1: Success after binutils: 3 commits discards fe6bf2bde775 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 0dc7cdadc44d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards e8833be54e29 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards d434171c266e 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 1b2a44e34895 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards f67f68508970 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 759b80a0c7aa 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 4b69579e191c 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 36e09ae4a4f9 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards b0993a7b3d09 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards a2dcf33f9ce7 93: onsuccess: #544: 1: Success after linux: 34 commits discards 1b96df00648f 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 6829e3fed813 91: onsuccess: #539: 1: Success after linux: 27 commits discards 29aa6f739e42 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 7cdb416ec12a 89: onsuccess: #536: 1: Success after binutils: 27 commits discards dd5a3c164be6 88: onsuccess: #534: 1: Success after linux: 12 commits discards 42966ffc55dd 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] discards 96a6a8b7d5c6 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 264dd9ca0d2d 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards b64c732226db 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] discards 335600022c86 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] discards ec2b7e59b3d5 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] discards ffb1207de804 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] discards 0cbf14689fec 80: onsuccess: #524: 1: Success after linux: 9 commits discards d0da93739540 79: onsuccess: #523: 1: Success after gcc: 25 commits discards cc070032512c 78: onsuccess: #522: 1: Success after binutils: 10 commits discards cfacac862dff 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] discards d8fdd29c4609 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 2f890a352fe6 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 11cf4061734a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 485a3e942b41 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] discards 2dc253c276f2 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] discards 4fdda91308e0 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 5d3d69b73fb4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards d1347535cd6d 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards ed92aaad242d 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] discards f27c36ceb4e3 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] discards da1c71be5977 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] discards ec6245cd3ba6 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] discards 25bab2f54b69 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] discards d862e2b48a1b 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] discards 04139432cab4 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] discards ee1f9aecb283 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] discards b4ecb05c7053 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] discards c71954a4aa04 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] discards fc12f00f2d73 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 3ceae8dd3101 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards dc8016af548b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards 32970bd7a14e 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards 7da8b492c1ba 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards 2f6cbf78feb8 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards e3098b269d9d 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 51092b465ea2 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 908ec345c698 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 56d6fe89b1ba 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 3027ddabdf79 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards f03a8c5dc0e2 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 2c574f45b53b 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards 45bce13d6703 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new f04362d13604 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 4feb9ec0aa77 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 5d27c3fffcec 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new c682e6155c4e 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new c0ce025f2978 49: onsuccess: #487: 1: Success after binutils: 11 commits new 3a3af1045bf5 50: onsuccess: #490: 1: Success after binutils: 6 commits new ab6277b9d22b 51: onsuccess: #493: 1: Success after binutils: 13 commits new 7d6b20097d65 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new a7b22588e6a7 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new a733b495c087 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 30e807950ac8 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new 87aa9698ec7e 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new a38192dabc2e 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new bc2fbf749d3f 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new abbeb98480eb 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] new 1bfdef614afd 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] new 000a795992d9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] new dc9575202c58 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] new b34e6a1b8319 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] new d32ce63d4003 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] new 90cbd2131c09 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] new a1f61a73398a 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] new b8a015062ed0 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] new 107f63c6b5ef 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] new 018ebfb062ba 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 50463340f616 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new cd1b3d7d40e8 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 9cdb198fd61a 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] new 0e00b0f6544c 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] new d0a344fa7948 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 63766a95b3cd 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new b4b5b3d463ca 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 27613ce7c048 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] new d3137d851ddc 78: onsuccess: #522: 1: Success after binutils: 10 commits new 39551e5e8783 79: onsuccess: #523: 1: Success after gcc: 25 commits new 7ac6f708ca95 80: onsuccess: #524: 1: Success after linux: 9 commits new e9020bbe064a 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] new 0288705089c1 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] new 875b04667534 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] new 16494f2e81d8 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] new 50cd41a3c631 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new ac2ead73729a 86: onsuccess: #532: 1: Success after gcc: 16 commits new a698a57494ee 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] new 4d14c7b45696 88: onsuccess: #534: 1: Success after linux: 12 commits new f914d06268ba 89: onsuccess: #536: 1: Success after binutils: 27 commits new cd76c5fcc27c 90: onsuccess: #538: 1: Success after glibc: 10 commits new 3e14a6d26c26 91: onsuccess: #539: 1: Success after linux: 27 commits new d0b776d41a56 92: onsuccess: #543: 1: Success after glibc: 4 commits new ac8045ce8182 93: onsuccess: #544: 1: Success after linux: 34 commits new 5612d9471cab 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new c2328604727e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 5c5822b6d564 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 9fb633d4b0f2 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 7d973b644d77 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 1ec8e5b694f1 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new b15d4b059420 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new 8888c9e78ecb 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 6791783b6ce3 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new d8730853af6f 103: onsuccess: #555: 1: Success after binutils: 4 commits new 6d1ad5383315 104: onsuccess: #558: 1: Success after binutils: 3 commits new 8da70a140efd 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new a5c14927b0f6 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new c2199db49149 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 321c91897929 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] new 58a77d467eb4 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 3ef3dec57296 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new 7017bd85c3cf 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new 97eddffc632d 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new 274a72b5b274 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] new 88019f93656f 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] new 6731fe37239b 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new 1e43900bf364 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] new 620c475406ff 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] new 7b63a36ec767 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] new 7246ac758048 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] new c5e3adfc772e 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new c6109c25640b 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new f21c2d2e9301 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 872741a16116 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] new a64c7732f944 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] new 41e7ff980664 125: onsuccess: #581: 1: Success after binutils: 4 commits new 164744264596 126: onsuccess: #582: 1: Success after gcc: 9 commits new 3148597a60d6 127: onsuccess: #584: 1: Success after linux: 21 commits new 27a982392c48 128: onsuccess: #586: 1: Success after binutils: 22 commits new 02091e93f5b8 129: onsuccess: #588: 1: Success after linux: 4 commits new 732a3705bd95 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new 15b61bbe4e97 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new de19a0b3244a 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 9ad63edf4294 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new d6d657dbad44 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new aa7f1f1fe402 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 1863fc427b7e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new 2a17170c3ed9 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new d628c31a1b14 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 9021bc90c848 139: onsuccess: #599: 1: Success after binutils: 10 commits new 32e57100d106 140: onsuccess: #600: 1: Success after gcc: 23 commits new 81a92f232d26 141: onsuccess: #601: 1: Success after linux: 794 commits new 62aef0ad1f99 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 88702108431b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new c700d16cd00a 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] new 045b109864c9 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 255bb4241b11 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...]

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 (d0c6f2946e89) \ 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 1732 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 54044 -> 53224 bytes 04-build_abe-gcc/console.log.xz | Bin 235540 -> 234736 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9228 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 236940 -> 235872 bytes 08-build_abe-gdb/console.log.xz | Bin 52128 -> 51076 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2536 -> 3204 bytes 11-check_regression/console.log.xz | Bin 7140 -> 6916 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 10 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 44 +- 11-check_regression/results.compare2 | 113 +- 11-check_regression/results.regressions | 45 - 12-update_baseline/console.log | 46 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 45 - sumfiles/g++.log.xz | Bin 2912752 -> 2925236 bytes sumfiles/g++.sum | 158 +- sumfiles/gcc.log.xz | Bin 2592436 -> 2556024 bytes sumfiles/gcc.sum | 4513 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 950768 -> 955736 bytes sumfiles/gfortran.sum | 100 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229736 -> 230680 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468764 -> 474876 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2575 insertions(+), 2712 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions