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 75990f6e0d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards ceadf5e322 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] discards d92a82e80a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards f2cae5e2ed 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] discards 6e2e1289f2 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 7de590658f 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards cf12ecb795 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 3d8fc6fc0e 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 74188ae410 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits discards 38852fe0a3 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 240c8ae01e 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards b913cc1d90 141: onsuccess: #601: 1: Success after linux: 794 commits discards 6e80fb1012 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 5ef643d5a1 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 018fc39147 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 8d632aee6a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 0bb2d30635 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 9f6507b7e7 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] discards 011cdd8326 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards dd5ea5bd7c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards 10c5ffb388 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 9e2eec6ce8 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 7e29d59b44 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] discards 0a28652a80 129: onsuccess: #588: 1: Success after linux: 4 commits discards af67213f4a 128: onsuccess: #586: 1: Success after binutils: 22 commits discards e5fcd1c6dd 127: onsuccess: #584: 1: Success after linux: 21 commits discards b57e7b078a 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 64b8eea5a1 125: onsuccess: #581: 1: Success after binutils: 4 commits discards c1b26c5084 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards e2d1520d5b 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards 700e69bb7d 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 4b38aa38ef 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 29c0e4aeae 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 55e790160c 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards 73b5b4f42a 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards baf98e5e5f 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards cfadb2489f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards e9fa345060 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards e73042595b 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards fed5b6281f 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards dcf519f078 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards c7dfdf0151 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 9571f151da 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 345e942df2 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 8031d4ee0e 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 923a91cf83 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 1da09935f5 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 3400fe05de 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 616958eb64 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 6822cd24f0 103: onsuccess: #555: 1: Success after binutils: 4 commits discards ed6f57a8a9 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards b7bab08aae 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards a4f2b72dd9 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 47d6de754a 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e12173cfcb 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 3f85d55512 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards f2fa000298 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 7515d09821 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards c4e85be98b 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 6be9939cfa 93: onsuccess: #544: 1: Success after linux: 34 commits discards 6e6b81fc22 92: onsuccess: #543: 1: Success after glibc: 4 commits discards a52d9f24cb 91: onsuccess: #539: 1: Success after linux: 27 commits discards e45698c6db 90: onsuccess: #538: 1: Success after glibc: 10 commits discards dd6ca50045 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 8771cd0c73 88: onsuccess: #534: 1: Success after linux: 12 commits discards f456f66f3a 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 7ba408135c 86: onsuccess: #532: 1: Success after gcc: 16 commits discards ddcdea4b65 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 9f67765ece 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards fc924476ca 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards dad9e39808 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 3cf0eed48f 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 5c239c5555 80: onsuccess: #524: 1: Success after linux: 9 commits discards e2c2426587 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 67b539be69 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 87cfaa54a0 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards a03ce5dedb 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards c53469cb9f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards c443fe3ee9 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards ce8b53a352 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards e9cda596f9 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 8a695f4af7 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards b4ca2d9346 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 3fe4361fda 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards bc55ae5797 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 4c28f725f8 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards f5d8aeeeb4 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 2ecf80282f 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 39166f402e 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 6a514e220b 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 7d4194322d 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 3b2b936d2b 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 88ce610b88 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 933fd205d3 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards df1ea26dfa 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 0416028021 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards f5927fc044 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards cf3ac9c7c4 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 5f3da4c16e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 95d7cb6147 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards e41536b600 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 9be6e99850 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 3c9fad84e4 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 748e22ea64 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new f1e7bd1a17 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 7045a21b2f 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new a636b25d53 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new aad024f1de 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 87fa10ecc0 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 63a48dc8a5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 76809c7c76 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 4b57d11f5d 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 77642e5888 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 630c0d6c31 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new fc40d9755e 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 45ca0c9023 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 6b7e9be1df 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 81dda27c6f 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new a0f0c0e4ed 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 957216107b 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new a71d0ce751 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 024c3f2ed3 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new b26ffc7a8f 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new b455ba58cd 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 51fdbb5be0 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 2239875e8d 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 82f6e9681c 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 6601a4a860 78: onsuccess: #522: 1: Success after binutils: 10 commits new 69d27ae38a 79: onsuccess: #523: 1: Success after gcc: 25 commits new 2545a48332 80: onsuccess: #524: 1: Success after linux: 9 commits new e51aadae87 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new a1b44c2bdb 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new a44c5970c3 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 5b12de9aab 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 3df1bc58cf 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new e8767b6748 86: onsuccess: #532: 1: Success after gcc: 16 commits new 8a6240ccde 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new bef99df10c 88: onsuccess: #534: 1: Success after linux: 12 commits new df7ee0ec7c 89: onsuccess: #536: 1: Success after binutils: 27 commits new 370b3e0d97 90: onsuccess: #538: 1: Success after glibc: 10 commits new fe82d036ab 91: onsuccess: #539: 1: Success after linux: 27 commits new 07eac36465 92: onsuccess: #543: 1: Success after glibc: 4 commits new 712fab42a3 93: onsuccess: #544: 1: Success after linux: 34 commits new 7aa691220d 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 3c4b11e158 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new b6cb089564 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 1c3c7186f0 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 52cea3c3a7 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new a9fc97236e 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 80c0a6afa0 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 697a5ea817 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 6c8440046f 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 44e68f65a7 103: onsuccess: #555: 1: Success after binutils: 4 commits new 8788247103 104: onsuccess: #558: 1: Success after binutils: 3 commits new 71a24d3423 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 3cca9b454f 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 7487da7763 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new e8e81c4393 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 4e44dca6ed 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 5227a0b49a 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 84d94c78fc 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 19bf3c5265 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 5d66971525 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 228dba85e4 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 4454a98c85 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 788a229d2a 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new af7e326243 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new bea67f3d03 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 39573f9afa 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new c02604e265 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new b7c81cf33b 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 49b65a4748 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 4287ab432a 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 0702043670 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 4727debc28 125: onsuccess: #581: 1: Success after binutils: 4 commits new 841030ca07 126: onsuccess: #582: 1: Success after gcc: 9 commits new 85c67cfb95 127: onsuccess: #584: 1: Success after linux: 21 commits new 20a95c2bb1 128: onsuccess: #586: 1: Success after binutils: 22 commits new 4c53b4c831 129: onsuccess: #588: 1: Success after linux: 4 commits new 35824d43ac 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] new 26e2b7cd7c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 933f46e173 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 5815406875 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new fd19361bf8 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new ae39505c94 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] new b7d72173e0 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 81a2eed7a3 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 5958f49fc7 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 082aa79770 139: onsuccess: #599: 1: Success after binutils: 10 commits new 54370371aa 140: onsuccess: #600: 1: Success after gcc: 23 commits new 8c88832252 141: onsuccess: #601: 1: Success after linux: 794 commits new d62d5140b8 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 83b0614e72 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new ed53a43e84 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new fae05ff272 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 54eda08dc9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f378fdf87b 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 4e0840bb61 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new ce6406432e 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new 9fa6990137 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new c70c385560 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new 37422b6859 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new ed72b526f3 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits
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 (75990f6e0d) \ 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 1788 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 53276 -> 53192 bytes 04-build_abe-gcc/console.log.xz | Bin 237196 -> 238912 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8304 -> 8360 bytes 07-build_abe-glibc/console.log.xz | Bin 238000 -> 238880 bytes 08-build_abe-gdb/console.log.xz | Bin 52228 -> 51572 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3868 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2668 bytes 11-check_regression/console.log.xz | Bin 7016 -> 6036 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 417 +-- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 + sumfiles/g++.log.xz | Bin 2912508 -> 2910740 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2588904 -> 2568916 bytes sumfiles/gcc.sum | 5028 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 946840 -> 955696 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230792 -> 229856 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 481496 -> 474832 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 2827 insertions(+), 3066 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