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 0909f569bc 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 107621823d 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards c5b23cc442 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 7982f8b73d 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 31d581737a 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 3ba952c48f 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards c7b391b80a 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards c779cd8802 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 34ffd07ec8 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 3c2e0242f7 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards aac9d58c3c 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 8a81096c7b 103: onsuccess: #555: 1: Success after binutils: 4 commits discards dbf5aa2624 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 00db668e4b 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards a35faa2856 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards ff4d721583 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e363d504e0 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards b647bb891f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 7781c78219 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards e0e8588ea0 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 8568e3b4bd 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards b2e8d304c0 93: onsuccess: #544: 1: Success after linux: 34 commits discards 743878ed0c 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 56f7f122b6 91: onsuccess: #539: 1: Success after linux: 27 commits discards c00a61616a 90: onsuccess: #538: 1: Success after glibc: 10 commits discards c8035603f9 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 2ed18494a1 88: onsuccess: #534: 1: Success after linux: 12 commits discards 60ef9348ee 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards aa421fce39 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 46a3bb7bf6 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 27888b0e21 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 3f2a8f6f3f 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards d698806270 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 3d7411e6ff 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards be959dc147 80: onsuccess: #524: 1: Success after linux: 9 commits discards 588e21b922 79: onsuccess: #523: 1: Success after gcc: 25 commits discards c1bc76acc5 78: onsuccess: #522: 1: Success after binutils: 10 commits discards e843e17015 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 84e45e89f4 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards f5f411cffa 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 36e1c9f59e 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 3655ecc93f 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 6f82b4302d 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards d5fa9e0ab5 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 88073d6402 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 183f733a86 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards fe580385f1 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 73eb7288d3 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 09e8061ba0 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards b350515109 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards d2e6e61bad 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards b41fc39d0d 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 4e489074e5 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 27a1dd9b45 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 993aa584f6 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 4204fee952 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 219b4c35f5 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards fd79697041 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 098dd22dd5 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 8099d1c330 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 3c4455ded7 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards f5a2f8521c 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards a6fc55d9fc 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 5f376f7498 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 43081266c9 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 599d90702e 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 71042832d3 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 38cae9388d 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards ae074104ae 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 3ff09fbe14 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 091f199b6c 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 0fceb57823 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 2a53e3a595 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 22a6ed323c 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 3a88b162be 40: onsuccess: #476: 1: Success after linux: 69 commits discards 0c27f573ea 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 1b7f018421 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 125fef6857 37: onsuccess: #470: 1: Success after binutils: 3 commits discards a5a1aa8bee 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards b5fdb93037 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 1208abdf7b 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 3d6e70aff9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards f46cdeafa4 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards a25455e6db 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 157b8ee54f 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards b445c488ba 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 2e206d84f0 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards af9ae217bb 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 0ec95e3e0a 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 7b8b095fe9 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards f03b3206f7 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 90d2f0b0ae 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 0f9137d2dc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 946d499c75 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 6458922eb4 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f68129484 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a682eaa88 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 49012c1cee 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1ca65d117b 16: onsuccess: 1: Successful build after binutils: 5 commits discards 71e25225b1 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5ace759358 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e3b29face2 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d9fa2a962 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f44c8774da 16: onsuccess: 1: Successful build after binutils: 5 commits new 2018118ec5 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d084e88388 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7715bc95b8 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7e02ca83b2 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fe155277ac 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new eb47ed0ad2 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e4226c878c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new c47e3aebf1 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new b59cb44edf 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 72075f88b2 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 4d9c01242a 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new b6463d0c6e 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 31ee56bcbd 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new a44c218c90 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new c7dabb0d76 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 00e8fa68cc 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new e458c02f8b 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 2520d69bb2 34: onsuccess: #465: 1: Success after binutils: 11 commits new a42810391c 35: onsuccess: #467: 1: Success after glibc: 2 commits new 2739bbd438 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 103bd354e3 37: onsuccess: #470: 1: Success after binutils: 3 commits new d81a98f22e 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 8f6d778d32 39: onsuccess: #474: 1: Success after binutils: 8 commits new df0e55be1b 40: onsuccess: #476: 1: Success after linux: 69 commits new 31669fd566 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 39b07ab2b5 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new fb1f81500c 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 02a9ea4d9a 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new ba2094f48e 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new eeb4135580 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new fe34ab8c17 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 997df99aba 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 9cef91ee87 49: onsuccess: #487: 1: Success after binutils: 11 commits new 50eb9944b7 50: onsuccess: #490: 1: Success after binutils: 6 commits new e1f783d2e1 51: onsuccess: #493: 1: Success after binutils: 13 commits new 64cd0e2608 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 4f15e58cdb 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 7893f4c39b 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new f9237a2cfb 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new c771d5086b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new b6d176293b 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new a4b5395181 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new cac83532a9 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new a709fb85e4 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 9474a63a0c 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 5f09e0c630 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 27c49453ff 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new c5bc788a9f 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 787670bbc7 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new bcfbf18dad 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new ef9b4c2555 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new bf1f59c4aa 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new fa4c840607 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new b0456c3223 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new dd337f3b5b 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 28b44f05bb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 2eb42edae8 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 81940dd581 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new dc2b10fbee 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new d4dfaf8934 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 16c5b7e2df 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new e9f1d47443 78: onsuccess: #522: 1: Success after binutils: 10 commits new 564447b225 79: onsuccess: #523: 1: Success after gcc: 25 commits new 0f4186d35b 80: onsuccess: #524: 1: Success after linux: 9 commits new 117d21213b 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 8098a0ec1e 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 755bc377d6 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 0e765b4db6 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new e695881e8d 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 5a43115128 86: onsuccess: #532: 1: Success after gcc: 16 commits new d1aabd5e34 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 4723ff44eb 88: onsuccess: #534: 1: Success after linux: 12 commits new 0a9e40a98d 89: onsuccess: #536: 1: Success after binutils: 27 commits new 046f3688cd 90: onsuccess: #538: 1: Success after glibc: 10 commits new 33b1d88dc3 91: onsuccess: #539: 1: Success after linux: 27 commits new 271f9db73b 92: onsuccess: #543: 1: Success after glibc: 4 commits new 4d1b0d5030 93: onsuccess: #544: 1: Success after linux: 34 commits new ec01095130 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new adea842578 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e4078ae753 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 70bd1fb54f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 8ddb7ce100 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 42a69e7aae 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new e1c7b0b87d 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new bd06319d82 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new d8237d03c2 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new cc18e90f9a 103: onsuccess: #555: 1: Success after binutils: 4 commits new b041e22aaf 104: onsuccess: #558: 1: Success after binutils: 3 commits new 1475d7edeb 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 61b7cec124 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 0d525c774f 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 65c22a2a31 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 5eafb7025a 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new f72f2fb7c9 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new eb92ddd7b7 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 3673c251da 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 69ba976e33 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 9bfab912d5 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 5ce926e903 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...]
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 (0909f569bc) \ 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 1676 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 52368 -> 52352 bytes 04-build_abe-gcc/console.log.xz | Bin 234740 -> 235428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8840 -> 9512 bytes 07-build_abe-glibc/console.log.xz | Bin 234692 -> 234836 bytes 08-build_abe-gdb/console.log.xz | Bin 50576 -> 51828 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3848 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2668 bytes 11-check_regression/console.log.xz | Bin 6936 -> 7376 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 9 - 11-check_regression/mail-body.txt | 81 +- 11-check_regression/results.compare | 38 +- 11-check_regression/results.compare2 | 216 +- 11-check_regression/results.regressions | 43 - 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 83 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 43 - sumfiles/g++.log.xz | Bin 2912452 -> 2893832 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2518156 -> 2507164 bytes sumfiles/gcc.sum | 4644 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 955016 -> 957780 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 228168 -> 229160 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 467348 -> 471232 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2709 insertions(+), 2755 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