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 519eb219af 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 23c8771825 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 8766416bd1 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 374ead2c83 108: onsuccess: #850: 1: Success after gcc: 2 commits discards aef6080c30 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 89448eb7ba 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 212f3b4751 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 39e10fea04 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards da46426921 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 3c2158743d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 612749a1fb 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 836a4b6819 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 12554227e2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards aacfe90122 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 945cca7c1b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards a4dc454f04 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 4303749e1d 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 562a2a9623 94: onsuccess: #832: 1: Success after binutils: 5 commits discards cbae093aa5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 7e15839df6 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards e03900b90a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 5ed915dc1a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 51792fe513 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 532ddc96d9 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 7d679152cd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards c9a70e8b2a 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 5bd41bc546 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 711d896b37 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 1039e46cd0 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards a7675473cb 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 15541d28fb 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards ef17b5a7b5 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 91c87f12d2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards e7fbc196a5 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards f3f770b6e6 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 3e8c0a1ccc 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards a1463c270c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 794ace86d0 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 59ef623e3c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards e1cb19ebd3 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 4dc5b2b58f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards a8b4553571 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards e292230201 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 6083b1ff0a 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 8cd63a2fbe 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards d934dc2550 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 7a0779c70d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards cb24abf133 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 7ca232f4e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards bd79c61577 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 2a4a5ba406 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards a55189997f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards d185fb6407 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards b275eb23d8 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards d5c1941cf3 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 25be5896e9 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 922940c85f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards d6261bde96 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards df91c5b5f7 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 0f1b82a2f7 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards c32ab81c34 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards e0cc263f24 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 3cfa102ce8 49: onsuccess: #785: 1: Success after binutils: 12 commits discards d2402cad0b 48: onsuccess: #782: 1: Success after binutils: 8 commits discards f3c9b0a46c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards d0e1ad1723 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards b52657a0fc 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards f6d0acf370 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 3d45aa9146 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 5e9b74310a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 4039c4841c 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards df90f16bbf 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards 71aa82afe0 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 9fc121989e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 9a70376a5d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 0420a8149c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 567c8857b6 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards 3f3ca3cd0e 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards b4951b33bb 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards b4708ed34a 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards bf2b424415 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 2461aaea6a 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 4c26c43bc2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards ede402c5db 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 186f1c01d2 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 9dce6c2200 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 187b95a172 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards e31c6da029 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards cba6b85560 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 725b093f85 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d55ad1bff7 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8baf49f8ee 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1654ed2a3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d33d98e9b4 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 85a7597627 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 912107dfc1 16: onsuccess: 1: Successful build after binutils: 4 commits discards ff5b80d4cb 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8dcf6c4885 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cfd66ccee1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9d3b1164c1 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2311a8be53 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c73ef54eb8 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c5e9373bd9 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae82fa13b4 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 07f064a6aa 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 270872634c 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0fbf3ea62f 16: onsuccess: 1: Successful build after binutils: 4 commits new d697f33f0e 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f6e677dac0 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 590d341cd0 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 87adb70c1e 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f3c819684f 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0fdf8f0745 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 082690c9a5 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new c9813e549f 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 64e262ecfe 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new a61f18e2a5 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 7487900a66 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new 9ed096bb98 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 1fe7a30e1c 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new f71a085708 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new db6bca43b4 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new 20b5944f27 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new b81deadb58 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new c7756607c6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 24efca23e5 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 4df3f38d34 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 1b91add732 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new bbd6d6c8d8 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 73a985589f 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 62b440be8c 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 2b245dab32 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 41876abcb7 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 1029dc69e8 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 7e0291e75c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 5a9a4ca14c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 0d33b1408d 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 480be4d7c8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new e8fd3a4f78 48: onsuccess: #782: 1: Success after binutils: 8 commits new 800dcebd88 49: onsuccess: #785: 1: Success after binutils: 12 commits new f9791211cc 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new f83c52419e 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 0d7d20843b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new b142ecb24c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 15a1b9279a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 0e1539c331 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 09383628ea 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 0fa0d76b24 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 3030230671 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 9363137fdf 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new b32a8f879a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new ede95c1bae 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 04cf3164f7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 079e736683 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 6935b5d645 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 39286b3be0 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new e7aa241de5 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new de73cd179d 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new a7b6c6d703 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new ca444d3898 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new cdba226328 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 5422204c08 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 3f16176e0e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 24f2cdf5a5 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 2f130207f9 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 7764e3e7a3 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 389adc0b13 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 634e6875aa 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 70685e8048 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new e7d0ecf4ce 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new e6fa5e0d25 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new d84b542513 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 6af755e5ee 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 231932cd20 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 142ca7c2d0 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 03d63388ac 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new cb2780e3fa 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new d0f9a913c5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new d0dfabaa89 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new e052592026 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 80145311c5 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 3980e349a9 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 04f173e4bb 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 0ec1c56fb1 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 36953a8b86 94: onsuccess: #832: 1: Success after binutils: 5 commits new 3e1a82212f 95: onsuccess: #835: 1: Success after binutils: 3 commits new 64c697f709 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new b8ed5af86c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new eac1380129 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c5beda41eb 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new d1f5e6150c 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 108ab3b25a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new f41437d5c8 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 1fba16ea8e 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new cc0c2e5ef3 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 14bd663f08 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 6ecaec25e7 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 0a2c128780 107: onsuccess: #849: 1: Success after binutils: 5 commits new 8713353b5b 108: onsuccess: #850: 1: Success after gcc: 2 commits new 8eb8e81e0e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new dbfc3b9568 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 52f35935e3 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2ff71064f2 112: onsuccess: #855: 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 (519eb219af) \ 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 1708 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39500 -> 39532 bytes 04-build_abe-gcc/console.log.xz | Bin 213488 -> 214244 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 243168 -> 244652 bytes 08-build_abe-gdb/console.log.xz | Bin 39164 -> 39028 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2740 -> 2980 bytes 11-check_regression/console.log.xz | Bin 6984 -> 7420 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 11 + 11-check_regression/mail-body.txt | 59 +- 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 184 +- 11-check_regression/results.regressions | 31 + 12-update_baseline/console.log | 48 +- 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 | 61 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 31 + sumfiles/g++.log.xz | Bin 3753876 -> 3743864 bytes sumfiles/g++.sum | 132 +- sumfiles/gcc.log.xz | Bin 3295824 -> 3302572 bytes sumfiles/gcc.sum | 4407 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1082600 -> 1077068 bytes sumfiles/gfortran.sum | 60 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230996 -> 232016 bytes sumfiles/libgomp.sum | 24 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 454972 -> 452680 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2698 insertions(+), 2453 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions