This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards 5c5b9a7e79 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 7ca1a7ea9b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 249992a722 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 5e4c891213 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards e865209550 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards a022787d1c 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 84a65d35df 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 24613f0af1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 3c7dc15733 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards c8706f7407 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 1dea966965 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards ff4826d89f 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 633890d79a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 069677c39e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 28e917751a 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 8606484cfb 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards dcab2f2f44 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 78286363ef 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards ed5116ad8e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 8c392da524 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 696ca32118 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards ac4b6456b0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 3732f364eb 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards faceea8a24 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 2b35d63f9c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 0750ab61ac 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 65c67f9714 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 4b02043a1b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 07fa6f8535 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 3c7ef8241b 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 32ce0067ae 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 646799c67c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 493bded246 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 454e4b9393 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 5c198ccb1f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 2712aff8b9 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 03b59f7335 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 7f03420afb 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards c22f72dec2 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8e1b0a0a93 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2412d28ba1 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b9434aa1c6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 1ffa07e02b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 73686f9fe7 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards da69525f31 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2d7e46625c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 477c92f57c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 8c53a1aeaa 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 10e75f8c89 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards e1219dd8b5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fe0d992c66 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dec5c755a7 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards edd79fbcad 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fd3ea558db 74: onsuccess: 1: Successful build after linux: 44 commits discards 9eb76997d5 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards a2e46312c7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10bbbec0d1 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards d8b7b02325 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 43fce54d1a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 58909e7926 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 43047e9474 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 78ad44b0ec 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6f3479732c 65: onsuccess: 1: Successful build after gcc: 4 commits discards b7efbee6a5 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e76e2c0c09 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 30839728a1 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 6a91fc17d2 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards cb7b9266be 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 43cfa82427 59: onsuccess: 1: Successful build after glibc: 2 commits discards 60f697bed4 58: onsuccess: 1: Successful build after binutils: 2 commits discards 9731bdef7b 57: onsuccess: 1: Successful build after gcc: 7 commits discards 8660673619 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fbbce4d01b 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24214537d3 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 43422bfd24 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards df09c041c5 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards a61e31e279 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 24b50b4d14 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dcc47842dd 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cea172dc8a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 7f3d6a68bf 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7906dd60cd 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 993b830bcd 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 457db79a2a 44: onsuccess: 1: Successful build after linux: 34 commits discards 5c46061b25 43: onsuccess: 1: Successful build after gcc: 2 commits discards 9b0730539d 42: onsuccess: 1: Successful build after baseline build: no [...] discards 2bacfb96db 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a22154a8e0 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d1a4c81853 39: onsuccess: 1: Successful build after gcc: 2 commits discards 218d095ed0 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d91c3b69c9 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9f8997930b 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d43d1e4ffb 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5615129c00 34: onsuccess: 1: Successful build after gcc: 3 commits discards b7b05df825 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 418c3c0356 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 55d3c0d98f 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7a3a218cea 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 7fede60989 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd99522774 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e5aa90f987 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e2b2fa4a11 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7ae6872550 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 038bcb008b 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 255d2efd67 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new c9273e486a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7918fc1fa5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new dc03d175ab 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4af2f02758 34: onsuccess: 1: Successful build after gcc: 3 commits new ab5899e228 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 030d80f722 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ead2336932 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 740d76c402 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1c1a8b03c4 39: onsuccess: 1: Successful build after gcc: 2 commits new 81ae7f401a 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5aa9de4d27 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 760764439d 42: onsuccess: 1: Successful build after baseline build: no [...] new 8849e22e87 43: onsuccess: 1: Successful build after gcc: 2 commits new 6908a8774c 44: onsuccess: 1: Successful build after linux: 34 commits new 76cbee0612 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6799c97025 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 1f60623190 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ee8b19e835 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new be42703e69 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 993d707b5b 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new de7d074047 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7a20bebe69 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a9ea0d6c23 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 145563ce54 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 626874885b 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 06d4020fcf 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5e62ac9c32 57: onsuccess: 1: Successful build after gcc: 7 commits new 7fc5f373a3 58: onsuccess: 1: Successful build after binutils: 2 commits new f63db6bc32 59: onsuccess: 1: Successful build after glibc: 2 commits new 03e95fcc34 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 14bd26d71c 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 28d5e7898c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 8ccff6dfa9 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 27e0d7e79f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0fb252f04 65: onsuccess: 1: Successful build after gcc: 4 commits new a2351a207c 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 557c0753d9 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8cb704576 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e8819bfa0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 5a410a7f25 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 02bfb76451 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ecf2b4b412 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2a51c77ecd 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fac00beb8f 74: onsuccess: 1: Successful build after linux: 44 commits new 8a5caba931 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5f320ab25 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 838a4382ca 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 45592c10b6 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c5c93f6a08 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c7ed24386b 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 5763dfda30 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new b5f2094f72 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e7ab4a1ddb 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 04c8bb4449 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 52b194e4d9 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new a824549f32 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 1cc5f85ac7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 18aabd7bb3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 86d31e7626 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f3222f7de9 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 51404cadc4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 6c65bad239 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 3d56a53bed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 6db89bd44d 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 3a8697c41b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new c1ba9e8e3c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 57befabf0b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 0163ef994f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 1028bd6fde 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 532a135fd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new cd8dac096e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 447706bb15 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new ee35eff544 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a85c63fedd 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f67ca43360 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 648462a680 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 3edea7447f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 2b253f3dfe 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 1309d1a375 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new d4acab8067 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f301720494 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 51a59a295e 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 893b97fbe4 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 5b12d4888e 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 2232a341a4 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new d5630a4e42 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 8b2129e649 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new ce60da1416 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 6138182850 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 74c0282f80 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 16d2ff07d3 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new b84b64af94 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 2b6b27dc82 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new ee2514b636 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 4985c945c9 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 2020d6b6cc 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 6d7c51705a 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 5cc4a42866 128: onsuccess: #1723: 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 (5c5b9a7e79) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

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 1688 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29940 -> 30500 bytes 04-build_abe-stage1/console.log.xz | Bin 90376 -> 91540 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 233720 -> 235660 bytes 08-build_abe-stage2/console.log.xz | Bin 223256 -> 224876 bytes 09-build_abe-gdb/console.log.xz | Bin 37180 -> 37648 bytes 10-build_abe-qemu/console.log.xz | Bin 31016 -> 32032 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 2480 bytes 13-check_regression/console.log.xz | Bin 5300 -> 5820 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 27 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2683832 -> 2658052 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2198808 -> 2241116 bytes sumfiles/gcc.sum | 2152 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 877232 -> 885908 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201104 -> 201108 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423708 -> 429572 bytes sumfiles/libstdc++.sum | 14 +- 37 files changed, 1267 insertions(+), 1290 deletions(-)