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 553897ab6da 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 659901d58c2 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards a1a9123d644 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards ff7cdfc7ff2 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 6231c960ef5 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 4886d62146e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards c914e298c28 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 877c8890f73 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 89a121cc995 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 25dc23d4f7d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards d4efb85deae 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards f6bbb4f12f0 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 6a616932d16 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards fe9cdd413ee 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 1f115a16f52 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards cd0466b3775 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards ce983730a19 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards be4228f6dbd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 7dfe958af2b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards e7e17115d0e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 5167e2948b9 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 9721b2a0937 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 7338bee3d02 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards d643ffbb0b2 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards fb017fed64a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 8bc3b163e7f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 0c505f461a6 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 7cf37fc1159 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 1f5fe0a2c86 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 60b9e55573f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 7d1ec89079f 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards ebb7c076730 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 713363f5a5a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 7ff5b5fc70e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 101cd347570 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards d43364c8e2b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 8ecca586e3c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 0ce889acbff 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards f7129520eeb 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards c671bf2d9b4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 641aa0620c2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 596091df02a 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 11e6d81d2be 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards fa1362fa339 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards f7de8b9e053 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards b56de458998 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards a564f324361 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards c464205e727 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 9a11d5b8b68 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 60a86100e98 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards b3a5b3583e3 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 14264ccda23 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 2efa6cd1999 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards e579b94f960 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 8dac2e6d07d 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 693f81b0295 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards f4c912c12f7 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 5313151b028 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 6c46a22f73c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 6396ed53bfc 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards b7adfecf8a5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards a55ec0eea54 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 13622d34241 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards b0925549518 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards fe799104474 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 3446ca76938 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 03348761c2f 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 64796ed644e 48: onsuccess: #782: 1: Success after binutils: 8 commits discards c83b0be18e2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards d696b70daed 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 4144f4318db 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards e7c3358664a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 42a8986985f 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 0e9cbdc3fc8 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 858ee4ab849 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 1b794365c6d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards d03968308cb 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 3be0a957867 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards bd6c4e41403 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards f7df3f14c8b 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 283c5537bf1 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 1c5eee00c4e 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards d526c6a3114 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 915dc99bb51 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards cdbe79ed055 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards e1486c3c091 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards cebf8397443 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 5f091743054 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 46b144f2abf 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 8e2b95a2ab7 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 0e4daeb225a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards 90489edcc1e 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards d02970d7f9d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 8588424e3d0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards fd444438d64 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 6dc9259a13e 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d779adef483 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 91b564c964a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 8c23f9840b0 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 732b8114e92 16: onsuccess: 1: Successful build after binutils: 4 commits discards d98ac7b5b81 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4161f4b4990 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 78cb71c784d 16: onsuccess: 1: Successful build after binutils: 4 commits new 8a4ecc86f94 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 6c797f2ac00 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 08a8ddbfb3d 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new df138a70b4d 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 777d861975b 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new eff85292727 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new d90340ceea9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 9ec68d2ea88 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 777cdbbf12f 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new fb68a452d5a 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 0e87ddc9074 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 93578d7f3ce 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 36c09c6c299 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 968d977eedc 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 4d21927aef8 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new bb3a4b12e19 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 5d7782eedab 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 2554e2fe6e1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 14daeb25736 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 69fb4c92101 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 13d1023d5de 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 7c576a7b977 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 85be3c9e363 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 8c53ccd47f3 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 620504ebb2a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new f1fe2431b1c 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 72f728fa28b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new a75cf98d046 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 60ff1151463 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 5d8eec88af3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new c8bc4d56cf3 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 5d7b11e24ea 48: onsuccess: #782: 1: Success after binutils: 8 commits new 9264faa73b0 49: onsuccess: #785: 1: Success after binutils: 12 commits new 1b7c51fe6dd 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new ddaeb4d267a 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 1d56ce0d105 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 5ad3e010580 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 7f0a56b6d8b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new fa59b7f566f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new cc9871a3b2e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 45ef188e309 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 104a47d97f3 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new a92592654f9 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new c974dc6adb6 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 846db273969 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 30832047039 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 14d130482f8 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 6434a14e1aa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new fbaec5cce89 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 7be8a153092 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 7cfb3f8efa0 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 3aff8928530 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new c40709a75a5 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 0646de39afa 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new b2184566e74 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new a60d7898b2b 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new a3b14f88484 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 3228046e5bf 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 8b74ca1eb51 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 55248fe8325 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 137dfc1dc2f 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 2d2a286d573 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 13e6cdcb52c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 47e79572903 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 17f8044ca79 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 385fd6188a9 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new ad4713a7bc2 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 84fffef4c7e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 1c53c1fd367 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new af91aaf8ab9 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new ac1003153b6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new bf326ab5855 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 7d84b89ce06 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new a9f4e26c6ed 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 66ea2eceff4 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new c6efa766566 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new 4dac80139f6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 4942667e380 94: onsuccess: #832: 1: Success after binutils: 5 commits new e52226e342f 95: onsuccess: #835: 1: Success after binutils: 3 commits new c6ffcb2fa1c 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 48ca6873dd3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 75ef36ded78 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 6d80d8725d9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new a927713ddf9 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 058c780d646 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 789724a03a7 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 77c2166b351 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new d847130cf41 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 38639a65436 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new d7115226963 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new ef2b9165701 107: onsuccess: #849: 1: Success after binutils: 5 commits new 84887dce84a 108: onsuccess: #850: 1: Success after gcc: 2 commits new 81500816d51 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new f9678737b00 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a0f91f04750 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new a41fe8a6ed6 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new b6d2d6c6f6b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 27db290a0fe 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 8760c06b456 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 82dbb614d0a 116: onsuccess: #859: 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 (553897ab6da) \ 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 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 39320 -> 39056 bytes 04-build_abe-gcc/console.log.xz | Bin 213908 -> 214372 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 244744 -> 245628 bytes 08-build_abe-gdb/console.log.xz | Bin 39100 -> 38772 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3848 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2788 bytes 11-check_regression/console.log.xz | Bin 7580 -> 6152 bytes 11-check_regression/mail-body.txt | 42 - 11-check_regression/results.compare | 40 +- 11-check_regression/results.compare2 | 123 +- 12-update_baseline/console.log | 48 +- 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 | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3739640 -> 3769508 bytes sumfiles/g++.sum | 141 +- sumfiles/gcc.log.xz | Bin 3295760 -> 3305656 bytes sumfiles/gcc.sum | 5120 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1078404 -> 1080036 bytes sumfiles/gfortran.sum | 94 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230948 -> 231932 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451980 -> 453412 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 2801 insertions(+), 2933 deletions(-)