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 4149bee4f5 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards a31c088f47 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 6370705fde 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 222c279c3e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 92221075aa 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards a66e16564a 95: onsuccess: #835: 1: Success after binutils: 3 commits discards bb90aeacd7 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 1790244615 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ba6099675c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 62e9ad9409 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards b8148f0a03 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 24e9fe8e24 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 00da8c3c24 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 130140b428 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards e6e52f2df8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 5b8336f76c 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards a78a1069a1 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards af9bf7ebcb 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards f23f16396a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 66e8fd358b 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7a4a71b09b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 533d422d73 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 2ac71a4542 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 223523930d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards b8a4ab8506 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 037b63d05d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards ff0e6fc0b1 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 1d961039c9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards e2b258c7df 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 462d87a64c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 1043dae4d1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 204d0a69c6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards d809c77d58 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards aadbf1d223 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 2d434a70d4 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 2ed65ecf36 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 7ac4c51a2d 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b5fde2f0e7 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 24524304a5 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards d502b1fa68 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 24d3d8aae4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards f2128a43c0 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 0369be36b5 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards cb4470485d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 71fd7b5f50 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards f13323a5ec 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 2b3567035a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards a5d94ff1d9 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 9be30e6001 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards b0f4193b0c 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 31c40b7046 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards e754513030 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 822f5eee05 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 5ad1cfffd0 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 7bfaa489b3 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 6bb27fc56f 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 685078f817 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards f4d0a1e040 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 413cb87a94 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 9cb41fc912 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 4fbf3d6860 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 366376ea89 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards ce9655cd6e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 99133fa3c2 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 4c255e0cf0 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 0bead72cef 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards f2792e60cb 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards b9df46d311 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 77421ca188 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards bfa9eed3eb 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards d61ec9cf74 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards fd382af591 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards b155f18e0c 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 5069c4451e 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 754b6c16c2 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 90710198bb 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 5662c7dad7 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 29a5cb4bde 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards c98f2cfccc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 9f286ddddc 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards daf024ecef 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 75b7919290 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 17e7255b4d 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4505e37003 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 43610ba6fb 16: onsuccess: 1: Successful build after binutils: 4 commits discards 5a34c02681 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be74ba6bb4 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 68161bd881 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a3352d9b60 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 94bb04547a 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a54156407 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cf3d386d59 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8b0ee7e426 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e3d1d69940 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b6f40e02db 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards eb01eb74c5 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 0641f5a7d0 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c4dd935043 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 601308a433 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3ef7050a49 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 54eda6b1e6 0: update: binutils-gcc-linux-glibc-gdb: 1 new 41c2f91a8d 0: update: binutils-gcc-linux-glibc-gdb: 1 new d78e1bed9d 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 608c7e847c 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3142422efd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 889f18e9db 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6d672e94dc 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d85836ab26 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 3ccb600a39 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 673b2faef3 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6d84fb49c7 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4fc0a63e0a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9cb67b0d95 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4127a192a9 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 030a16dbb1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 878ce17d6f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eee3fea60f 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2359d070ba 16: onsuccess: 1: Successful build after binutils: 4 commits new e0be1feea6 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7b0b3acbc9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c3060f859c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a5ea9e210d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 14bfa859c0 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7dc514a786 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9483851f4c 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new d49b8510f8 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 8cadc7f1e3 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 0a125ef551 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new d39a2d6ef1 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new e3d730b8d0 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 8b77bc3524 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 044fa59317 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new 53fe58bd18 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 95a25307de 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 867f25ec40 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 8425f3a8c6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 0eff7c3a05 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new f599bef16c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 5ac0d45e02 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 969f846586 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 6bc132e805 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new ce033bd7d7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 7c8c35de0f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 5068cc7b22 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 905dd095eb 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new a4996dd12c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new cca428cab2 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new a785bec747 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 7fb46e3415 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new f31c58352c 48: onsuccess: #782: 1: Success after binutils: 8 commits new 2caf435516 49: onsuccess: #785: 1: Success after binutils: 12 commits new 8625fcb3fd 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new ea9da694e6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new bf673f6e84 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new b1cd6181fc 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 4ce73ffded 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new d37c2b87f1 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 5490575364 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 084ad84c4c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 58eab802f1 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 6cf55ad934 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a1f8fc278a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new ac5509df10 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 3f060fe55f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 3930699636 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 8bd0e87274 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 549034b7ab 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new bd84a31d87 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new a0cdb59ad9 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new b7b2fc5a78 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 581f2b1679 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 6ecf6c5d0a 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 55f2360d8b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new cdc3c1e946 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new aeda5a64c2 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 0830c401be 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new cf737224e3 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 15c2e27d28 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new b3e7f332f5 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 5652f33e98 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new c02990348d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new b84f861185 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 50ce8fbb9c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new a3c4fec973 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 1ec495e146 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 309609b386 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new e1e36ffb36 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 1f251cebe4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 336d500e24 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 395c3478ce 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new d91c57d56d 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 45947a5bad 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 8bb2901e7f 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 187330af3d 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 27b00e5c23 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b1e832e416 94: onsuccess: #832: 1: Success after binutils: 5 commits new 8d3bb6db37 95: onsuccess: #835: 1: Success after binutils: 3 commits new f1015bce93 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 35a8804204 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 60d67f0988 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new b049814b7a 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new c85ec761f8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 8ce28f0640 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...]
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 (4149bee4f5) \ 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 1752 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 39376 -> 39764 bytes 04-build_abe-gcc/console.log.xz | Bin 215056 -> 215748 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 8752 bytes 07-build_abe-glibc/console.log.xz | Bin 243744 -> 244432 bytes 08-build_abe-gdb/console.log.xz | Bin 39168 -> 39128 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2716 -> 3744 bytes 11-check_regression/console.log.xz | Bin 8804 -> 5980 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 10 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 29 +- 11-check_regression/results.compare2 | 560 +--- 11-check_regression/results.regressions | 30 - 12-update_baseline/console.log | 39 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 30 - sumfiles/g++.log.xz | Bin 3741716 -> 3749764 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3294100 -> 3299144 bytes sumfiles/gcc.sum | 4893 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1079704 -> 1077360 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230636 -> 231784 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450112 -> 453816 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2678 insertions(+), 3230 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions