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 601859b8fe1 118: onsuccess: #863: 1: Success after linux: 12 commits discards 73440ebe65c 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 5b10528008a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 929df00bddd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards b62acf004b9 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards fe0eb75b840 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 1c02474b882 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 2d076fe955b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards ddc0fdb09fc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 0e8b39713b5 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 0a16ed0b39a 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 81baec4ddaa 107: onsuccess: #849: 1: Success after binutils: 5 commits discards a59bf233c0d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 96515d78867 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards a11df02b07f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 4faa3732557 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 5b781d39610 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 4b59229d0b6 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 823db54164e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards aebdb5653e9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 7b1998b8ef1 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 8c5cf587ae1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 848d8f79d16 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 1f4fc65f880 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 7ca4540a5bf 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b95bbd73241 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 4b6fbd169c1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards ab8af324e19 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 472a5aa8cae 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e99eafef1fc 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 8482fd7e200 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 04ca838db54 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 8e0fa1a7489 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 162214917b8 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 4466911cd13 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 48cf7eecd30 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards b2e829280d0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards f023dc51bb8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards a9713876b8e 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 91105fb6f37 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 00d2a3c29d7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards e758b3f2407 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards d6eaf91671e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 6ebb744f0ec 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 7e632a3c52d 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards bade4d706c6 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 54c75968771 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards b3b869b1b2c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards fd9b270f1d5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 619ed660fd4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards ba6d0449dea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 19299c9c7b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 0bff4a80ecb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 97958fc73db 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 6286c575bb1 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards d91c2edbb37 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 2c4d08189da 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards fd4fac26864 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards dfaf14f2aca 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 2df6ec4a1cf 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards c2860607043 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 798e1afcd0f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 75bc94cb0ac 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 258e5355482 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards a7a0940d59d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards f524d7c2764 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 93ce1aff0df 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards cafc737a7e3 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards d0db2a79ae0 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 6a76d502ea6 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 144b6a067fb 48: onsuccess: #782: 1: Success after binutils: 8 commits discards e3498d1b557 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards b3a2f443ea3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 1b1ef2ad7f6 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards c4c363d007b 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards b88e3276290 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 907b0e39a3e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 19b2a764b71 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards b145a445108 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards c366c133213 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards d9d9e2b41f9 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 56c6b21c3eb 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 18ca0f37aac 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 683f844cb96 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards f2f0a22cc94 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 83571d06832 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 63a5c26b4ae 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards b2bdf09918d 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards f9f490c9a3a 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 9025e11e1a0 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards d78532bbce7 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 674a6a6a023 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards a7dc747a127 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards b4d4f6c0f2f 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards f9c7e006ea0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards e7791425a92 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 33d906cc98e 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards b1b440ba800 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c489667a5ac 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 92ca07ea68c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ed006a80da5 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c5a28d4ea47 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new f6f8f305708 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4ef9ec60a4d 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3ed461d62b6 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 446f13bf7f0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 7259133c5f5 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 8c1f1fb663e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 7e381ba923d 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 8d51a056b4e 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new d2751d7d192 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new c006d6f1b25 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 16add68e636 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 8603051a518 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 1019783728c 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new d982b64a0bd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new ec25f0a3873 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 55191be855f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 31b1fe20af8 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 3037ee1a1fd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 6c8b88cb630 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 2f5c082901f 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new b0b31ffe630 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 2ba57f88c48 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new ce4b843b9cb 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 3f5880575a6 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 2cee81ebfc0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new e864fddf3c3 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 514278d8003 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new cdca9bb9a4b 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new d9c2a4b4cd4 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 5677b8ce820 48: onsuccess: #782: 1: Success after binutils: 8 commits new a7a7bfcd3bd 49: onsuccess: #785: 1: Success after binutils: 12 commits new 1180de743ef 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 8cc2d21fb04 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 3c93246650b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 0721fdf2806 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 7d47ede03f4 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new c4f714b4d96 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 06ed784bf21 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 3bbae48b8e1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new a3b9bee1bc4 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 216853a2c6a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 377b3b2ad01 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 9a01ac7ffba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 98c54dfa3e1 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 8c4f4749fa8 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new a027cf1c05a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new f8e2f369ad4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 91b2a06a7db 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 2f9899382bf 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new ad88ad10e50 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 8f71ecf8aa6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 8b9a9061098 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 741a5638b8f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new d2d4ac33727 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 02bee66e19b 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new ca5bf6bb0ee 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 7a9ccb581e9 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 0a58c04d374 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 19fdd08a8bc 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 3df4adc6f57 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 766eea3c69c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 98052c87702 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 16bf080dd17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 202855a893b 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 2524e2d6904 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 6f5fe57f3dd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 68993034a45 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 6a2d47efe7f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 5b4893af8ea 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new c9cbf6242a9 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 92285ee85d1 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new bcf50657a29 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 7a6337877ac 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new d496184ab94 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 571962a7515 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new d48cb20d829 94: onsuccess: #832: 1: Success after binutils: 5 commits new 167653fcaf2 95: onsuccess: #835: 1: Success after binutils: 3 commits new 378b49a7017 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 89e99c15a7e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 6e3d0120d41 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 7a10b0f2c73 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 2cee15b6296 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 856cfcd204b 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 3400c94806c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 4e8bb120d18 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 9199d1307a2 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 089082c18c7 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 4ae737b71ec 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 9778ad0a4bb 107: onsuccess: #849: 1: Success after binutils: 5 commits new 6a8ae9da110 108: onsuccess: #850: 1: Success after gcc: 2 commits new 461eb5fc5fb 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 6020e9134f2 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 38504873f98 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new da21edc01a0 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 0482a060710 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new b60c74b7af5 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new cf3920505e4 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 9d2f4532b02 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 918f85e2a69 117: onsuccess: #861: 1: Success after binutils: 18 commits new ba8b652fee6 118: onsuccess: #863: 1: Success after linux: 12 commits new 02242900b21 119: onsuccess: #864: 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 (601859b8fe1) \ 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 1788 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39332 -> 39576 bytes 04-build_abe-gcc/console.log.xz | Bin 214516 -> 215288 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8428 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 246076 -> 243404 bytes 08-build_abe-gdb/console.log.xz | Bin 38932 -> 39148 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2772 -> 3576 bytes 11-check_regression/console.log.xz | Bin 4908 -> 7832 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 232 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 3739028 -> 3747500 bytes sumfiles/g++.sum | 224 +- sumfiles/gcc.log.xz | Bin 3318432 -> 3330456 bytes sumfiles/gcc.sum | 5089 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1080964 -> 1081840 bytes sumfiles/gfortran.sum | 114 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231200 -> 232148 bytes sumfiles/libgomp.sum | 26 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453080 -> 456840 bytes sumfiles/libstdc++.sum | 16 +- 38 files changed, 3078 insertions(+), 2749 deletions(-)