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 1344549494d 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 937a2d87ae9 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards ede079a96a0 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 081e61f18ce 128: onsuccess: #876: 1: Success after binutils: 12 commits discards e52cd1c3b56 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2d4ba349dab 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 65335292f43 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 0288c8245e2 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 6c8e7fab85a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 591eb85960a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 488efe52b4a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards bb213ee53d9 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 7614e887157 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards a9c1005cc5e 118: onsuccess: #863: 1: Success after linux: 12 commits discards 9864670b06b 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 451416b86a6 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards ac55f53495f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 6c5b9d55d0f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 4d1112c6249 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards fecb467d37f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 21943cc6b79 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 1add1d469f3 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards d1684553550 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 33e22f09478 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9b5f5c2348d 107: onsuccess: #849: 1: Success after binutils: 5 commits discards e0aebccb26d 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 5512847c147 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards e4fe40882a9 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 965b722df49 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards fea0c16b1c4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards f50515b29fc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 949c447cbcc 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 2d3ad4cf831 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards a4c74092590 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards 2163168a3f5 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 9b6522ad8fa 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 51de7dfebd2 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 162a79dfb2d 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 481b87cd7cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards a810a37af31 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards b525fee49fb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards e4bc3de69a1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 7cc9429951a 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 19380184abc 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards fd9f058c1e8 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards bce55da6d25 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 19f056719af 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 415e6f7e841 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 6ff8fbb7932 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 74b3fa503a7 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards de18808f9c8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 89d6c20a416 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 4647ca8c947 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards da12c63e86d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards fce6b274b3d 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards b0dd7d9ebe2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 49357091fcc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards e3ecc989650 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 3c005f7c570 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards feceab5eb3e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards e1cd568ad95 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 79a6dd08994 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards e9e90bbed37 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards bebcdf7b72b 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards e79350ad7cc 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 8d1f5624dad 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8d63f46fdaf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 5ac1cbf53ed 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 9a544b63182 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards a7c512865f7 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards c2e46cb15f3 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards c6f03526902 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards a5ddcc4e4ab 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 99d34b2d87d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 72ba16fc4d1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards d24e658acc3 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 53c7bf6fb9b 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 07e31650e7b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 0dd819bc63a 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards de581d8ad4b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards f11795f5871 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 328cad21365 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards f8e050bdbfd 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 7dbb15e99f5 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 9f860f22758 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 5bf8c098011 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 418f9b62581 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 7d13eae2053 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 19c6a3614b0 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 66973e0c7d5 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards b6f2d17992b 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 5274893fc92 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 113fd015e2d 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 0de75554e63 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards d14b38624e7 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards a12f942070c 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 7dd9bd8dfe4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards ee083fd144a 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 9226e8c9230 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 0c5d60f0331 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 0108f7392a2 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new f6da4b15dc6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new d808a32d6c9 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new f02b4d5b884 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 36cbf598ad1 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new f659df71a32 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 0b5d4745743 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 26c359e7b74 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 4b259a1e5dd 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new b2ca7faa67d 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new f3d48a0735b 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new f9e6667e214 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new 007b72f2e4e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 755c804a442 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 0773cfd7883 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new d1c9cc61b4d 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new b728b5d81df 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new f9a5fc89465 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 5e70ccb1caf 48: onsuccess: #782: 1: Success after binutils: 8 commits new b4d298ab396 49: onsuccess: #785: 1: Success after binutils: 12 commits new 7fd6fba3642 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 7d0db5c52b5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 37d9a450ee1 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new d07305c0b7f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new bdd440e24b6 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 5bc08b461b3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 7469493d9bb 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 0d5c713ee63 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 90070c23ca3 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new ca92e67c94d 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 94e04484712 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 7777f99b47a 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 8842053ef35 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new d4bf740c8d4 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 1ce7bd5d6bd 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new b8161cf0ffb 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 1334e1a1068 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 13367350a9a 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 1621e774ae2 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 71b08141760 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 37e2e08f651 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new bbf0552d87a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new b5119c92f9b 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new ea46a6a9c39 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 5191e3f6840 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 441bba26fb6 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 24ea8c2a107 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new 8a9def32014 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 97cd48edd9a 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new bff8362e0e0 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 05588a7698d 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new f4f1170204d 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 4b1150f656a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 90abfb4a921 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new a528b6fba09 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 578ab523e19 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new 4b896d60c3d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new fe6049befb2 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new e571bae1d6c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new aafa0f53ea0 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 1728f55c173 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 07aecbbc91d 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new b36ceca9f40 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new a350fa4f35f 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 83ae852c295 94: onsuccess: #832: 1: Success after binutils: 5 commits new 03c75c41719 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7bb7e1db1c4 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 1b7bfac8b5b 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 91aa4f39684 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 9b56537b886 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new abed5775fec 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 189b9c147f1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new a89439238bb 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new a73152fd0bb 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new c6cb3139712 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 62afc410603 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 0fd5ef49e1f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 66d9260407d 107: onsuccess: #849: 1: Success after binutils: 5 commits new cf4c73b3c61 108: onsuccess: #850: 1: Success after gcc: 2 commits new 44ba04c1ead 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 3fd15ecf4a4 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new ad71ce499c0 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new e6e581b774e 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 5aaecd54004 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 96d7c7a5c77 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 8d9672b5f45 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 6847ca54619 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 73add8d9042 117: onsuccess: #861: 1: Success after binutils: 18 commits new a5f7463e1f9 118: onsuccess: #863: 1: Success after linux: 12 commits new 91388531f57 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 9fd35c7e878 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 092f28844d6 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new c6c4ea02873 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new f6af8d0b87a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new a9b2db6d5fc 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 55da97684a9 125: onsuccess: #871: 1: Success after binutils: 26 commits new 96a91418f12 126: onsuccess: #873: 1: Success after glibc: 2 commits new edf637a8774 127: onsuccess: #874: 1: Success after linux: 219 commits new c249ce65126 128: onsuccess: #876: 1: Success after binutils: 12 commits new e9f5a64ce22 129: onsuccess: #878: 1: Success after linux: 3008 commits new 0df9cc83112 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 1f89f2f1ed5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 7f625878b8f 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...]
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 (1344549494d) \ 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 1756 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39540 -> 39808 bytes 04-build_abe-gcc/console.log.xz | Bin 215176 -> 214540 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9600 -> 9780 bytes 07-build_abe-glibc/console.log.xz | Bin 244740 -> 243544 bytes 08-build_abe-gdb/console.log.xz | Bin 39328 -> 39260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3880 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2780 -> 2488 bytes 11-check_regression/console.log.xz | Bin 7508 -> 7388 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 17 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 212 +- 11-check_regression/results.regressions | 37 - 12-update_baseline/console.log | 60 +- 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 | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 37 - sumfiles/g++.log.xz | Bin 3754172 -> 3745796 bytes sumfiles/g++.sum | 184 +- sumfiles/gcc.log.xz | Bin 3350216 -> 3307476 bytes sumfiles/gcc.sum | 4892 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1081024 -> 1089368 bytes sumfiles/gfortran.sum | 100 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233108 -> 232152 bytes sumfiles/libgomp.sum | 28 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 449368 -> 450744 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 2886 insertions(+), 2909 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