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-aarch64 in repository toolchain/ci/base-artifacts.
discards 4852c0a0fb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 87ef2232e2 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards f371bb21ef 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 57777092c2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 5fb6a420fa 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 0b4f273127 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 5e1abaed8d 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards e8fe6b5d5e 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 67c3444a38 128: onsuccess: #876: 1: Success after binutils: 12 commits discards c8bc9aece5 127: onsuccess: #874: 1: Success after linux: 219 commits discards 4e9a0b5840 126: onsuccess: #873: 1: Success after glibc: 2 commits discards dbb15ba38b 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 8a4f559ceb 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards a82635fc5a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 85faa99a8a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards e185a41fe1 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 5241daf318 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 6a1d95fef5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards d087899ee4 118: onsuccess: #863: 1: Success after linux: 12 commits discards 2a0ed6604d 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 0483d68c65 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 113421da88 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 12ea372f7a 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 646ffb5450 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards d94259804d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 22351ffce7 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 80a464e9e6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards ab33270e1d 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards c5024ed3bc 108: onsuccess: #850: 1: Success after gcc: 2 commits discards af3dd8c212 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 8d76471cb6 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 4d76732893 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards eebc045425 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3cff428d6f 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards b3d01322b9 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 685365b17a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 2239cdff72 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards b1af2a728b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 0aaba906f3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 210b79e6bf 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 6cb131b129 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 0c0d83c957 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 2295a145e0 94: onsuccess: #832: 1: Success after binutils: 5 commits discards d1fd89573a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 6f371a0b3a 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards c0aaa7acb9 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards a56bd16b05 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 0b9ed8be8c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards e60a258ee3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 009f0b5bc5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 4c024cf639 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 1329f0df90 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards deb692688b 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards c8761d894b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards cbc695fb94 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards ff39528a46 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 9f44a2f7d1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards cca953d51a 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 06d39d87a1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d95533b0d8 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards f4f14675ba 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards c36f9d3fa1 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 80e13d6ae4 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards a6ccff0629 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 53a1712eb7 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 0ae719379a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 81afde358b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards bd02c699c2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards a9a41b5c1d 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 49db19ae1f 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards e204d8950f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards a0994fdd01 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards ea737a72bf 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 5cc028fc8c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 4e010a4c83 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 8f03bff3cd 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 6e91c01e67 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards ae39eb0745 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards c68f5c3ae6 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards aa4891fbab 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards db3c0d2d88 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards ee0e25efea 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 4ddb3725d2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 892eb16b8a 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 7f49cc1f8b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 23195152e8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards b8edd3a008 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards cdabf65332 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f15b0ddf49 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 2adac321a2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 86bcea1139 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 402fb35817 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 08c116273c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 0a9686de4b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 4ba75cecb4 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards ba5420889b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards bdc9fb4a3b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 409ff4e360 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 6a5db62df2 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards fb7ba70905 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 6c3dceee51 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new b2a82d7274 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 450c0edf51 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new fc018158a1 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new f5f059dee8 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 5a91d81e1a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new faf2445595 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 63a60e6ed4 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new b0990e1abd 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 66dce90bb2 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 0887c154dd 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 2c64400b8c 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new b533b2be25 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 46d42b2513 48: onsuccess: #782: 1: Success after binutils: 8 commits new e8a45235f0 49: onsuccess: #785: 1: Success after binutils: 12 commits new cc6ff012bc 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new cc4cc49f26 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 2383615453 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 339aad0822 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 7fa13394a6 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 26960cb92d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new d04ea1e255 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 7d5be59612 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new f736cc80db 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 786419d3ac 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a457d7dbc8 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 4c5ffde082 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 1c1ffc22f3 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 451843154e 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 4d20edf71a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 0278e06534 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 3316118a4e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8cf165e250 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 6d687b82a7 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 294a657991 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new cda0113100 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 44850dc4b6 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 95ae947f3a 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 6a169c8618 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 81a835c689 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1e42061b4c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new e58861795e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 742652f122 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new afee2272fb 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 0da3c41c29 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 9f188602d7 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 30a50e1a23 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 2b683515a1 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 7b76bc79b1 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new d631c0c4f3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 93c7aa3ae4 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new cba6617eca 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new c49c493174 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new b9e3671c17 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 09b90998d6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0d871eccdf 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 4d223d14b0 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5910570b0a 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e68cc41584 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 466fe9801f 94: onsuccess: #832: 1: Success after binutils: 5 commits new dd42f30a73 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7f966a39ad 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 038edeaa4d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new fae9eacb89 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new f8ac6b7589 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 5ed5d7c9cf 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new adf103462d 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new bc3640df7d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 33704110f7 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 158b403fcf 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new ed1646d920 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 348e0ef1c8 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new ee121f1c9b 107: onsuccess: #849: 1: Success after binutils: 5 commits new eb494cc0a8 108: onsuccess: #850: 1: Success after gcc: 2 commits new 1e4f2c2d55 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 96a3222275 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 37712a1878 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 81fd4ab698 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new e52d0520dc 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new b1fbd2520c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new cc0f7288f6 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new f90094b130 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 7f2ea69e41 117: onsuccess: #861: 1: Success after binutils: 18 commits new 9a249217a7 118: onsuccess: #863: 1: Success after linux: 12 commits new 3300d4ebb5 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 94408cd458 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 0fedcfa10f 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 5ee57618bb 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new b60ed21bf4 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new c8cc98f1ca 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new ce5cc9ad37 125: onsuccess: #871: 1: Success after binutils: 26 commits new b9af00c977 126: onsuccess: #873: 1: Success after glibc: 2 commits new c8b025f052 127: onsuccess: #874: 1: Success after linux: 219 commits new 844f0d5810 128: onsuccess: #876: 1: Success after binutils: 12 commits new 2d904f38c1 129: onsuccess: #878: 1: Success after linux: 3008 commits new a2f16b3463 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new eece69599b 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 75d047485a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 91c6e95618 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new e14266a229 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 48924a518c 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 628ac87973 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new e8f81d1be0 137: onsuccess: #886: 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 (4852c0a0fb) \ 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 1768 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39872 -> 39936 bytes 04-build_abe-gcc/console.log.xz | Bin 215640 -> 215660 bytes 06-build_abe-linux/console.log.xz | Bin 8516 -> 8828 bytes 07-build_abe-glibc/console.log.xz | Bin 245640 -> 245476 bytes 08-build_abe-gdb/console.log.xz | Bin 39428 -> 39272 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3288 -> 2904 bytes 11-check_regression/console.log.xz | Bin 6788 -> 7200 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 | 10 +- 11-check_regression/results.compare2 | 142 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 62 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 27 + sumfiles/g++.log.xz | Bin 3761124 -> 3741064 bytes sumfiles/g++.sum | 83 +- sumfiles/gcc.log.xz | Bin 3311640 -> 3322332 bytes sumfiles/gcc.sum | 4732 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1078032 -> 1083348 bytes sumfiles/gfortran.sum | 64 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233408 -> 233248 bytes sumfiles/libgomp.sum | 6 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 450176 -> 453984 bytes sumfiles/libstdc++.sum | 4 +- 42 files changed, 2741 insertions(+), 2536 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