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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 4de8f2cb15 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f79bf836ec 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a77d332338 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards ff504041f6 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 4f4996c29d 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 095adbcb19 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 9b96ce63b7 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards af123f23d9 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards a9d9665d4d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 761003e8c1 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 3ab1d7848f 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards f7750d661b 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 42172a411f 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards ca7bf581d6 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 23a2a02c84 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards b55ce3827d 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 84cdf22e76 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 0dc25d4736 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 6a93a1281c 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 520f5c494b 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 3a1a2db147 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards ef981d7dd2 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 72e2edd10c 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 7c3c50c5d3 127: force: #27: : Failure after baseline build: no new commits discards 1637db03b3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f23369dace 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 1e52d2cd0e 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 7337942580 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 7f24dbd008 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 7d088dfdb7 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards fcd74dba53 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ec84ae68b5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 864e06b867 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 7a3bbea651 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards cf0bd37f13 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards eb957c1d41 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 2003124433 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 24919e4aa0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards a1c5ff73eb 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 2c76b1b666 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 9f4dd23a42 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 95f0b0794b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 1f7585cc9a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards d88763eefd 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 5bb1611ea5 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards e16ad4efe1 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 87b6d15ab0 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 421d40cb97 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards fec7f8857a 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 273ba893b5 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 485a8f735a 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 4dfce6f04e 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 6e2ff081b3 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards ff33e326e1 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards a3bd1c61cb 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 464a74113f 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards c989d11f5b 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards cfd6e4153d 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 10908dead5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 3d2c71054a 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards b316ce1d92 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards f2431ddb47 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards bbda09a2e2 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 2c215fc70c 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 23abe7f0d6 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 8b64e0bfe3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 973c93eec5 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 17a475a03f 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 35fa7468df 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 59f643b9f9 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 4b645aa12d 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 97f8150e5b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 2a42246c40 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 5b666652bc 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards fa36dca4df 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 7ef5133c03 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 7372e3aa6e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards fe209f877c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 1cd0277590 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards dc263d3d09 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards ee8376c082 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 3aa30449f1 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards f3d3cffcbe 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards bbbe7bbbe8 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards ec2cad33bb 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards a2c21024aa 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 5860b7047e 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 5c84686183 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 40a29a5ba2 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 722704b64d 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 4078800239 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 1d4feea583 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards ebedc1ae5e 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 940ae024be 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 492838d3cd 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 140ba22a3d 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards c42e4ec370 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards fbdc2a1b49 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards ce507e613d 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards eb61e73e05 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 0b2b21ba38 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new a50f847b88 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new 49d3b4bc34 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 8c3d0608eb 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 6169a77d77 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 1898761a87 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new f9faced66e 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new b408cf0c5f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 1e5701998b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new d84367dd65 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new f11c08f859 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 64c354f5ff 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 81209230c6 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new b0f51e19cf 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 0237e7f9fe 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 4881f9b156 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new d046234d9e 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 5983d8eb0d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new b489e0c056 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new a34c3917ce 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 8ed5a7268f 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 7b41765f90 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 09166f6234 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new c91858498a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 42dc46dca8 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 61343aa430 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 90169c8622 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 0f7327cbf7 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new dc663d4744 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 099a11fd0d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 3c8ecf43ac 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 846b65938f 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 924333f228 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new abf08245f5 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new c91efe43fa 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 14bf994225 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new acaf565ecb 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new ee1f06472f 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8ce0263956 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 9896b09187 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new f9cda8b53d 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new e2497635d6 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 718340db6d 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new e4d0091f1a 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new c4e939ccdc 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 8fb8eb20c1 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 2b72972ab3 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 5bf589960f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 2b51fa825c 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 91e9dc1b92 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 0e67292bfa 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 5146909fec 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 65209e3570 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 3fce8f0bb1 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new d7f0d95ff6 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 2a83bf3948 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 863b4e7d3f 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new cfca03ac96 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 3ae361ec86 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 12f3139091 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 4737169b2f 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new ff45d4dd0e 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 66f3702bd1 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new d51912be7e 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9bf3e6966b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new c4041b3df1 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 96217d87d3 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 4a645a6937 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 2b913541bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 06802b26ce 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 239561d921 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 948182d27e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 5f567ff387 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 56b71cc174 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 6f2113dc02 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 721da442fc 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 65ec1ecefb 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new cbb9002364 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 403fb345cf 127: force: #27: : Failure after baseline build: no new commits new 5ea5124fbd 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 2de6892a3f 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 2fd6fa1095 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 54b2247d31 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new e0d42a95d5 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 56fa53fab8 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 00de714586 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new f801d7b7c8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 20c1b6f6ce 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new eccdedaafe 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4e4cd20606 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 7246e804d1 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a31c633ee2 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new e5599487da 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 787c720605 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 612e08bc68 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 779a97f157 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 1f4b02d1bf 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new beca849a97 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 986dff0c57 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new d721c26e1c 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 3cd2f4fe14 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new eb9d9b43fc 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 02068a38e6 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (4de8f2cb15) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 2244 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 35380 -> 35216 bytes 04-build_abe-gcc/console.log.xz | Bin 203164 -> 203324 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8716 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 241168 -> 240592 bytes 08-build_abe-gdb/console.log.xz | Bin 34948 -> 34860 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3160 -> 3108 bytes 11-check_regression/console.log.xz | Bin 1952 -> 1292 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 64 ++++++++++----------- dashboard/dashboard-generate.sh | 17 ------ dashboard/dashboard-push.sh | 7 --- .../squad-vs-first/score/results-functional.json | 1 - git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 7 --- jenkins/notify.sh | 2 +- {11-check_regression => mail}/results.compare | 4 +- manifest.sh | 36 ++++++------ sumfiles/gdb.log.xz | Bin 14408 -> 14432 bytes sumfiles/gdb.sum | 4 +- 28 files changed, 64 insertions(+), 98 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100755 jenkins/dashboard-push.sh copy {11-check_regression => mail}/results.compare (72%)