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 90adc78f70 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 8048fba4b5 104: onsuccess: #558: 1: Success after binutils: 3 commits discards d0c8eb60e3 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 1cf458b911 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 3bc3b17e95 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 5d4237c82f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 81e341b379 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards fbafe3c97c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 7cacc67d1f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 21d07426bb 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 9955492751 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 8da6aef608 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 2a99c811aa 93: onsuccess: #544: 1: Success after linux: 34 commits discards 98590ddeab 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 03ce45e511 91: onsuccess: #539: 1: Success after linux: 27 commits discards b9fa24c549 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 5c7f3a6520 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 437f82ee65 88: onsuccess: #534: 1: Success after linux: 12 commits discards 78f2c03d00 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 4a2707bf8e 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 6d994ad268 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 65539ba792 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards e883786190 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 6a9187b0f9 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 0bcc4c618b 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 015aad69dc 80: onsuccess: #524: 1: Success after linux: 9 commits discards eaa2636b57 79: onsuccess: #523: 1: Success after gcc: 25 commits discards b34966c836 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 442d152c61 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 29eb29a7fc 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 5d879ce44d 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards d25318e0e1 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards ce5f0acff9 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 0f01487fae 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards a6f9ba575b 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards f964275d35 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 563961ad8a 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 2e7d0c4782 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 20c68f171d 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards ff72942411 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards afdc7cc91d 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 2d29ac2dff 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 0d0c8cae42 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards b28f97eeb7 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards fe1a1efef1 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 4ad5b66892 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards e769b12eb0 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 234f400c16 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards c5555da726 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 4a525aaceb 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 6cdb308643 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 1eac756881 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d9b7b109ca 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 4afe283434 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 4b96e206c6 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 4ec30e6039 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 6fafa526a1 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 5604b763b2 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 69946be9a9 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards d307f46f04 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards b6eaf4b4e0 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards f099c2658e 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 9fdf1017c4 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 8e4b3633b3 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 8fe206ab24 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 555f8edbba 40: onsuccess: #476: 1: Success after linux: 69 commits discards 321c35a84b 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 5109ba7988 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards a8f44b327a 37: onsuccess: #470: 1: Success after binutils: 3 commits discards f948f5605a 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards dbd4936695 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 31c09daf29 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 38f0dc7fbd 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 1020ed3461 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 4d7eb0cb87 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 0fd741febe 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards d0db820cd2 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards f758b2deff 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 203708c421 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards b842647614 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 482e3a2723 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 9ae2507e20 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards a47ab9455c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 869eabcc27 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards a261c56496 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f8b1fdd8ce 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32ab4e14a3 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e079a7dd5f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8ef5a1865 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80b01c6986 16: onsuccess: 1: Successful build after binutils: 5 commits discards ecfff1b1bb 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d9f41ae4b2 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 61fc168c30 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e7ff1f24d8 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f45d297303 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c7d8af59cb 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0bcd770df5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e73a0773ba 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 43ea84f194 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 5a499c8464 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8f7a6aadf2 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 886455a98b 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 112bf04852 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 758e10bbaf 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e1daee884b 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 942099bb05 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6743b52a65 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 367a3d886b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e39709870a 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a30f2c4200 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29b5ff7479 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51043b84c6 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c5767deae 16: onsuccess: 1: Successful build after binutils: 5 commits new 3132a91c53 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d51cbc0d47 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3466297e90 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ac046c0cd 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 42aa72bb91 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 57b96913a0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 37af35d748 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new bc4ef1ff27 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new da08783add 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 41aa17e86f 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 4cb2f211b9 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new b536d39b20 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new b1ddee5d71 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new c561df8dd7 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 8218b0b49b 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 8b965ec60e 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new eac6c5fa17 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 13d90a86ed 34: onsuccess: #465: 1: Success after binutils: 11 commits new 80a7ef7601 35: onsuccess: #467: 1: Success after glibc: 2 commits new 2e6090316d 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 47583a6b76 37: onsuccess: #470: 1: Success after binutils: 3 commits new 19dec0e0b7 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 4a8b7493f9 39: onsuccess: #474: 1: Success after binutils: 8 commits new 2985a3b748 40: onsuccess: #476: 1: Success after linux: 69 commits new 1a7000bcbf 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new ea1c263087 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 9a6eae49da 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 9f051286f8 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new ffec2ed569 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 74037fd372 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 39b3cfb250 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 0835efefa2 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 8ebc2ea959 49: onsuccess: #487: 1: Success after binutils: 11 commits new 97c3d9019a 50: onsuccess: #490: 1: Success after binutils: 6 commits new 767bbb6424 51: onsuccess: #493: 1: Success after binutils: 13 commits new bbb5fa0e89 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 10b8a88b1b 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new c1fe855dec 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 18088ae6ba 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 8dc8d9fb66 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 50820ae68c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new dfcddd965c 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 0e2d244d61 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 09684372c8 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new dc2ec50ad9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 4af5ffff2d 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 890d027cba 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 0aa0a85703 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 1e199da362 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 558cfd5ca5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new c7d08a3323 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new dde6b454d8 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 3a337e95c5 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 4b6da8aaf7 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new de712e2165 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 371b5ab1bb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 50cb8d3dbd 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 792c6ebe54 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 6515b8bbc0 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 034207c439 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 1fa43db508 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 5335db9900 78: onsuccess: #522: 1: Success after binutils: 10 commits new a02e58d58a 79: onsuccess: #523: 1: Success after gcc: 25 commits new 9c7ab9e0fc 80: onsuccess: #524: 1: Success after linux: 9 commits new fc3e166714 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 49d7698bce 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 34ab854168 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 70f977bcb9 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 52942fd92b 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 37f5adc2e0 86: onsuccess: #532: 1: Success after gcc: 16 commits new fd15abf0ce 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 62d1adebc1 88: onsuccess: #534: 1: Success after linux: 12 commits new 26db0b30de 89: onsuccess: #536: 1: Success after binutils: 27 commits new 5168a7c8bd 90: onsuccess: #538: 1: Success after glibc: 10 commits new 6e00493ba8 91: onsuccess: #539: 1: Success after linux: 27 commits new 2ca3302347 92: onsuccess: #543: 1: Success after glibc: 4 commits new 96aa5c4fb0 93: onsuccess: #544: 1: Success after linux: 34 commits new ca7e22c6a6 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 244da612c9 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 080c7ca2a2 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new f116f1333e 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 730e2189a8 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 21999df736 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 93dd91c325 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 7502bcacc2 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new d4c9f8f15e 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 176ca3ae10 103: onsuccess: #555: 1: Success after binutils: 4 commits new 97749eba0a 104: onsuccess: #558: 1: Success after binutils: 3 commits new 6e0e7244ac 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new e22c0bbe82 106: onsuccess: #561: 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 (90adc78f70) \ 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 1892 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 53232 -> 53532 bytes 04-build_abe-gcc/console.log.xz | Bin 234320 -> 234244 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9004 -> 8936 bytes 07-build_abe-glibc/console.log.xz | Bin 238556 -> 236088 bytes 08-build_abe-gdb/console.log.xz | Bin 52396 -> 51604 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3876 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2596 -> 2468 bytes 11-check_regression/console.log.xz | Bin 11916 -> 6216 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 11 +- 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 41 +- 11-check_regression/results.compare2 | 991 +------ 11-check_regression/results.regressions | 41 +- 12-update_baseline/console.log | 40 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 41 +- sumfiles/g++.log.xz | Bin 2851612 -> 2880608 bytes sumfiles/g++.sum | 143 +- sumfiles/gcc.log.xz | Bin 2530548 -> 2525668 bytes sumfiles/gcc.sum | 4744 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 951992 -> 953676 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229112 -> 229468 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469300 -> 470208 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2739 insertions(+), 3617 deletions(-)