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 5a0a1b7a8a 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 5473b684d6 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 85bcb52e56 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 8914f9f8d9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards e4270a5b76 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 49852bf7d1 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 2c1b6334ae 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards b6765dd930 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards f867c9f587 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards e70a99a5a3 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 70b8dc8c0a 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 857fbd631a 127: onsuccess: #874: 1: Success after linux: 219 commits discards 8bf950188b 126: onsuccess: #873: 1: Success after glibc: 2 commits discards dcbacc60c0 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 96a52b2292 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 2063cccd58 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards f217966d7d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 5220a5dde1 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards c9cdd1d878 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 5f2a958988 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards e87f40f93f 118: onsuccess: #863: 1: Success after linux: 12 commits discards a397d1e3de 117: onsuccess: #861: 1: Success after binutils: 18 commits discards aae6a756fe 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 18ea7fd366 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 1901102056 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 84bc3a4a96 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 2c9726995c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 987fc09551 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards e8adcfc487 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 9006097735 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 20785f1c9f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 454fa2b547 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 37c6a26063 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 1dadfe744f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 0b8248ca70 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards e875e23fb4 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 60181c954a 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards e841375727 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards a88afff606 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 4e8e7ab0cb 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards fb5d6ba8ee 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards df9f12d967 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 4aaacf22c2 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards c0b84301cc 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 0c886006ae 94: onsuccess: #832: 1: Success after binutils: 5 commits discards d43b8e7c3b 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 413571b31b 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 646df18c21 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 00424d249e 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 627e73d4a1 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9c2e782639 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 40d41a9b1d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards cb43377bb1 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards cd59637ad9 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 9c57cf8952 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 728ce7fb83 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 5d0847e6cc 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 318f920394 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 82515edbd8 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 448e3656c9 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 436d11c143 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 2a75e5f0ef 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 177e7dc21a 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards a364d398f9 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 7a2a10f3a9 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 207f66799f 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 74da0a2196 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards efdbfbe282 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards e281bbe232 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards db4e0d0efe 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards f99c9aa1e4 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 9eba9190a3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards f7624f5d9e 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 86ce7dabb8 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards fda5ba451b 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 25ebb54b37 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards c8d0c2bb24 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 9c27b4719d 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 387b3d99f6 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards a20a7ba99f 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards cf86ca943c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards bcb000e170 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 6f162b40d6 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 54de4eb2b7 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 3b2b2e2b8d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards f140bc4255 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards b1ffef8fb6 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards a1997dc059 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 425ffc53e9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 62dd7ff9ff 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 3ac7e300f9 48: onsuccess: #782: 1: Success after binutils: 8 commits discards b88cbd3c48 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 438d163781 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 20f1366d78 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 0f935eb9bf 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards b11b5b8d2a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards f1ec25a365 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 88dbdce81d 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 340ae5823f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 5e5b29d260 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards b76ba6f9bc 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 5ea497e1c5 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new d542cac9ea 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 65d0f12bc0 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 74805cfee3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new a04cd83324 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 6632e34596 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 3c79d695bc 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new a9d7e3e555 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 6e96b797c0 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 8f07dfaa92 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 2c317c52e2 48: onsuccess: #782: 1: Success after binutils: 8 commits new 3bfd6b31e2 49: onsuccess: #785: 1: Success after binutils: 12 commits new 545a20c529 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 95aab256e6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 1b111177de 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 3632d08cab 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 5e314b56c0 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new b334afd978 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 084527af79 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new ab47a8cf36 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 0127913e06 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 0e916c2736 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new f5378c8499 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 72073ac434 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 56a840af85 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 234269aa79 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 708d93390e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 882d75f2a9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 8853f1e83f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new ad93877c65 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 2524a1f2e1 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 9050d44a98 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 7460313833 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 0b7644ddd8 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 854e1341a3 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 4228611657 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new df75be090e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 54868bc6ee 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 7ab57626b2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 7494d8674b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 89425308ca 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new c691192d9f 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 30d90393c9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new ad7e8f9e2b 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new a96368ae36 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new d53325156a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 5be6aa34e8 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new b4a449acbb 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 93c7b7f10e 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 1d919bb18d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 94b343da23 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new a717dae63b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 9cd93ccf63 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 1e54f1f39a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 404b193530 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 87cf2341e1 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 64584d66bb 94: onsuccess: #832: 1: Success after binutils: 5 commits new 56be2b44f3 95: onsuccess: #835: 1: Success after binutils: 3 commits new 2dd12fd640 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 1e032eff7f 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 463392c2e3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 38e67cd29a 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 1500accd57 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 0149348bc6 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 2d5cfcccc4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new b6538840b8 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 634bfe74db 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 198ae0f738 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new b036e084ca 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new bececa99c2 107: onsuccess: #849: 1: Success after binutils: 5 commits new 4555ccaa7f 108: onsuccess: #850: 1: Success after gcc: 2 commits new c035b68b59 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 2c1b6d8e9d 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 508c9ac7dd 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 6984c6e876 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 149ef1cad0 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 63e7db57ce 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new dbe0181a7f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 6af462b7d4 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 02bfc4964a 117: onsuccess: #861: 1: Success after binutils: 18 commits new dce021b7fd 118: onsuccess: #863: 1: Success after linux: 12 commits new 10f06c2a24 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 5a753f5b05 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 335b5a3160 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new e2340db499 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new fe39e7526d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 32d4fe6fc7 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new d2ad0decd7 125: onsuccess: #871: 1: Success after binutils: 26 commits new 369451f1ca 126: onsuccess: #873: 1: Success after glibc: 2 commits new b0fb9ba43a 127: onsuccess: #874: 1: Success after linux: 219 commits new 5fd5d67a01 128: onsuccess: #876: 1: Success after binutils: 12 commits new 551f9a6589 129: onsuccess: #878: 1: Success after linux: 3008 commits new 4ed02adb2f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new cf9ce5cad2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 6a6e5707dd 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 6d1902dc72 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new b83f17e416 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 92a5b395d9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 82d8ce4a43 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new b675ac6a6b 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 404670e6cc 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new b547d1a560 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...]

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 (5a0a1b7a8a) \ 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 1744 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 39864 -> 40576 bytes 04-build_abe-gcc/console.log.xz | Bin 215200 -> 216340 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8576 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 244836 -> 246312 bytes 08-build_abe-gdb/console.log.xz | Bin 39772 -> 39796 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3856 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2540 -> 3012 bytes 11-check_regression/console.log.xz | Bin 7184 -> 6980 bytes 11-check_regression/mail-body.txt | 27 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 165 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 3729912 -> 3777464 bytes sumfiles/g++.sum | 160 +- sumfiles/gcc.log.xz | Bin 3299552 -> 3323064 bytes sumfiles/gcc.sum | 4858 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1078392 -> 1082404 bytes sumfiles/gfortran.sum | 60 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2280 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231984 -> 232824 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455160 -> 461648 bytes sumfiles/libstdc++.sum | 62 +- 39 files changed, 2783 insertions(+), 2727 deletions(-)