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 46cb8b9b94 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards bd074ed87f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards ac5354e1b6 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards d15e8f0564 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards cbc1d6fb5a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 789b6dfec8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 81c565b5a3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards a0861c51f8 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 117f77c352 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 328769d724 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 4861e4d1ac 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a22ecc3282 94: onsuccess: #832: 1: Success after binutils: 5 commits discards e9ffac24fb 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 3906bc5855 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards e973a5fca5 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 4ac72f0099 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards e985b627c9 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 36311a1615 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards b55ff47f14 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 7e50426e6f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 4946d4dc5d 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 6f0d71d66a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 35016909d2 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 5cde51b5a1 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b692cc35c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards f4351516e4 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6fa7d70306 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards a5dd83e144 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d0da0484be 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards f3ecb8e4b1 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d4c5c88382 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards d1e3a9ad05 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 8f5e685844 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 2c40b3b492 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 340c8b0a1c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 1fc4e817b5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 08b1f2050e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards a803ef75fa 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 46a3f9888a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 5cf243d24c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 7289c94ab9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards f8e99eeb6e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 2efc6be314 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 640afca595 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 168e44ddcf 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards f1f1c90657 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards ba71bef5c4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards fbc1b9fa58 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 4928255d42 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 5eb071839e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards ae2ccff6a6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 6d0ca6298a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 0d3ce97b4d 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards a1dad78169 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards f336f4143f 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards ed031165e0 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 38bdcdde23 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 8ea08df888 48: onsuccess: #782: 1: Success after binutils: 8 commits discards b50d78121e 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 8c1c4432bf 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 436fb96d13 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards a77661accf 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 7592e9bb3c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 525a976005 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 7936c94d31 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 221646095f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards fb20d7a01a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 7654c41641 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 3e29644a1d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 3e5ab1f8b9 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 9bb03ceb95 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards e3a6b4f9a9 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 5cd2b744df 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards e7fd167d69 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards f8cbcc1706 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards af14e3c26d 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 7d3fad6525 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards bbd7e4c47a 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards d98c8be98a 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 10ba189b9b 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards decd5c14f5 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards ad12efa7cd 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 042feadc95 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 964ea31705 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 3466717e6c 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 73b0b33d61 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0c870a497 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5696d461cb 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ec5af3d46 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8717e3e46a 16: onsuccess: 1: Successful build after binutils: 4 commits discards d738b80ea3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 00e1fdd2df 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 78069d98af 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ffce259b31 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 277d001666 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32a325528a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 99d64956e5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8069af9b6b 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ac370e4878 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards ad79c8713e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards f1d9e40543 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 66041e9ccf 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 426f284298 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bcefa11c9a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 997b1769f3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 88373bc4e0 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 80b837fe20 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 787b401272 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cbead31d5c 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5f10c808b 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b7e6b102e4 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7bd325ffb3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f9dd591e9 16: onsuccess: 1: Successful build after binutils: 4 commits new c02f0af1ed 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 57e89c12c7 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c24332671a 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab1b1169d7 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1b1f467c75 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a19142a764 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5318691b6a 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 818dbbe132 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 1593976da6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new ea44ae79cb 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new c0e00cb5b1 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 34570243a8 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new da4fc7ec50 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 9f5a508e68 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 07788853b2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 619a1952ac 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 0a17ac557a 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 4cf6df99f9 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new a1ae4a91c2 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 3b68ee7c32 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 24566a6fbb 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 2942703694 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new d1eddcbe29 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 0e5dc1850d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new a90fe51e6d 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 1f81b725b0 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 5965b5ef36 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new c95a710796 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 0f7383c022 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 1b4494350e 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new ac80051f72 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new f73b6b005c 48: onsuccess: #782: 1: Success after binutils: 8 commits new 597054fb9c 49: onsuccess: #785: 1: Success after binutils: 12 commits new a178a380ba 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new b1f649cdfd 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new d625be300b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 6c53f499e5 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 0636f85f34 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 10e6f9e25f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 00b546c8ee 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 4462cd6acd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new a9e9a25829 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 08cc175a27 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new b689522dd4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new eedda08df3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 7fb87c3933 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new e58019d609 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new ffa60f0c1e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 5692507d1b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new d942a3b516 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 2067b6b1bb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new a6fa0e0169 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 6d0a0f8c89 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 030ef561a0 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 62c58fb369 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 7252f0fda2 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 8eb4ceec8e 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 96e6d1059f 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 2bb2b8e446 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 91359aaabf 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 2874ea1d28 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 1fcf7aaf4b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 62ff6520e5 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 59a99321ba 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 063dc393f7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new f197ebb1ac 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 5e1032d748 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 3dee8464b3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 02e17fed94 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 2fd0640ec0 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 250b5b5a50 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 956fa97044 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 02b87eb8cd 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 1191885369 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 4bfd152dd0 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 1665534e10 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 985c54272f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new eb7f3e3017 94: onsuccess: #832: 1: Success after binutils: 5 commits new 58846d51db 95: onsuccess: #835: 1: Success after binutils: 3 commits new fbc21fed1c 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 71ba76e4a0 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 9185b8fd5d 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 034ed959d7 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 8da56d63ff 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 2bcab5b6ba 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new b18f13b6ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new cbaa0df499 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 627e4e8e97 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 0a542f16c8 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 3822c46070 106: onsuccess: #847: 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 (46cb8b9b94) \ 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 1684 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39236 -> 39272 bytes 04-build_abe-gcc/console.log.xz | Bin 214764 -> 213312 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 9548 bytes 07-build_abe-glibc/console.log.xz | Bin 243512 -> 243792 bytes 08-build_abe-gdb/console.log.xz | Bin 38888 -> 38800 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2724 -> 2572 bytes 11-check_regression/console.log.xz | Bin 7208 -> 6456 bytes 11-check_regression/mail-body.txt | 40 - 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 196 +- 12-update_baseline/console.log | 58 +- 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 | 42 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.xz | Bin 3720096 -> 3724504 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3272888 -> 3310512 bytes sumfiles/gcc.sum | 5060 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1083272 -> 1078664 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230664 -> 230840 bytes sumfiles/libgomp.sum | 22 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452588 -> 450496 bytes sumfiles/libstdc++.sum | 14 +- 38 files changed, 2740 insertions(+), 2962 deletions(-)