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 7d087f36a29 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 40efbef006b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 81226115b8c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards af7a0b9ca02 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards f22a3607507 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards d3c1edfb85b 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 7690cceafbf 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards b8ab31dbf3e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 17b31598e95 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 9d93519a573 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 106f340d4f8 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 781197c3025 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 2bb316a52e5 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards d749caccc1c 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 73b6b21b7af 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 20a8791bbcd 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards fb0885f2c45 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 8b6c871522d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 442b36b0b31 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards dcfb8230483 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards acbc791f106 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 7dd3c737f28 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards c2d03cd1f15 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 7e634b276ee 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 59c9ed5e8fc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 156929c08e8 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards f6a5cc217f6 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards f5e5e77349f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 64b76ed2468 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards dddc7f043fd 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 8263d82e33b 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 41f56e9bf9a 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards be3dbb9f3ea 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards cfdbe1fae53 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 0fcc244e57e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 56728f2f1e3 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 20ec736541f 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 74c37202d6b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards ddba7881ee0 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards fe9ed2f32f0 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 17237923040 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards c3dc70d46a5 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards e1ee03affaa 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards de30ab8a902 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards d3f39085def 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 2cf361fb8e1 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 81598cfc19c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards f9fc52f5ba5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 29d460bf2a9 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards bc2132e9bcd 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 6f44246be02 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards f8d1fac818c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 2b0ee1099aa 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards e872c349dd7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 16f4e2ecb2a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 62bf2f51344 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 9dfbef358a5 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f563fd2cc5d 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 3777cef88fd 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 2ec6f75f806 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 3fec95dbc55 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 511176289f5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards d09d0fda76b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 5a63868cefd 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards d6a9c5d47f4 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 45deaf04ead 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 78dab1d3de8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards f013d2e6bd5 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards e9ac5e0d943 49: onsuccess: #785: 1: Success after binutils: 12 commits discards e84b6253403 48: onsuccess: #782: 1: Success after binutils: 8 commits discards fd91cbf4d7a 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards e5562e15e12 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards fe99c4f1181 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards f1ebda3bf06 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 612bcce173c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards a45d9bdfd18 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 501ccf5ca5a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards da2d70d467e 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards fd584ac3297 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards c88359a8880 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards adb2a1a133d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards a29630d6d37 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 149a615e7bd 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 2063f1f05af 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 756279b2cc8 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 07e118838c3 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 35668186f53 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 0a0245f078c 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 0f1938a8a58 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 07839da339c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 9586c845424 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 973982325cd 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 88881cb4547 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 7f2b0951d30 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards a635334c3d8 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards bffd38a4192 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 144125b2989 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 6861853b391 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 38d7e14992b 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 5125295f7e2 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 9c2696f0b23 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new a4e0020b3e5 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new ed006a80da5 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 92ca07ea68c 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c489667a5ac 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b1b440ba800 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 33d906cc98e 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new e7791425a92 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new f9c7e006ea0 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new b4d4f6c0f2f 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new a7dc747a127 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 674a6a6a023 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new d78532bbce7 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 9025e11e1a0 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new f9f490c9a3a 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new b2bdf09918d 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 63a5c26b4ae 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 83571d06832 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new f2f0a22cc94 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 683f844cb96 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 18ca0f37aac 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 56c6b21c3eb 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new d9d9e2b41f9 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new c366c133213 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new b145a445108 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 19b2a764b71 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 907b0e39a3e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new b88e3276290 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new c4c363d007b 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 1b1ef2ad7f6 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new b3a2f443ea3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new e3498d1b557 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 144b6a067fb 48: onsuccess: #782: 1: Success after binutils: 8 commits new 6a76d502ea6 49: onsuccess: #785: 1: Success after binutils: 12 commits new d0db2a79ae0 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new cafc737a7e3 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 93ce1aff0df 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new f524d7c2764 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new a7a0940d59d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 258e5355482 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 75bc94cb0ac 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 798e1afcd0f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new c2860607043 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 2df6ec4a1cf 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new dfaf14f2aca 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new fd4fac26864 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 2c4d08189da 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new d91c2edbb37 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 6286c575bb1 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 97958fc73db 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 0bff4a80ecb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 19299c9c7b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new ba6d0449dea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 619ed660fd4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new fd9b270f1d5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new b3b869b1b2c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 54c75968771 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new bade4d706c6 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 7e632a3c52d 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 6ebb744f0ec 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new d6eaf91671e 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new e758b3f2407 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 00d2a3c29d7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 91105fb6f37 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new a9713876b8e 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new f023dc51bb8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new b2e829280d0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 48cf7eecd30 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 4466911cd13 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 162214917b8 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 8e0fa1a7489 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 04ca838db54 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 8482fd7e200 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new e99eafef1fc 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 472a5aa8cae 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new ab8af324e19 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 4b6fbd169c1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new b95bbd73241 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 7ca4540a5bf 94: onsuccess: #832: 1: Success after binutils: 5 commits new 1f4fc65f880 95: onsuccess: #835: 1: Success after binutils: 3 commits new 848d8f79d16 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 8c5cf587ae1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 7b1998b8ef1 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new aebdb5653e9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 823db54164e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 4b59229d0b6 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 5b781d39610 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 4faa3732557 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new a11df02b07f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 96515d78867 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new a59bf233c0d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 81baec4ddaa 107: onsuccess: #849: 1: Success after binutils: 5 commits new 0a16ed0b39a 108: onsuccess: #850: 1: Success after gcc: 2 commits new 0e8b39713b5 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new ddc0fdb09fc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 2d076fe955b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 1c02474b882 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new fe0eb75b840 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new b62acf004b9 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 929df00bddd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 5b10528008a 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 73440ebe65c 117: onsuccess: #861: 1: Success after binutils: 18 commits new 601859b8fe1 118: onsuccess: #863: 1: Success after linux: 12 commits

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 (7d087f36a29) \ 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 1804 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39540 -> 39332 bytes 04-build_abe-gcc/console.log.xz | Bin 213456 -> 214516 bytes 06-build_abe-linux/console.log.xz | Bin 8832 -> 8428 bytes 07-build_abe-glibc/console.log.xz | Bin 244988 -> 246076 bytes 08-build_abe-gdb/console.log.xz | Bin 38960 -> 38932 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2852 -> 2772 bytes 11-check_regression/console.log.xz | Bin 4780 -> 4908 bytes 11-check_regression/results.compare2 | 19 +- 12-update_baseline/console.log | 54 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- sumfiles/g++.log.xz | Bin 3750260 -> 3739028 bytes sumfiles/g++.sum | 12 +- sumfiles/gcc.log.xz | Bin 3289536 -> 3318432 bytes sumfiles/gcc.sum | 4598 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1082992 -> 1080964 bytes sumfiles/gfortran.sum | 58 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2272 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 231200 -> 231200 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 453136 -> 453080 bytes sumfiles/libstdc++.sum | 8 +- 32 files changed, 2394 insertions(+), 2387 deletions(-)