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 dfcc568444 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 327d133f38 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards d24fe46efb 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 31e9ae6ea3 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards eaa62f6192 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 21afe2a28f 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards cbe2f6fbc1 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 8eeb465d64 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 81ac248d16 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards b486bbfa8f 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 7a170b6b46 94: onsuccess: #832: 1: Success after binutils: 5 commits discards fc0c649648 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ddd4c93151 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards c8624a76ee 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 137e06e651 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards b3497cb3ff 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 4d44952747 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 2ce3521e3a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 3deee609df 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards a69a44d19d 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards b1b13f96c9 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 4266ca1b8d 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards cb76925a1e 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards cffb407054 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards eeb3518e95 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 3e1c4b9873 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 5f23f09dfa 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 2a1cecbd8e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 038f8069ec 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards c6b5aa4fe0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 6efde22413 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards dc39d3fd35 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 0074050889 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 63f9ddaca4 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards a17b43b282 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 9a2f3c0d8a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 1d363593ba 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 81c7bbc5fa 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 3588979c8f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 1affecb592 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 31450ca6ea 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards a2581afb2c 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 7ce567a870 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 59f35b49b6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards e6e3d88141 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 94e4840e27 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards dd391485cd 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 44cf982065 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 1cae83f04d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards b966bb6a38 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards f4c81ef935 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards b61fdec91c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 24bbb709ea 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards b11588142a 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 5d574117b4 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 6ca38f2239 49: onsuccess: #785: 1: Success after binutils: 12 commits discards cca5ac1e9a 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 5743f8ea4c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 52d61035c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards bbbedd312c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards fc7299f284 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 1c43adf199 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards c2ad3752b7 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 705a546ed8 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards efeabe0b7a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards d793f4cbd2 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 619dc0ccd2 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards c934537719 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards f85ff6d5c3 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 329e6d60af 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 1e52a1166f 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 1602433c92 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards 121327752c 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards cc1be23e55 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 6c1325a835 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards d95692fb98 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 15d4fdc642 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards b55ddf6aee 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards afd7660995 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards d765e5256a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 44d6695f2c 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 674976f7f1 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards c8dda7aac4 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 0f0a039f41 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ba977ac60e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 47e0c93c3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bfb255a95b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3917699e98 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 30159a27ca 16: onsuccess: 1: Successful build after binutils: 4 commits discards ab4dc3b450 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7911f8d7ff 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d9fed8ca79 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 90d2eb8197 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e223df0fc 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5088a0020a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5b9ada933d 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 50d961633a 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bdfe06b46f 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards cc236f1ed4 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 106b06d8f8 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards c7c562708d 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ad56224a7b 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f1d9e40543 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ad79c8713e 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ac370e4878 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 8069af9b6b 8: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 99d64956e5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 32a325528a 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 277d001666 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ffce259b31 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 78069d98af 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 00e1fdd2df 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d738b80ea3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8717e3e46a 16: onsuccess: 1: Successful build after binutils: 4 commits new 9ec5af3d46 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5696d461cb 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e0c870a497 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 73b0b33d61 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3466717e6c 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 964ea31705 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 042feadc95 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ad12efa7cd 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new decd5c14f5 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 10ba189b9b 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new d98c8be98a 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new bbd7e4c47a 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 7d3fad6525 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new af14e3c26d 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new f8cbcc1706 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new e7fd167d69 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new 5cd2b744df 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new e3a6b4f9a9 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 9bb03ceb95 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 3e5ab1f8b9 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 3e29644a1d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 7654c41641 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new fb20d7a01a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 221646095f 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 7936c94d31 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 525a976005 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 7592e9bb3c 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new a77661accf 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 436fb96d13 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 8c1c4432bf 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new b50d78121e 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 8ea08df888 48: onsuccess: #782: 1: Success after binutils: 8 commits new 38bdcdde23 49: onsuccess: #785: 1: Success after binutils: 12 commits new ed031165e0 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new f336f4143f 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new a1dad78169 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 0d3ce97b4d 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 6d0ca6298a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new ae2ccff6a6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 5eb071839e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 4928255d42 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new fbc1b9fa58 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new ba71bef5c4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new f1f1c90657 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 168e44ddcf 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 640afca595 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 2efc6be314 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new f8e99eeb6e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 7289c94ab9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 5cf243d24c 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 46a3f9888a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new a803ef75fa 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 08b1f2050e 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 1fc4e817b5 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 340c8b0a1c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 2c40b3b492 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 8f5e685844 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new d1e3a9ad05 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new d4c5c88382 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new f3ecb8e4b1 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new d0da0484be 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new a5dd83e144 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 6fa7d70306 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new f4351516e4 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new b692cc35c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 5cde51b5a1 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 35016909d2 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 6f0d71d66a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 4946d4dc5d 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 7e50426e6f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new b55ff47f14 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 36311a1615 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new e985b627c9 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 4ac72f0099 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new e973a5fca5 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 3906bc5855 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e9ffac24fb 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a22ecc3282 94: onsuccess: #832: 1: Success after binutils: 5 commits new 4861e4d1ac 95: onsuccess: #835: 1: Success after binutils: 3 commits new 328769d724 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 117f77c352 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new a0861c51f8 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 81c565b5a3 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 789b6dfec8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new cbc1d6fb5a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new d15e8f0564 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new ac5354e1b6 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new bd074ed87f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 46cb8b9b94 105: onsuccess: #846: 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 (dfcc568444) \ 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 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39400 -> 39236 bytes 04-build_abe-gcc/console.log.xz | Bin 214192 -> 214764 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8384 -> 8528 bytes 07-build_abe-glibc/console.log.xz | Bin 244608 -> 243512 bytes 08-build_abe-gdb/console.log.xz | Bin 39060 -> 38888 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2504 -> 2724 bytes 11-check_regression/console.log.xz | Bin 6476 -> 7208 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/mail-body.txt | 58 +- 11-check_regression/results.compare | 29 +- 11-check_regression/results.compare2 | 208 +- 11-check_regression/results.regressions | 40 - 12-update_baseline/console.log | 62 +- 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 | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 40 - sumfiles/g++.log.xz | Bin 3748656 -> 3720096 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 3280156 -> 3272888 bytes sumfiles/gcc.sum | 4996 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1079992 -> 1083272 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230704 -> 230664 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453312 -> 452588 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2866 insertions(+), 2873 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