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 2ff71064f25 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 52f35935e30 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards dbfc3b95689 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 8eb8e81e0e3 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 8713353b5bc 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 0a2c1287807 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 6ecaec25e7a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 14bd663f080 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards cc0c2e5ef3b 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 1fba16ea8e2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards f41437d5c84 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 108ab3b25ae 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards d1f5e6150c7 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards c5beda41eb9 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards eac1380129b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards b8ed5af86c6 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 64c697f709e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 3e1a82212f6 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 36953a8b860 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 0ec1c56fb11 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 04f173e4bb9 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 3980e349a98 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 80145311c55 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards e052592026c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards d0dfabaa89c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards d0f9a913c5d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards cb2780e3fa4 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 03d63388acb 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 142ca7c2d0d 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards 231932cd206 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards 6af755e5ee2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards d84b5425135 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards e6fa5e0d25d 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards e7d0ecf4ce4 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 70685e80484 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 634e6875aa1 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 389adc0b130 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 7764e3e7a3c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 2f130207f9c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 24f2cdf5a50 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 3f16176e0ee 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 5422204c08a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards cdba2263286 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards ca444d38988 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards a7b6c6d7036 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards de73cd179d5 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards e7aa241de5a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 39286b3be03 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 6935b5d645a 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 079e736683e 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 04cf3164f71 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards ede95c1baed 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards b32a8f879a7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 9363137fdf8 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 30302306715 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 0fa0d76b24a 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards 09383628ea5 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 0e1539c3313 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 15a1b9279aa 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards b142ecb24c4 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 0d7d20843b5 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards f83c52419eb 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards f9791211cc7 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 800dcebd883 49: onsuccess: #785: 1: Success after binutils: 12 commits discards e8fd3a4f78a 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 480be4d7c83 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 0d33b1408de 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards 5a9a4ca14c0 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 7e0291e75c1 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 1029dc69e86 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 41876abcb7e 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 2b245dab32f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 62b440be8c2 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 73a985589f8 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards bbd6d6c8d8d 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 1b91add7328 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 4df3f38d344 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards 24efca23e5f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards c7756607c6c 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards b81deadb589 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 20b5944f27b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards db6bca43b4c 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards f71a085708d 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 1fe7a30e1cd 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 9ed096bb98b 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 7487900a669 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards a61f18e2a59 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards 64e262ecfe7 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards c9813e549f3 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 082690c9a50 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 0fdf8f07456 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards f3c819684f9 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 87adb70c1ef 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 590d341cd06 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards f6e677dac02 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards d697f33f0ea 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 0fbf3ea62f8 16: onsuccess: 1: Successful build after binutils: 4 commits discards 270872634cd 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 07f064a6aa1 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ae82fa13b47 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards c5e9373bd9e 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 548918e4081 12: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 128a279faf9 13: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 14b86d7e08c 14: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 25c272d2e45 15: onsuccess: 1: Successful build after binutils/gcc/linux [...] new bdd84efc398 16: onsuccess: 1: Successful build after binutils: 4 commits new 9a00729e868 17: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d17854b80fd 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new d6a2ac76e6f 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 02a311b77b0 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 57f4505a14c 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 4e933ebd5f1 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new e3409d61b03 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new a271892f75f 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 2dfc72e8658 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new bf43249444a 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 16ce15476de 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 9cc317864a4 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 1f7d7c191b9 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new a79242072a3 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new bc44c70ba6f 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 66fc3e40740 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new 8d1dea8b1b1 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new dc4d724f3f6 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new a62c633942b 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new e777fca9230 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new eef7dfff45e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new a7c05f4cabf 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new dc9b82d2e99 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 150bb87e51d 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new fbe076f66da 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new f220b01bee3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new d0d57b3b87a 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 408fe86ea2c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new 94fc7633003 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new de4da114b44 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new bdabebc7eda 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 52809ab3596 48: onsuccess: #782: 1: Success after binutils: 8 commits new 9591b435fad 49: onsuccess: #785: 1: Success after binutils: 12 commits new 8bac9b076fb 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 00c9e3d5c1b 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 40149b5a9ad 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 843376e126f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 0a17d01fd5d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new c3d890b9bde 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new bc6a333fc07 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 22a3aa0d2b0 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new b8f5a7509ea 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new 630f33c5b98 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new f7331f59c4b 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new b3478d9bddc 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 7ee009bb2a8 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 5dbb18dcdd0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 2b0e6f42306 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 8540e3b620c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new c852cb8ac79 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new ca5cab9ed3e 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 8649f800044 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new a93adb8dc14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 51d80fce8ef 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 05accb5ee09 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 84e7852e2bc 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 2700dc4e63a 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 54692b276c1 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 7b0fb269f28 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new 05623ff9f97 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new a7cbb745dec 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new 2dbe31d59dc 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new a69f9086003 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 8e7a119a077 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 506dac2fd90 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new f8d2aff0c9f 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new a0855d1da59 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new a7e64d8646d 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new e19c0fb45df 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new a6cf2e8aa4f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 8a2fe9ae128 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new bd446d3b576 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 9b1434a4670 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new ae3a52c56f1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new ab3a4ae433b 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 6c1733e319c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new a21fd4371e0 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 06b13d68289 94: onsuccess: #832: 1: Success after binutils: 5 commits new 058e05cdc95 95: onsuccess: #835: 1: Success after binutils: 3 commits new cc386ea880e 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 77854e6853a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new ad7a31bb3ed 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 673fb598222 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new a1e8ebdc7a4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 4e1a3f8b8f4 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 04d3172313c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new e6b57419b5b 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new efc0f8c87a1 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 7a35473ee68 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 45f3172cc98 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new 9b41b2fc0ee 107: onsuccess: #849: 1: Success after binutils: 5 commits new 6e53e0eb9c0 108: onsuccess: #850: 1: Success after gcc: 2 commits new 012ec58fd15 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 7727024eefd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 85495f19447 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 99b53d913f1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new bf821814c1e 113: onsuccess: #856: 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 (2ff71064f25) \ 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 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 39532 -> 39820 bytes 04-build_abe-gcc/console.log.xz | Bin 214244 -> 213872 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 244652 -> 244332 bytes 08-build_abe-gdb/console.log.xz | Bin 39028 -> 39160 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2980 -> 2920 bytes 11-check_regression/console.log.xz | Bin 7420 -> 8732 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 12 +- 11-check_regression/mail-body.txt | 59 +- 11-check_regression/results.compare | 28 +- 11-check_regression/results.compare2 | 564 +++- 11-check_regression/results.regressions | 28 +- 12-update_baseline/console.log | 56 +- 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 | 61 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 28 +- sumfiles/g++.log.xz | Bin 3743864 -> 3756372 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 3302572 -> 3285492 bytes sumfiles/gcc.sum | 5383 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1077068 -> 1085980 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232016 -> 230816 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452680 -> 451508 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 3506 insertions(+), 2987 deletions(-)