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 1abaf1f4632 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards e8d686c50f9 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 79e88deac68 118: onsuccess: #863: 1: Success after linux: 12 commits discards 1ad647f1b30 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 5e2ebb2956d 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards e0908f6dffc 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards abe04a87932 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 6ed424e493c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 23006f4737a 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 365be5a5132 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 944ca9cd947 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 07261adb25c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 1b95615456f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 1162873ea48 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 2d37c00d8e2 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 2285d27f42a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 89a0c228f2f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 0fb01b784ec 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards ccf14b94e40 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 1324b914218 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 1ebe264f89d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards fab35a06a69 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 1b885cab7b2 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 38074d9c0a4 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards c01db81b2d6 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 985ad4af17a 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b22f08b79f0 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b1d4bd1bf3f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards e8ead4039e9 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 6fba8420a73 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 59efb65f650 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 7c0131405d5 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 79a343a6d6c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 699fb7d2045 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 9a47f79d457 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 8684de813b9 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 0371d8c6651 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards f6d65243974 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 56460e77686 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 085a0b46639 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards de340c48516 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards f7abd138dfb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 294c6c26d5f 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards f9c2f5599bc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 6d9f89dda3a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 30afc751247 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards a5a476f9f5b 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 570a1e727a5 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards d5fb5162d92 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards adf534a1e49 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 58fd80e3607 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards c45805643a2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards b43bcc36078 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards a682181f569 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 03ce2dc18b5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 869f9e72a1f 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards e2c30ac73cd 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 6435228b6bd 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 0d4668028f2 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c373f914153 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 06aac5daacb 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 4a7df064418 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 84b64b1df0d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards af8481ad9dd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 4fb9c625830 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 9521ca64ea6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 618efc85143 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards b062579a9c2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards e9b9cc520a4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards a0e4cec84ee 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards ef9053f764e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 4df711824a0 49: onsuccess: #785: 1: Success after binutils: 12 commits discards b493f7dde94 48: onsuccess: #782: 1: Success after binutils: 8 commits discards cf8cf5c8166 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards f333971e78f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 8f3168664ba 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards c4f8eee90f9 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 80e8cbf84d3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 03d43ce35cd 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 9f30efddfa2 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards d91f98d578a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards aa925c6c795 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 17a196ded7f 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards b9eca511e02 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards a4e28e71c2b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 121714b476c 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 68dd2b335f8 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards ae38e8f1814 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 6fa24e3dfd6 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 5e00c5b611e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 7e232212853 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards fe92e3b2747 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards d1406ec4695 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 894695feb67 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 5f570a5fdde 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 0dada265ce2 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards e1bfb94a87c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 9de5833f9ed 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 46dde8ebe90 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 52eac4f18ff 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c32533c80b5 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 776343b91e4 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6e5c310f839 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f239de4a29a 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 18c1b76b0eb 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 1f437a786b0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 18ef88a2997 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 26f9a339173 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 359a4253e35 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new d0f3bd9e55d 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 8d90163205e 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 40b3948168b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 0814acfbb26 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 6edeccbec08 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 30d28ea9998 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 45290253906 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new c068f9ffd1e 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 352da7305fb 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 14bdfe8c57e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new fcd868f4a22 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new ad66afbb04e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new b1456d77fa1 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 0064ef484ba 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new afd9d778f2e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new a382d7ba1ac 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 851538ae099 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 9148f6776f3 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new c3e48d64dd9 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 623f6fffd32 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new c4deaa5671f 48: onsuccess: #782: 1: Success after binutils: 8 commits new 755f69ad2ba 49: onsuccess: #785: 1: Success after binutils: 12 commits new 1a329a896d3 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 3acd5369329 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new d0dc6a5f499 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new f5b68dfe22b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new a05f8e40ca0 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new b27108279d3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 0d04972b3de 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new bf302f382e9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 0e2f011b1df 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new db16fdc5df7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 5da817e231d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new b4cb9742696 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 101d34c5208 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 01caf8b0701 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 85b5e42b8f9 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 9724e52a190 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 146cb134aa5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 6cb1780ebe9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 0eaf5bad93f 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new cdc41291707 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 89a5c0738b3 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new ac6930b5466 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 94d75eb4d63 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new a53d1fe6c5a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new c1ca7411af5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 75102afe700 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new d6a84952af9 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new bd106f71e95 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 9e9f635d719 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 334adb95c18 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 99e39120a9c 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 13856fffc15 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 38fcd727b0c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 1dbcb05d1e0 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new feab18af51e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 84cecdc46a0 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new a52c3c8e038 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 8876df3b2dd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 55a0f0ba1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new fc836ea4ecb 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new be62ad06e56 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 3ff8b02aa49 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 3c708a5cb13 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 7aaade82c24 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new b4f5b9a7a35 94: onsuccess: #832: 1: Success after binutils: 5 commits new e7c009c91d5 95: onsuccess: #835: 1: Success after binutils: 3 commits new cc3d3f57c1a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 7cfbb364a21 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new bb70f71dc60 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 8fa6ad95962 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 9abac687911 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new ecc98a64c88 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 8577c385c2d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new cd82797f6a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 395fb5addf4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 059457bacdd 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 6d7e069791a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new aee5cffd05a 107: onsuccess: #849: 1: Success after binutils: 5 commits new d455e0fc6fa 108: onsuccess: #850: 1: Success after gcc: 2 commits new 84ee35915ee 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 16e733e634c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 742a68a918e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 680343463d6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 3a1cdf1a147 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new dbabd8cc56f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 08f94db2ecb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 795e13375ab 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 75ae16f679b 117: onsuccess: #861: 1: Success after binutils: 18 commits new d1edaaeb629 118: onsuccess: #863: 1: Success after linux: 12 commits new 18a92f6494b 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new ac53ca3583f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new d04a13ae207 121: onsuccess: #866: 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 (1abaf1f4632) \ 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 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 39752 -> 39676 bytes 04-build_abe-gcc/console.log.xz | Bin 216032 -> 212676 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 244392 -> 243216 bytes 08-build_abe-gdb/console.log.xz | Bin 39232 -> 39004 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2708 bytes 11-check_regression/console.log.xz | Bin 7328 -> 7728 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 | 25 +- 11-check_regression/results.compare2 | 278 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 38 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 27 - sumfiles/g++.log.xz | Bin 3750376 -> 3728288 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3291704 -> 3303216 bytes sumfiles/gcc.sum | 5483 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1085088 -> 1075860 bytes sumfiles/gfortran.sum | 118 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231448 -> 231420 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453348 -> 450116 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 3155 insertions(+), 3125 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