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 b547d1a560 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 404670e6cc 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards b675ac6a6b 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 82d8ce4a43 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 92a5b395d9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards b83f17e416 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 6d1902dc72 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 6a6e5707dd 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards cf9ce5cad2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 4ed02adb2f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 551f9a6589 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 5fd5d67a01 128: onsuccess: #876: 1: Success after binutils: 12 commits discards b0fb9ba43a 127: onsuccess: #874: 1: Success after linux: 219 commits discards 369451f1ca 126: onsuccess: #873: 1: Success after glibc: 2 commits discards d2ad0decd7 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 32d4fe6fc7 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards fe39e7526d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards e2340db499 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 335b5a3160 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 5a753f5b05 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 10f06c2a24 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards dce021b7fd 118: onsuccess: #863: 1: Success after linux: 12 commits discards 02bfc4964a 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 6af462b7d4 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards dbe0181a7f 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 63e7db57ce 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 149ef1cad0 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 6984c6e876 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 508c9ac7dd 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 2c1b6d8e9d 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards c035b68b59 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 4555ccaa7f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards bececa99c2 107: onsuccess: #849: 1: Success after binutils: 5 commits discards b036e084ca 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 198ae0f738 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 634bfe74db 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards b6538840b8 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 2d5cfcccc4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 0149348bc6 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 1500accd57 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 38e67cd29a 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 463392c2e3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 1e032eff7f 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 2dd12fd640 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 56be2b44f3 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 64584d66bb 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 87cf2341e1 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 404b193530 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 1e54f1f39a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 9cd93ccf63 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards a717dae63b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 94b343da23 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 1d919bb18d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 93c7b7f10e 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards b4a449acbb 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 5be6aa34e8 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards d53325156a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards a96368ae36 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards ad7e8f9e2b 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 30d90393c9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards c691192d9f 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 89425308ca 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 7494d8674b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 7ab57626b2 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 54868bc6ee 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards df75be090e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 4228611657 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 854e1341a3 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 0b7644ddd8 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 7460313833 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 9050d44a98 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 2524a1f2e1 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards ad93877c65 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 8853f1e83f 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 882d75f2a9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 708d93390e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 234269aa79 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 56a840af85 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 72073ac434 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards f5378c8499 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 0e916c2736 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 0127913e06 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards ab47a8cf36 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 084527af79 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards b334afd978 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 5e314b56c0 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 3632d08cab 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 1b111177de 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 95aab256e6 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 545a20c529 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 3bfd6b31e2 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 2c317c52e2 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 8f07dfaa92 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 6e96b797c0 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards a9d7e3e555 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 3c79d695bc 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 6632e34596 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards a04cd83324 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 74805cfee3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 65d0f12bc0 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] discards d542cac9ea 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 42d216d2ff 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gli [...] new 51aed3b256 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 704f56df23 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 02ed8f3154 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 543b67a641 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new b1a906b404 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 9fb2639757 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 99e26d7e5f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 3e2668d4ea 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 4b1f765011 48: onsuccess: #782: 1: Success after binutils: 8 commits new 036d925d4e 49: onsuccess: #785: 1: Success after binutils: 12 commits new 30625937ec 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new a3a528eab2 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 54eee30f9a 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new ff6a8d82ac 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 512c4dd924 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 9a053dbefd 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 3338ebaa98 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 719c1e34db 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 28f3cb22db 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 6f1c6f6fad 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 1ce2e5f872 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 3ea6fb6b69 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new c1646efa25 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 339dfffa5b 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 08f92db4cb 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 818f04f770 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 6c9eac002d 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 2cac81074d 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 7fd01309ea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 1a2cdd942a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new b0c400db57 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new e1ff83fa48 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new ddf79d64f5 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new a00d57ba2c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 6c48e820fa 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 2dcf48a339 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new c5fe134702 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new efa9300c80 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 4f9035e15a 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 40e3522b71 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 0fd0804faa 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 0989032c44 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new be4c2db1cb 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 40e164fda3 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 3d28bb2255 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 95989465bf 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 09d1bd2225 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new a39f3763e6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9f4453743b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new bc5c4da971 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 1e27eb0688 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 2c567dfa38 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 2cb6b2b3a1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new b17d6fbd77 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new a9aef33567 94: onsuccess: #832: 1: Success after binutils: 5 commits new a3dbc844a4 95: onsuccess: #835: 1: Success after binutils: 3 commits new fa4022eb2a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new c0fca66d29 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new eda0c4cbdb 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new b9ff9c5b6e 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 96b4eccb1c 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 6cc4969af9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new a2d082c34e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 5c10cf84ac 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new e1a697de08 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new abcf80fcba 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new ddebd86d7a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 9a896eb39a 107: onsuccess: #849: 1: Success after binutils: 5 commits new 222ae16508 108: onsuccess: #850: 1: Success after gcc: 2 commits new 67a802747a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new c43f9a5017 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new a574d64e71 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 91bba390b4 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 90ed957369 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 01ad012a4f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 2e37fbb08d 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 7deaf8b27c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new cecdcf176a 117: onsuccess: #861: 1: Success after binutils: 18 commits new 3b8a2945cd 118: onsuccess: #863: 1: Success after linux: 12 commits new d8fdb11c86 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new bca4f80a8a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 17908fe61e 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new fc4fe55526 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 8fa96dd6c9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 3bcf43a7e1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 0726ae72c7 125: onsuccess: #871: 1: Success after binutils: 26 commits new 6f6fa88aef 126: onsuccess: #873: 1: Success after glibc: 2 commits new 23110c21e9 127: onsuccess: #874: 1: Success after linux: 219 commits new 9f41588da7 128: onsuccess: #876: 1: Success after binutils: 12 commits new 65e78c47d4 129: onsuccess: #878: 1: Success after linux: 3008 commits new d8ef9304cc 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new ff1f9439a2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 64864aa58a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new dfd6952ac7 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 637d54cd75 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 3473e7cde3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 380f097567 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 95614f01ca 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new eceb875977 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new d7208fa6cc 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new d583171bf0 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...]
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 (b547d1a560) \ 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 1760 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40576 -> 40596 bytes 04-build_abe-gcc/console.log.xz | Bin 216340 -> 215364 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 8540 bytes 07-build_abe-glibc/console.log.xz | Bin 246312 -> 245448 bytes 08-build_abe-gdb/console.log.xz | Bin 39796 -> 39580 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3012 -> 2460 bytes 11-check_regression/console.log.xz | Bin 6980 -> 6964 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 179 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 38 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 + sumfiles/g++.log.xz | Bin 3777464 -> 3752572 bytes sumfiles/g++.sum | 114 +- sumfiles/gcc.log.xz | Bin 3323064 -> 3302488 bytes sumfiles/gcc.sum | 4786 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1082404 -> 1072908 bytes sumfiles/gfortran.sum | 67 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232824 -> 232176 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 461648 -> 452460 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2745 insertions(+), 2667 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