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 9fd3a81154 104: onsuccess: #558: 1: Success after binutils: 3 commits discards cddb1ab3aa 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 823cc4453d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 9e9bcf36c1 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 8ce6da6529 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards c73f427874 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 2bb8d9553e 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards c8912460a7 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards e620f162cd 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 0d21d25e38 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards e1299785c3 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards e0b97874e8 93: onsuccess: #544: 1: Success after linux: 34 commits discards d37a6bdbef 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 6874f66657 91: onsuccess: #539: 1: Success after linux: 27 commits discards f16deed73c 90: onsuccess: #538: 1: Success after glibc: 10 commits discards efa4725f6a 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 79c11d7e1c 88: onsuccess: #534: 1: Success after linux: 12 commits discards 00ee09fe65 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 3eee9430e9 86: onsuccess: #532: 1: Success after gcc: 16 commits discards bf6273d268 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 31af0ac255 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards ae3a877778 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards c8533d588d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 0c355f7876 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards a9b4161d11 80: onsuccess: #524: 1: Success after linux: 9 commits discards 2a0c2fccde 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 2ac9c75839 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 7c53fe4dc6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards a076cd77b6 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 71b317b8ee 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 7207705ac5 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 996016ba57 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 09bf924f16 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 5f25f0fc79 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 9c9679bd2c 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 6dd95eaa93 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards cbef4a3e9c 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards b35fc42541 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 050f083766 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 248c274a52 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards f44aa68960 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 0192d4bd68 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 84d587b222 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards abca1e1451 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 4949b88d22 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 8e3cf91481 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards f9939e3f5e 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards be4b70fe43 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards ffc5fbc2d7 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards d69d314ee6 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards a44562e554 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 56e48daed8 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 7ab3b411fc 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 63d389a618 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 3c2aab2933 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 4a74c73eb5 49: onsuccess: #487: 1: Success after binutils: 11 commits discards ef7c1ff324 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 76f22fbc7d 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 7e376bb4a5 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 2aff08adb0 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 1fc970dbf0 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 99cb4ed2e4 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards a4e98fc0db 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 11c178e9b2 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards a3e9f6a6b8 40: onsuccess: #476: 1: Success after linux: 69 commits discards 06b816a10a 39: onsuccess: #474: 1: Success after binutils: 8 commits discards d976841f9b 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards dcad91bac5 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 41cf9735ec 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 6998f01bc3 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 934e4c1a7e 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 2cdbe28df6 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 9eae8cc223 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards e15f78aad8 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 3e72ab1be9 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards fb6053133b 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 31991e0427 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 14914a420b 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards fe97f82950 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 5ef36060a7 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards c364621be4 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 5aa3c614cb 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards e856615b74 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards b81c379261 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 38d6e13550 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 803aa5bca7 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 61084de701 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5eddef3f42 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 13e7358cf1 16: onsuccess: 1: Successful build after binutils: 5 commits discards 438dc7e872 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3c05391a94 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cd9a171b99 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 984009b898 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8dcbdfd84a 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c11806102f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 11eff99f34 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 44fd82a0fe 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 762831da46 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8bb4daac16 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 5be3ab8829 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards d9616b420f 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cf0c5a50b3 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8f7a6aadf2 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 5a499c8464 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 43ea84f194 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e73a0773ba 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0bcd770df5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c7d8af59cb 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f45d297303 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e7ff1f24d8 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 61fc168c30 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9f41ae4b2 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ecfff1b1bb 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 80b01c6986 16: onsuccess: 1: Successful build after binutils: 5 commits new a8ef5a1865 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e079a7dd5f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32ab4e14a3 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f8b1fdd8ce 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a261c56496 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 869eabcc27 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a47ab9455c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 9ae2507e20 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 482e3a2723 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new b842647614 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 203708c421 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new f758b2deff 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new d0db820cd2 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 0fd741febe 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 4d7eb0cb87 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 1020ed3461 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 38f0dc7fbd 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 31c09daf29 34: onsuccess: #465: 1: Success after binutils: 11 commits new dbd4936695 35: onsuccess: #467: 1: Success after glibc: 2 commits new f948f5605a 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new a8f44b327a 37: onsuccess: #470: 1: Success after binutils: 3 commits new 5109ba7988 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 321c35a84b 39: onsuccess: #474: 1: Success after binutils: 8 commits new 555f8edbba 40: onsuccess: #476: 1: Success after linux: 69 commits new 8fe206ab24 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 8e4b3633b3 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 9fdf1017c4 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new f099c2658e 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new b6eaf4b4e0 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new d307f46f04 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 69946be9a9 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 5604b763b2 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 6fafa526a1 49: onsuccess: #487: 1: Success after binutils: 11 commits new 4ec30e6039 50: onsuccess: #490: 1: Success after binutils: 6 commits new 4b96e206c6 51: onsuccess: #493: 1: Success after binutils: 13 commits new 4afe283434 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new d9b7b109ca 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 1eac756881 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 6cdb308643 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 4a525aaceb 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new c5555da726 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 234f400c16 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new e769b12eb0 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 4ad5b66892 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new fe1a1efef1 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new b28f97eeb7 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 0d0c8cae42 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 2d29ac2dff 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new afdc7cc91d 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new ff72942411 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 20c68f171d 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 2e7d0c4782 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 563961ad8a 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new f964275d35 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new a6f9ba575b 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 0f01487fae 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new ce5f0acff9 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new d25318e0e1 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 5d879ce44d 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 29eb29a7fc 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 442d152c61 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new b34966c836 78: onsuccess: #522: 1: Success after binutils: 10 commits new eaa2636b57 79: onsuccess: #523: 1: Success after gcc: 25 commits new 015aad69dc 80: onsuccess: #524: 1: Success after linux: 9 commits new 0bcc4c618b 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 6a9187b0f9 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new e883786190 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 65539ba792 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 6d994ad268 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 4a2707bf8e 86: onsuccess: #532: 1: Success after gcc: 16 commits new 78f2c03d00 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 437f82ee65 88: onsuccess: #534: 1: Success after linux: 12 commits new 5c7f3a6520 89: onsuccess: #536: 1: Success after binutils: 27 commits new b9fa24c549 90: onsuccess: #538: 1: Success after glibc: 10 commits new 03ce45e511 91: onsuccess: #539: 1: Success after linux: 27 commits new 98590ddeab 92: onsuccess: #543: 1: Success after glibc: 4 commits new 2a99c811aa 93: onsuccess: #544: 1: Success after linux: 34 commits new 8da6aef608 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 9955492751 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 21d07426bb 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 7cacc67d1f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new fbafe3c97c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 81e341b379 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 5d4237c82f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 3bc3b17e95 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1cf458b911 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new d0c8eb60e3 103: onsuccess: #555: 1: Success after binutils: 4 commits new 8048fba4b5 104: onsuccess: #558: 1: Success after binutils: 3 commits new 90adc78f70 105: onsuccess: #560: 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 (9fd3a81154) \ 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 1724 -> 1892 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 50660 -> 53232 bytes 04-build_abe-gcc/console.log.xz | Bin 232076 -> 234320 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8912 -> 9004 bytes 07-build_abe-glibc/console.log.xz | Bin 235548 -> 238556 bytes 08-build_abe-gdb/console.log.xz | Bin 49892 -> 52396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3956 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2596 bytes 11-check_regression/console.log.xz | Bin 4596 -> 11916 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 10 + 11-check_regression/mail-body.txt | 44 + 11-check_regression/results.compare | 43 +- 11-check_regression/results.compare2 | 982 +++++- 11-check_regression/results.regressions | 44 + 12-update_baseline/console.log | 56 +- 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 | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 44 + sumfiles/g++.log.xz | Bin 2906292 -> 2851612 bytes sumfiles/g++.sum | 249 +- sumfiles/gcc.log.xz | Bin 2509392 -> 2530548 bytes sumfiles/gcc.sum | 5623 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 947536 -> 951992 bytes sumfiles/gfortran.sum | 77 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229136 -> 229112 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473968 -> 469300 bytes sumfiles/libstdc++.sum | 39 +- 43 files changed, 4599 insertions(+), 2735 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions