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 1aa97e7877 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards f3b86bba50 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards ae322eefb1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 5bd70d0f45 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 48dedfb3b2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 09d3ad869b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 8dcaeebb6d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 89390fc79e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards c5b3d84293 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a1efc2d8c7 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 081fa0f078 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 32568b3ce4 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards be84b88f36 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 7aafccf583 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 19eca28185 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards c02e8263bb 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 4eaf51b755 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5ddc199adc 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 5ab54f4819 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards f58ac3ef1c 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards c0cf4d4bfd 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 37cb8ca0dc 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 34481c3b05 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 55976fa96f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6e877311c3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 82ca3839d1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 56a0131452 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 394c4ef349 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 807d7eee5c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards c9f49e297e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 09b821d6b8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 7ebb5d6e0c 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards f88324098e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 7d687bb15e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards a1a9b991f7 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 00f64bbc77 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 451e23a9da 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards e21fdaacd6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 6ad83501f0 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 5ad3a8e543 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 8a4123f6da 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards d9330ad12d 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards c312cdd3bb 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 58e0cd5555 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards a5bd5e330a 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 76230ebac7 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards e37a93db85 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 254bb676f5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 6eb190649d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 4ac8cbc969 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards c909221efa 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 5f5b1c57b8 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 074a9a56f7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 66eaec6df4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 192ca53f30 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 94b1480a6d 48: onsuccess: #782: 1: Success after binutils: 8 commits discards a0b219770b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards b49e1442d6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 2ff4ece4ce 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 04f5ed61b5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 6769485d2c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 0742c1eabe 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 414ee26008 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 984bf64465 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 508fdd906e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 5120ef8a5c 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards b444605a3d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 151aa0675c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 5f7ca5fbe6 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 02ad3523f0 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 97beab0550 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 2d8b8de2dd 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 6cb1da5a7e 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards e9c11279fd 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 8c90c4f542 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards dbac8a3727 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 1e55c22a2f 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards e15491788f 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 6f6f49cb08 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 4a41bff458 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 58e6585ba8 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 278aa2e01c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards bd377d7977 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9a9a7e1fa 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 23e7013aa6 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9b6801d502 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd0e9e8694 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 46e770d61e 16: onsuccess: 1: Successful build after binutils: 4 commits discards eb3733acc5 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4008500922 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b961cf32d3 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc64b540b4 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards babdc3e24f 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c52e383ff7 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f9ac8a25b5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bb7c2a77f8 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d055da0d61 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 360f240957 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 820c096d57 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards a744e2945b 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 4e305383e9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0588d1f3c9 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c7c562708d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 106b06d8f8 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cc236f1ed4 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new bdfe06b46f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 50d961633a 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5b9ada933d 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5088a0020a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e223df0fc 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 90d2eb8197 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d9fed8ca79 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7911f8d7ff 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ab4dc3b450 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 30159a27ca 16: onsuccess: 1: Successful build after binutils: 4 commits new 3917699e98 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bfb255a95b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 47e0c93c3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba977ac60e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0f0a039f41 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c8dda7aac4 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 674976f7f1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 44d6695f2c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new d765e5256a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new afd7660995 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new b55ddf6aee 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 15d4fdc642 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new d95692fb98 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 6c1325a835 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new cc1be23e55 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 121327752c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 1602433c92 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 1e52a1166f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 329e6d60af 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new f85ff6d5c3 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new c934537719 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 619dc0ccd2 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new d793f4cbd2 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new efeabe0b7a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 705a546ed8 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new c2ad3752b7 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 1c43adf199 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new fc7299f284 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new bbbedd312c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 52d61035c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 5743f8ea4c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new cca5ac1e9a 48: onsuccess: #782: 1: Success after binutils: 8 commits new 6ca38f2239 49: onsuccess: #785: 1: Success after binutils: 12 commits new 5d574117b4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new b11588142a 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 24bbb709ea 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new b61fdec91c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new f4c81ef935 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new b966bb6a38 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 1cae83f04d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 44cf982065 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new dd391485cd 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 94e4840e27 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new e6e3d88141 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 59f35b49b6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 7ce567a870 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new a2581afb2c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 31450ca6ea 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 1affecb592 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 3588979c8f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 81c7bbc5fa 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 1d363593ba 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 9a2f3c0d8a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new a17b43b282 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 63f9ddaca4 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 0074050889 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new dc39d3fd35 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 6efde22413 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new c6b5aa4fe0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 038f8069ec 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 2a1cecbd8e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 5f23f09dfa 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 3e1c4b9873 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new eeb3518e95 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new cffb407054 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new cb76925a1e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 4266ca1b8d 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new b1b13f96c9 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new a69a44d19d 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 3deee609df 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 2ce3521e3a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4d44952747 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new b3497cb3ff 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 137e06e651 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new c8624a76ee 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new ddd4c93151 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new fc0c649648 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 7a170b6b46 94: onsuccess: #832: 1: Success after binutils: 5 commits new b486bbfa8f 95: onsuccess: #835: 1: Success after binutils: 3 commits new 81ac248d16 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 8eeb465d64 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new cbe2f6fbc1 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 21afe2a28f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new eaa62f6192 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 31e9ae6ea3 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new d24fe46efb 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 327d133f38 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new dfcc568444 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 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 (1aa97e7877) \ 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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 39184 -> 39400 bytes 04-build_abe-gcc/console.log.xz | Bin 214444 -> 214192 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 244028 -> 244608 bytes 08-build_abe-gdb/console.log.xz | Bin 39000 -> 39060 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2684 -> 2504 bytes 11-check_regression/console.log.xz | Bin 6680 -> 6476 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 4 +- 11-check_regression/mail-body.txt | 44 +- 11-check_regression/results.compare | 18 +- 11-check_regression/results.compare2 | 125 +- 11-check_regression/results.regressions | 18 +- 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 46 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 18 +- sumfiles/g++.log.xz | Bin 3768964 -> 3748656 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 3295056 -> 3280156 bytes sumfiles/gcc.sum | 4296 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1080092 -> 1079992 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230512 -> 230704 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 446520 -> 453312 bytes sumfiles/libstdc++.sum | 5 +- 40 files changed, 2393 insertions(+), 2287 deletions(-)