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 938c8c2f5dd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 11790d16ab0 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 0c5493d2502 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 8d707b2176c 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards ed5ba05234c 118: onsuccess: #863: 1: Success after linux: 12 commits discards b1f047360f8 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 943ebf199f3 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards c60d51a2229 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards ac4bb239280 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 1550a7e6edd 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 06f43ddf6b4 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 9885b361c0e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards ea781c2d1cd 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards a76315a4bca 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards d05d5dbd5ec 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 971b1c040b3 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 2aba4dc57a2 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards 8e9dd2f9f97 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 9325352def3 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 4f3d71a62a2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 65ec78064a8 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 617107f8ef7 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 585330ade68 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 81ae5437fd0 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 31934640ca3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards b43336b9f3c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 9d08d42163d 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 4769408e850 95: onsuccess: #835: 1: Success after binutils: 3 commits discards ea9c9e2bd4f 94: onsuccess: #832: 1: Success after binutils: 5 commits discards a83a088a9b2 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards f4f540b0c2f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 31878b09c53 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards ccbb5abc929 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards b94b5c8466c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 6f4024cc56f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards e3bfb65eaf9 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards 43ebe76f54c 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards d7ce545e822 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 6d74a0ac510 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards c1591ad500c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards f42cf02bb52 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 2d2b3722d60 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards e59b77d368f 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards d425672825a 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards e9272cc2ff2 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards 221a4b254f2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards 3fe6b7fa737 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 30c650d9503 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 98dff52af97 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 748df362bf8 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards b93aea0a697 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards b9fc13c07be 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 3efef04ece1 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards 2c1a50cd5c4 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 36661108391 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 2988d02f48c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 6855073f9b9 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards c7794d5620c 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards fc84cd0d4b0 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 0da43428491 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards c72451efbde 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards a678af267c6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 68d6d6964c7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 07e85dfc293 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 92f3ac7119d 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 83bdbca7130 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards a336c841771 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 48e6b4d64ee 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards e2597903787 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 874afaf62ea 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards 266a19c752a 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards d4fdefa67b5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 19ea697dc23 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 342dc70dec6 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 15f45cec913 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 44b5aa0f94c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 103d16e6ff8 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards f7544c7f766 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 0b35e3c094a 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 5ccbda5c7fe 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 8fead16106d 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards c35d11424dd 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 67ce2b9c9b9 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards d66341d0bd0 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards e56a464e25a 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 4eb3fe35c48 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 8439aa53fa5 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards b467311d5d0 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards bf722060785 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards 710400165bb 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 478733259e4 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 4478425bf59 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 8e238301f88 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 0128510115d 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards 814639c6a0f 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards 87da2a93fd0 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 35bacbd7022 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] discards e019796ea5a 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] discards aee9ae88126 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] discards 2d99fcf2da6 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards cffbe909eaa 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 16a7c552e5d 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 9bba33ec773 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 1cc54c70492 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 [...] new 3b179209147 25: onsuccess: #757: 1: Success after binutils/gcc/linux/gd [...] new 81b23c4926c 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new bbc968b4898 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 55b89fbcae3 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new c900bbd4aaa 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 0d0633aed66 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 7d71c7d84d7 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new fc01f82c50b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new bf71170c46a 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 9ffc0159b6b 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new 7d4fe4da526 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 65e4aac64c2 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new 2995d0b121f 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 6f698f40101 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 1bd2edd4eea 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 4d7dd4ce2eb 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 45a8e815368 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new a3f5baf2a78 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 2a29fe50bb6 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 2c359fdb6cc 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new ac8b68c6ce7 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 300b53841b6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 72f4b4cef61 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new aac840c5c3d 48: onsuccess: #782: 1: Success after binutils: 8 commits new be4ff11c5f2 49: onsuccess: #785: 1: Success after binutils: 12 commits new 3daa8721be9 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new a6c51a43560 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 8c93c3fe343 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new cddb027a6c8 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new fa72cc6ec65 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new e098201f4f6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new 749a03992fa 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 998a1cdfafb 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new 82d9fca4652 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new ebaabae2ae0 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 32218a20000 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 6f4fc559576 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 3d66f9b4517 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 1179e8defef 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 41b1704513e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new f59c195227a 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new 062899f6706 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new c58f2e77347 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new ee1e5725c1e 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 0593d0b9818 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 2a739d4289b 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new a5e629ec68f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new a6f071dd773 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 28dc1a6c60d 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 23aa4a90e51 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 8ce2aef2ff5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new ba6ff964bf2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new b534ce783e1 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new f1a21856f55 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 84d0c747935 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 6552f26c582 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new d4cff3d7ce4 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new bad95a8ff1a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new ed0bfaebdae 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 2d65dab67bd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new d3095f7faa2 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new dea4ebc72c8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new 6dcf0fd6f9d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 1c074dd7873 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new 0c56b52c463 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 28661c6f2ec 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 9530e295a7c 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 9db5d71fdeb 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new ad94dd08559 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 175e971e1fa 94: onsuccess: #832: 1: Success after binutils: 5 commits new 9cedaf07b84 95: onsuccess: #835: 1: Success after binutils: 3 commits new 43bf52d2df1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 35741088f3e 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new fa08fe43712 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new e3f7b6fe8ee 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 233b971d221 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new c5c64363150 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new 272374766f5 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new bbc1f3b0e82 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new f442979a116 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 88692dd9af0 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new b98586d07fc 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new a9896b54606 107: onsuccess: #849: 1: Success after binutils: 5 commits new d9d0e128416 108: onsuccess: #850: 1: Success after gcc: 2 commits new a1bace73a0e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 55de3c32fcc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new 84e22835941 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new 8ed5b4aad74 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new d359075888a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 1f68281be45 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 63b6118131a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new dc150b63e53 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 7e5285c5a0c 117: onsuccess: #861: 1: Success after binutils: 18 commits new 9517f36bcd9 118: onsuccess: #863: 1: Success after linux: 12 commits new 72107ed7e91 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 9732ae991ce 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new df2a105daed 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 44a12eb49b2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new ab3a1a083c9 123: onsuccess: #868: 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 (938c8c2f5dd) \ 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 1752 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 40060 -> 41168 bytes 04-build_abe-gcc/console.log.xz | Bin 214920 -> 216220 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8828 -> 8764 bytes 07-build_abe-glibc/console.log.xz | Bin 245532 -> 246468 bytes 08-build_abe-gdb/console.log.xz | Bin 39868 -> 40500 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3888 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2768 -> 3024 bytes 11-check_regression/console.log.xz | Bin 7896 -> 7520 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 12 +- 11-check_regression/mail-body.txt | 62 +- 11-check_regression/results.compare | 35 +- 11-check_regression/results.compare2 | 233 +- 11-check_regression/results.regressions | 35 +- 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 | 64 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 35 +- sumfiles/g++.log.xz | Bin 3732384 -> 3781660 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3319476 -> 3307336 bytes sumfiles/gcc.sum | 5172 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1080408 -> 1079296 bytes sumfiles/gfortran.sum | 70 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2280 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 231132 -> 233012 bytes sumfiles/libgomp.sum | 43 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 451804 -> 457880 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 3065 insertions(+), 2948 deletions(-)