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 4e17ac0fce 108: onsuccess: #850: 1: Success after gcc: 2 commits discards c7e05bb0e6 107: onsuccess: #849: 1: Success after binutils: 5 commits discards e21f8e63ca 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 2c998cb13e 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards ebbb2a7fb5 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 2fdfedae54 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards d4b91caa07 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards d305f5e1c0 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 5ea40677fc 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 833e8a3d2f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 1fd3816b1a 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 874dc3caf5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 9181fd8775 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards aafcb32cf8 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 6a132ebdfa 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 4ed021bb58 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 84623a23b2 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 082dc9645e 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards dd6ded46a2 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 941288a17a 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 875e447e97 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards bf453827b2 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 8bc8954408 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 3a6b990f29 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 286d62a523 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 47d1852739 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 8b315e9784 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 7b18913d9f 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 6e87bd7e7f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 9bb6505c7b 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 2a24df2fa7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 957ad5804b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 3c9f453ea3 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards c0c3e219f5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 33129cd52a 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards c8f4f54a54 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 2efa7eb87d 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 5ee9eccebc 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 45df6a7087 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 354402f29c 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards dd5a9234bd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards d9fc3e062a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 2285a2e267 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 20de01a84c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 31d396f113 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards ef470634f5 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 3c343725c7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 1e4437852f 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 98b7c36dfb 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 310052cc9e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards fa526c2e57 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards c4b1af5743 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 391f1ef152 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 0f7e0efbf3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards b011234662 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 12b82c2da8 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards f979158876 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 786b2e4ffc 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 8c5b3c242d 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards ec635d925b 49: onsuccess: #785: 1: Success after binutils: 12 commits discards e0c5970f20 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 7bc310344f 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 6b2854a958 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 5cdc78587d 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 9a96d14bd5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 2f2e9d8d39 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards b8893843b9 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 256ef00856 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards de93a5c4ac 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards edf5ff1073 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards d9541c070e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 84edb3294b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 4e88d84acd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards fc113d1c8e 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 4daac0136f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards e63028f2cf 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 902a564de4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 12ebe01833 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards f59dba30df 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards adc976bd4f 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 806282dcb3 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 0f659fc0c4 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 13b8c2916f 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 6a805d47e0 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards ffb41512b0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards e2d8a96509 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d9932a60ae 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards ee4ebf2a2f 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fa31854a6b 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f817c19e26 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4aa3ae72a6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 820b4f7f10 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5888679add 16: onsuccess: 1: Successful build after binutils: 4 commits discards b7df4ab7b2 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5847d5ad00 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 529ff91d92 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b3e3bf34d8 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 44871e03d6 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0bfacbedb5 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7e6b89afb7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5cb5bed021 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 18504445f4 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9abda65c52 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5143a2a689 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fdec3a6d01 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0bd16f984 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 394776522a 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ddf97679b3 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 620c4d6a2b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 820bbe8ddd 16: onsuccess: 1: Successful build after binutils: 4 commits new cce2451f88 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a91e1058f2 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fe5cad9c36 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b45ad2460d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 01200fe535 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f107215244 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e614e29735 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 39d230cb7d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 65e1bbb318 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 62e303825e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new ff794f2d9c 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 82d1259f59 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new b1612b203b 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 904c08e992 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 9f9ae1abbd 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 5265dd40ab 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new a2300543c3 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new ed7cb1324c 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 4c5bb5c220 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 86a29fcbbf 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new f242f82f0b 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 383986abf6 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 97c5c1cf15 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 1c4384b4bf 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new e012d4f10b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new ffcea228cb 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new e486d6bea1 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 89cfd9f790 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new c02992dbef 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 7d750e9e21 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new dba6ada688 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 1e33d7214d 48: onsuccess: #782: 1: Success after binutils: 8 commits new b5a8378208 49: onsuccess: #785: 1: Success after binutils: 12 commits new 34f50a5183 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 128532cc5c 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 08f4766a55 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new f39e4c2405 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 34c1548fee 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 080e47f98c 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 3d9d71971c 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new f3aa878c8d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 0cfabf688e 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 190dc613a4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 8522ed451c 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 2ac6f3f6db 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 9ebc974652 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new b55537740e 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 007ec65610 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new fbec24b720 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 28ffaa3340 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8a37ed77b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 10a3aacf15 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 1e0d6d41a8 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 3125db3119 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 452abe9979 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new f1f7f89f05 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 86960f2c74 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 5a025c43e8 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new fa1e3801d1 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 4aad54a61a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 9822481dd7 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 89282f50b3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new b9feeaf1a3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 9a42989ceb 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 52356fedf2 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 3b11b0d21e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new a870be6ae6 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new eede216609 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new a9e9467731 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 56ac5f1fad 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 0c18f91019 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new e3690ed1d4 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 75ed4e89e4 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 64d7ac0ed0 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 5129a46934 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new fe29028eff 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 2248718406 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new f92daecb5a 94: onsuccess: #832: 1: Success after binutils: 5 commits new 5027b91cfc 95: onsuccess: #835: 1: Success after binutils: 3 commits new 2c4aa0cf99 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new b2197af255 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new d23eb078d3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ee24fa3f6c 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new e3e61465cd 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 5d9dc4e6bd 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 9a9565e019 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 2d8d0c6982 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new d61cb3aca2 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new eabf4df1a2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 8bffafecd1 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new db20638946 107: onsuccess: #849: 1: Success after binutils: 5 commits new bcd6aa9016 108: onsuccess: #850: 1: Success after gcc: 2 commits new 9abf1a930f 109: onsuccess: #852: 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 (4e17ac0fce) \ 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 1692 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 40160 -> 39900 bytes 04-build_abe-gcc/console.log.xz | Bin 213568 -> 213668 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9688 -> 9272 bytes 07-build_abe-glibc/console.log.xz | Bin 244176 -> 243764 bytes 08-build_abe-gdb/console.log.xz | Bin 38940 -> 39584 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3856 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2384 -> 2432 bytes 11-check_regression/console.log.xz | Bin 5320 -> 5836 bytes 11-check_regression/mail-body.txt | 27 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 64 +- 12-update_baseline/console.log | 46 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3747608 -> 3753052 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3324888 -> 3315624 bytes sumfiles/gcc.sum | 4848 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1068488 -> 1082516 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231884 -> 231788 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 458664 -> 452336 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 2591 insertions(+), 2694 deletions(-)