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 b63a3b3360e 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 98cc57cd9c0 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 36ca3dfbe3d 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards a0af8d81a1b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 71a87bc82b1 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 7572a51d1d0 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 2ea43c1d010 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 7b054ea04c8 107: onsuccess: #849: 1: Success after binutils: 5 commits discards cbacae92809 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 8f06d55a9d6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 2a7c1245ff8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 2b3a48b5098 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards c6798c2192e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards a26899f7d6e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 91567e7972e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 2f96a9a03c3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 20cd329f146 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 4dc1621e2c9 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards d027896f2f1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards db36c72cff4 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f3fa1b38c05 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 92bb328b4c5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards d60db611484 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 65c150ee69c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 8ff6de6b88b 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 9b3f71de24b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 061a02eb474 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 672cfd0a830 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 28b3434932b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards aba16e62cef 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 7505a55e63f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 296791af455 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 00a5fd8fbde 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 0ac6b561627 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards b9c0196b6e1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 486f93017ad 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards d688db2bdbd 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards dcc6657bc17 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 1f5fa162150 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 537d76c01a8 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 31074a04498 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 2f0a3b84860 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 67f4713483e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 8ee72e80c5e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards eaf9845afa6 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards f7a8a05e17a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 7f13056d8e9 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 00e49b69ef8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 5bb925b9c3c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 41705b0a9fd 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 4cb24f460c9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 940eb0216cf 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 7d99b927e73 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c6f12f6db2b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards ebb0f78c985 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 2e7fda5e00b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 4d10d3d1b1b 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards b72e8e455e2 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards d292a1ca4ca 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 51ffe1af45b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 699357f77e7 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards d9f6215df13 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 0bbc244e290 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 6d9685e3065 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 0c7c072d40e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards a82a59f8062 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 2d3340dd2be 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 774b7e23dc8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards f8c3b814a05 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 05bb1e94c42 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 210627e9a24 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 41b870f7f40 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards a11e5f0f836 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 6b9311f974e 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards bbf61966ad2 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards bb4f8653718 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 86192a74d11 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards d66e58d030d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 1d094f8b2af 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0c091c80c0a 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards a748113b361 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards ae037d49a03 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 7c127f1cc5b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards e8746e57edc 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards c02cb654980 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards c15deca5b6e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 53ba6ab2d1c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 1345927d62e 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 17aaa4f16f1 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 2b8d4deffcd 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards c4e8d0ca025 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 67508e1f2c1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards cbc8dadb101 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 626a0fec65a 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0a5996f9f18 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8aad06f750d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ed7262575c6 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f44f19d094d 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 91a484dee8e 16: onsuccess: 1: Successful build after binutils: 4 commits discards d62144261d4 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 64f8e7b4147 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 44a95345dff 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d98ac7b5b81 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 732b8114e92 16: onsuccess: 1: Successful build after binutils: 4 commits new 8c23f9840b0 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 91b564c964a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d779adef483 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6dc9259a13e 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new fd444438d64 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 8588424e3d0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d02970d7f9d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 90489edcc1e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 0e4daeb225a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 8e2b95a2ab7 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 46b144f2abf 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 5f091743054 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new cebf8397443 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new e1486c3c091 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new cdbe79ed055 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 915dc99bb51 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new d526c6a3114 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 1c5eee00c4e 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 283c5537bf1 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new f7df3f14c8b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new bd6c4e41403 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 3be0a957867 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new d03968308cb 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 1b794365c6d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 858ee4ab849 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 0e9cbdc3fc8 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 42a8986985f 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new e7c3358664a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 4144f4318db 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new d696b70daed 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new c83b0be18e2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 64796ed644e 48: onsuccess: #782: 1: Success after binutils: 8 commits new 03348761c2f 49: onsuccess: #785: 1: Success after binutils: 12 commits new 3446ca76938 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new fe799104474 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new b0925549518 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 13622d34241 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new a55ec0eea54 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new b7adfecf8a5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 6396ed53bfc 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 6c46a22f73c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 5313151b028 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new f4c912c12f7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 693f81b0295 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 8dac2e6d07d 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new e579b94f960 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 2efa6cd1999 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 14264ccda23 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new b3a5b3583e3 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 60a86100e98 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 9a11d5b8b68 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new c464205e727 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new a564f324361 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new b56de458998 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new f7de8b9e053 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new fa1362fa339 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 11e6d81d2be 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 596091df02a 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 641aa0620c2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new c671bf2d9b4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new f7129520eeb 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 0ce889acbff 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 8ecca586e3c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new d43364c8e2b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 101cd347570 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 7ff5b5fc70e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 713363f5a5a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new ebb7c076730 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 7d1ec89079f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 60b9e55573f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 1f5fe0a2c86 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 7cf37fc1159 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 0c505f461a6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 8bc3b163e7f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new fb017fed64a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new d643ffbb0b2 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 7338bee3d02 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 9721b2a0937 94: onsuccess: #832: 1: Success after binutils: 5 commits new 5167e2948b9 95: onsuccess: #835: 1: Success after binutils: 3 commits new e7e17115d0e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 7dfe958af2b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new be4228f6dbd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new ce983730a19 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new cd0466b3775 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 1f115a16f52 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new fe9cdd413ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 6a616932d16 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new f6bbb4f12f0 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new d4efb85deae 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 25dc23d4f7d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 89a121cc995 107: onsuccess: #849: 1: Success after binutils: 5 commits new 877c8890f73 108: onsuccess: #850: 1: Success after gcc: 2 commits new c914e298c28 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 4886d62146e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 6231c960ef5 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new ff7cdfc7ff2 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new a1a9123d644 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 659901d58c2 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 553897ab6da 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...]

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 (b63a3b3360e) \ 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 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39084 -> 39320 bytes 04-build_abe-gcc/console.log.xz | Bin 214544 -> 213908 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 243288 -> 244744 bytes 08-build_abe-gdb/console.log.xz | Bin 38824 -> 39100 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3848 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2596 -> 3024 bytes 11-check_regression/console.log.xz | Bin 7792 -> 7580 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 218 +- 11-check_regression/results.regressions | 42 - 12-update_baseline/console.log | 46 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 42 - sumfiles/g++.log.xz | Bin 3748248 -> 3739640 bytes sumfiles/g++.sum | 153 +- sumfiles/gcc.log.xz | Bin 3297028 -> 3295760 bytes sumfiles/gcc.sum | 4751 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1084188 -> 1078404 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231112 -> 230948 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453260 -> 451980 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2700 insertions(+), 2877 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