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 e8113a4497 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] discards 60dbb8350b 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards efb10c0b7f 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards 82348c2c86 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards c8d4b6bd76 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 7095d558cf 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits discards ce6ba7e259 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 48daffc821 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards c43bc1086c 141: onsuccess: #601: 1: Success after linux: 794 commits discards a3da827f59 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 12712261db 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 6e2e1ae422 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 8049c4e518 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 723bd8fd9e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 372235cb59 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] discards 3d8cc134a7 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 2489bcdc04 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards e45852d6c0 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 8f85e0e6bb 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 8f3d465963 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] discards a9cd56e164 129: onsuccess: #588: 1: Success after linux: 4 commits discards 600cb628f9 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 6c8a82c592 127: onsuccess: #584: 1: Success after linux: 21 commits discards 3831fde8d6 126: onsuccess: #582: 1: Success after gcc: 9 commits discards f122034f61 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 69730494f5 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 4152f261b3 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards a84433ab23 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 9fd425af60 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards eeb8c8a861 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 407a55414e 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards 98a14b7a76 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards db893a7ccb 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards 10e55a930b 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards 825fa89a90 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 0510d74ea4 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 98bcf2266a 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 85cce96ebe 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 8e2f778470 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 323f32e1e8 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 168f587b49 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards df7d77279b 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 1016513ed1 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 1fcae7af3b 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards e445c05896 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 7f11e5ff7b 104: onsuccess: #558: 1: Success after binutils: 3 commits discards ce09695004 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 7cfc689763 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 993c4abee8 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6a68cb8627 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 0eb31c3ecf 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 36bc8a15f7 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 0cc667e639 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 911991768e 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards b91247c187 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards d767e243d1 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 47a3202275 93: onsuccess: #544: 1: Success after linux: 34 commits discards 95bd54b98e 92: onsuccess: #543: 1: Success after glibc: 4 commits discards ca10af5f28 91: onsuccess: #539: 1: Success after linux: 27 commits discards c6fff334bc 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 80619cd2c0 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 038f69173c 88: onsuccess: #534: 1: Success after linux: 12 commits discards 7bc77eca80 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 8d71f1caa7 86: onsuccess: #532: 1: Success after gcc: 16 commits discards f44a37dc76 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 7e2b1c54f7 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 690baa16cc 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 351ec8df02 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards e4916e0db2 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 38110044f5 80: onsuccess: #524: 1: Success after linux: 9 commits discards fb02c293ee 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 9211cc83f5 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 17e4787f6b 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 0ec5259c1b 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 7be4f4f5ac 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards ec3c2361e0 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 1c50541712 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 5f2a3f08b4 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 9721fc3638 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 709ead1797 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 040bba5b17 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards cd764450e5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards f0eadb7f69 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards a07484a660 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 9cc5a43d07 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards e6f58e9ca6 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards d5fdde8ee2 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 40d6bf7019 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 0ab714f8e0 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards e69643925c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 3af928d0db 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 34690f4f81 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 8b1f3ec671 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards c813054929 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 6c4e674066 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards dfcaac62ce 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards b241347b8c 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 1f5d5bc8c4 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 45b45589c7 51: onsuccess: #493: 1: Success after binutils: 13 commits discards c7906b863f 50: onsuccess: #490: 1: Success after binutils: 6 commits discards ea2df8a0be 49: onsuccess: #487: 1: Success after binutils: 11 commits new c7ad91c80b 49: onsuccess: #487: 1: Success after binutils: 11 commits new b34548a42c 50: onsuccess: #490: 1: Success after binutils: 6 commits new 7d86079f99 51: onsuccess: #493: 1: Success after binutils: 13 commits new 6b7e9e2058 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new d96c16d8c9 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 0c79d29e88 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 4d5ac9a313 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new b3dde210c0 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 239913b84c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 3100de57ed 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 8f2269a78f 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 28b0b5c20d 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new b700c3c0b9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 65951037d0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new ff8ba2668a 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 7f80a8f0ee 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 4e302b799f 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new e0bd2b2069 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new a4a249b8ac 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 368c79c4cd 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 8fe297cb4d 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 1c7fdbf2a8 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new dcb6439487 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new d06b0e95bb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 92cd50693d 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 96f9ad7fbb 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new c0877f7664 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new f0cd79db97 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new eef6914ebe 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new cc36b4fb6c 78: onsuccess: #522: 1: Success after binutils: 10 commits new 261f8c12a5 79: onsuccess: #523: 1: Success after gcc: 25 commits new 87720e512e 80: onsuccess: #524: 1: Success after linux: 9 commits new 68f2da5a26 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new b5fcbd0e18 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new c4323f0f2c 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new a99cd38234 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new c8defaf585 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 2a15a14285 86: onsuccess: #532: 1: Success after gcc: 16 commits new 683a51d5b1 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new fc4c3413b5 88: onsuccess: #534: 1: Success after linux: 12 commits new 16e2fe2fd7 89: onsuccess: #536: 1: Success after binutils: 27 commits new cf7b3d4b55 90: onsuccess: #538: 1: Success after glibc: 10 commits new 1814d1a434 91: onsuccess: #539: 1: Success after linux: 27 commits new 53bc015d2a 92: onsuccess: #543: 1: Success after glibc: 4 commits new da7d602d4e 93: onsuccess: #544: 1: Success after linux: 34 commits new d1e3e76a0c 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 90622ef2a5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 5892bb7ec2 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new b21bf013ce 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 1eeed95f12 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new f8584cb1ee 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new b12b1f3541 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 3402a7ba86 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 2877addd01 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 671ff72468 103: onsuccess: #555: 1: Success after binutils: 4 commits new 45c43e6a9d 104: onsuccess: #558: 1: Success after binutils: 3 commits new aeae10b08b 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new e22253b3f2 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new d1cd851221 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new cbc881bae9 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 07a337bc3c 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 354351685f 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new fead4c7820 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 6a042af0a9 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 725d0f7885 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 1a7b5a7f2e 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new bac4badc9a 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 2c26eac7c2 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new 7052039b64 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new 707dbf9baf 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 79ca7cafb2 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new 679f18ce63 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 05cbcdd185 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 59ce75865e 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new d3f762e93b 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 80141fd778 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new b52f0913c5 125: onsuccess: #581: 1: Success after binutils: 4 commits new b26a116006 126: onsuccess: #582: 1: Success after gcc: 9 commits new d256aa3cd6 127: onsuccess: #584: 1: Success after linux: 21 commits new fdcabe2a6c 128: onsuccess: #586: 1: Success after binutils: 22 commits new 635e76fa1b 129: onsuccess: #588: 1: Success after linux: 4 commits new 5e157d5d40 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] new 6206668a7e 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new f1543ca674 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new da8500a29f 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new a880f4b1b8 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 1561f988ea 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] new 8ae4b77375 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new f881f7b186 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 8520321086 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 99de28824d 139: onsuccess: #599: 1: Success after binutils: 10 commits new 6fe9f043ad 140: onsuccess: #600: 1: Success after gcc: 23 commits new 7f9cc1a13b 141: onsuccess: #601: 1: Success after linux: 794 commits new 4496187d2e 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 0d46f99c61 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 25608baf79 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new 74d05d6bd1 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 0c67481847 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 215f03f3b7 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 0f4ed0d082 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 092e76c1f5 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new 4f2d4b0bb8 150: onsuccess: #610: 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 (e8113a4497) \ 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 1756 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52572 -> 53628 bytes 04-build_abe-gcc/console.log.xz | Bin 239292 -> 239524 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8752 -> 8708 bytes 07-build_abe-glibc/console.log.xz | Bin 236744 -> 237004 bytes 08-build_abe-gdb/console.log.xz | Bin 51712 -> 52140 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3824 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2692 bytes 11-check_regression/console.log.xz | Bin 7264 -> 5788 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 159 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 36 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 - sumfiles/g++.log.xz | Bin 2941300 -> 2942956 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 2573948 -> 2564172 bytes sumfiles/gcc.sum | 4460 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 951168 -> 953840 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229420 -> 230528 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 475484 -> 481440 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2433 insertions(+), 2642 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