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 c40ffad94e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards dc3671e94b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 2125151a10 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 811c6cf824 107: onsuccess: #849: 1: Success after binutils: 5 commits discards fbaa214b4e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 56d5c493f6 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards da9bacd9d6 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 24fc975ffc 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 587a307337 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 2bf04a9ce9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 71212f8ef3 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards d35bef84cd 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 1476621d1e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 64fd92fb1c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 4f272d27ed 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards fc24ad80f4 95: onsuccess: #835: 1: Success after binutils: 3 commits discards be13ed5634 94: onsuccess: #832: 1: Success after binutils: 5 commits discards e605f9d36a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards ad975ba4a8 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 99dcfd3c16 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 7d455ddd09 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 4764da1482 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 5353b423c2 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 6b67e69cd3 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards cfe127e5f5 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 65f8facf93 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 048fdf9a81 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards a60a61ca85 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards b24a94b628 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 507c4fdff7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards b924e5b6c2 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards c536862e8c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards e64c567383 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 65a5dd0218 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 011377f788 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 7de7e3ccd5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 565cb1cf0d 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 04e41c2f89 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 30af9242ae 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 1cf9cdc33b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 72ea62c71b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 09821577c2 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 84d282ab06 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 29068dd850 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards a5817f7135 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 9b7f5da59b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 9113c130a3 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 4c425eafc0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 0d830ac3c5 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards faa18d91a4 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 36b9cea829 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 8652610a6d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards d9aee993c2 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 2ae22612a0 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 4741d7b9c3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 9616716c79 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 48d1391179 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards a3f0d8a4f3 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards c46e7eaec4 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 8ead1688b6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 6e735a2784 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards b306044904 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 9ed94acc53 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 1a6c28c62a 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 2ba2bce64a 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards f93d922b27 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 9a2c2dc8a3 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 142b596b3a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 3bd60ff70a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards d324c77b9f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards a8b91012d7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards f41879fd36 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] discards 8afef27606 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] discards 6e83c1f1c5 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] discards 4a50c96234 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards e9770ac82d 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] discards fd157804c3 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] discards 3d04286749 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] discards a0eb9590f4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] discards 47e01716d6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] discards 40a4b3db7b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] discards 9d982a6dbd 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] discards 056a9685a4 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] discards 0d45a682f4 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] discards 45543e6c18 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] discards 95fe11ada6 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] discards 10707a7202 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 9a4800ef47 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards b3075a9786 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards c51009788b 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 83440f0d21 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10d90dd117 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a4b9e27e8c 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fd9acc9cc4 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb5eb77360 16: onsuccess: 1: Successful build after binutils: 4 commits discards e6919d13f2 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 29abfcfeda 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3d51c353ab 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c64d821e7 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f19b7f0541 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 020e53933f 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fccfc80609 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2311a8be53 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9d3b1164c1 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cfd66ccee1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8dcf6c4885 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ff5b80d4cb 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 912107dfc1 16: onsuccess: 1: Successful build after binutils: 4 commits new 85a7597627 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d33d98e9b4 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1654ed2a3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8baf49f8ee 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d55ad1bff7 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 725b093f85 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new cba6b85560 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new e31c6da029 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new 187b95a172 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gdb [...] new 9dce6c2200 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gli [...] new 186f1c01d2 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gli [...] new ede402c5db 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gdb [...] new 4c26c43bc2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gli [...] new 2461aaea6a 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gli [...] new bf2b424415 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gdb [...] new b4708ed34a 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gdb [...] new b4951b33bb 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gdb [...] new 3f3ca3cd0e 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gli [...] new 567c8857b6 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gli [...] new 0420a8149c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 9a70376a5d 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gli [...] new 9fc121989e 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gli [...] new 71aa82afe0 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new df90f16bbf 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 4039c4841c 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 5e9b74310a 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 3d45aa9146 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new f6d0acf370 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new b52657a0fc 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new d0e1ad1723 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new f3c9b0a46c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new d2402cad0b 48: onsuccess: #782: 1: Success after binutils: 8 commits new 3cfa102ce8 49: onsuccess: #785: 1: Success after binutils: 12 commits new e0cc263f24 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new c32ab81c34 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 0f1b82a2f7 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new df91c5b5f7 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new d6261bde96 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 922940c85f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 25be5896e9 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new d5c1941cf3 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new b275eb23d8 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new d185fb6407 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a55189997f 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 2a4a5ba406 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new bd79c61577 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 7ca232f4e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new cb24abf133 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 7a0779c70d 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new d934dc2550 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 8cd63a2fbe 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 6083b1ff0a 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new e292230201 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new a8b4553571 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 4dc5b2b58f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new e1cb19ebd3 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 59ef623e3c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 794ace86d0 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new a1463c270c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 3e8c0a1ccc 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new f3f770b6e6 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new e7fbc196a5 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 91c87f12d2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new ef17b5a7b5 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 15541d28fb 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new a7675473cb 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 1039e46cd0 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 711d896b37 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 5bd41bc546 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new c9a70e8b2a 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 7d679152cd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 532ddc96d9 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 51792fe513 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 5ed915dc1a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new e03900b90a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 7e15839df6 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new cbae093aa5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 562a2a9623 94: onsuccess: #832: 1: Success after binutils: 5 commits new 4303749e1d 95: onsuccess: #835: 1: Success after binutils: 3 commits new a4dc454f04 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 945cca7c1b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new aacfe90122 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 12554227e2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 836a4b6819 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 612749a1fb 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 3c2158743d 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new da46426921 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 39e10fea04 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 212f3b4751 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 89448eb7ba 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new aef6080c30 107: onsuccess: #849: 1: Success after binutils: 5 commits new 374ead2c83 108: onsuccess: #850: 1: Success after gcc: 2 commits new 8766416bd1 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 23c8771825 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 519eb219af 111: onsuccess: #854: 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 (c40ffad94e) \ 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 1692 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 40332 -> 39500 bytes 04-build_abe-gcc/console.log.xz | Bin 213256 -> 213488 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8892 bytes 07-build_abe-glibc/console.log.xz | Bin 244092 -> 243168 bytes 08-build_abe-gdb/console.log.xz | Bin 40156 -> 39164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2564 -> 2740 bytes 11-check_regression/console.log.xz | Bin 8416 -> 6984 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 8 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 27 +- 11-check_regression/results.compare2 | 363 +- 11-check_regression/results.regressions | 28 - 12-update_baseline/console.log | 64 +- 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 | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 28 - sumfiles/g++.log.xz | Bin 3758720 -> 3753876 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 3296532 -> 3295824 bytes sumfiles/gcc.sum | 5668 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1076572 -> 1082600 bytes sumfiles/gfortran.sum | 62 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231692 -> 230996 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457544 -> 454972 bytes sumfiles/libstdc++.sum | 12 +- 43 files changed, 3134 insertions(+), 3421 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