This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards fdddd83b18 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards 341c752346 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 6465eeb40f 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards bf11229c83 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards a3268e3022 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 45af7d9c93 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards f0d5abd93d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards aee68c2909 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 38192afb8c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 9bddddfed4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 1fb49a3338 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards d7757529b3 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 1fe5c14875 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards bc34a3d587 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards ceb710b284 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards d3e32e9e9d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 07b142f727 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 610198ffd6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 864a30f996 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 0e2eb65e15 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 16873edb3d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards eaea25eb08 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards 0a52c1fe29 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 08824f263a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 28ad8dc67a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 70ed1dc412 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 17accf1c67 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 663d36c02f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 668a7f572f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards bd675a7617 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards c38061eb83 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 2081dd6f3f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 1bb151a3b8 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards dc0a2af762 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 3ff1f9612a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 8b6a027c87 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 23513fe457 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 43a94fd0be 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards dbf0b00930 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards f4d16ac7f1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cc9244b668 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards b22c0934c8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards f5e03569e3 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards c9adac6c8e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 14f0c62547 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards fbaca7098b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 45e0bb8537 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards bab047de63 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 391ff87ca8 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 62e65779ce 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 1f2c6712d6 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards d9ca5b1549 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards ea23b99598 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards ee931eaa34 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 163716f1c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 537131e932 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e41a828cda 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 919ef023bf 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 9c0bf617ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards a16ece18bb 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards fddd578b81 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards fed893d09e 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 5738ca7a65 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards ce69c45304 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 2f21bb2960 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 91af0dc10b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards d1d919b683 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards e95969cc65 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 77a0b02ea6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards e1f38025b0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 9baa537f07 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 072f292963 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 94cd22429f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 0bbd8ae00a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 9daf822009 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 63ff90cecf 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 2a10daf59b 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 57c6dfcc10 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards feefe0c5d2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 64fb764095 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards f1293e1326 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards c5a9916b3a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 3dbdfbfc84 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 3ee3542d02 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards ef23e7a638 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards cab0192ab7 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 7b526a597a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 1b51018008 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 3df57840dd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards 86aff461d5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 6008c34a39 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards 3ad66e9dc4 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards df87fd8aed 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 16b2db05f9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 7489f8c940 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards fb0045793d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards cd3b913149 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards fe0edc8d57 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards 3e2f993b13 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 577c7a1d3a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards ad882a7288 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new a9805542f1 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new a1732d6cf7 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new d414d3521d 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 7372a98817 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 5d94fc31d7 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new bc33abf3b9 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 21a2fa0bb4 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 7dce54457a 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new fd44527db6 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 51839bd901 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 1039835a18 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 41937fa279 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new abdf740172 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new ea5621bc36 290: onsuccess: #2106: 1: Success after gcc: 2 commits new bd58d99680 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new f4a5d72353 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new d0f427ced4 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new a5b8023dfb 294: onsuccess: #2110: 1: Success after gcc: 17 commits new b408a9c122 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 276edc757b 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new fbb98a25ee 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 00b9191c96 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new b23e237f1e 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 231d7418db 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 6888b1113f 301: onsuccess: #2118: 1: Success after linux: 16 commits new 5cc758082c 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 25f3f36f6f 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 0d8c07ed1b 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 557c1eeae1 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 1485be483c 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new be1edbe023 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 7993633fa8 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 48b4416400 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new a90373dbf6 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 72c55177b3 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 0d36126bc0 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 8a2361598b 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 52de6e8e86 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 3ad68994b5 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new fbe1e83bb2 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new b8cb619577 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new f8344d9ccd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new cea98f80f7 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 924f2ebd55 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 675582e8e3 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new b6c0fb8a5d 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new a364ff87c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 0b3b2a7f59 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 0ca8e9afbb 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 6910372d60 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 36b48a3d58 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 9a9fddfce9 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 6764ccb533 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new eece2b41d8 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 7b10a1b24c 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 36e5de135a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new fcdba547e7 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new 63b8f2397f 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 144fd92bd4 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new d7785f3eb5 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new c7cea911f8 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f22b5e969c 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new 5b2a0b2b32 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 1064f3a585 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 338097f4f8 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new c4e4201987 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 2c321e6472 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 2ba2b9a755 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 107101cb6e 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 0c1929bc36 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 600310fad0 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 6be4595c31 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 7977b4dd28 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 1ea4608daa 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new d5453f4e97 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 40aa965579 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 815b9ad4a7 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 2dc0bc7f00 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new ffcfed9697 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 8221317a8c 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 5f1a95bb95 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 759b53648d 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new ef4d0c7489 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new feba6cd4b7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 72664b79ec 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 88d3b912e2 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 85ce46e7d6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 079cb0d983 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new a2d056110f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new b7b62ed6a4 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new c89eec8b3f 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 03785b8f06 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 7b3b77a1be 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new b1d037d59a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 422216bd52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7dc2c11131 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 1aed2f1f9e 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new e98e997d12 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new e03a6442ee 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 3a4bf55be9 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 435c31d82e 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 6c842f4f59 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits
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 (fdddd83b18) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1816 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31228 -> 31720 bytes 04-build_abe-stage1/console.log.xz | Bin 91988 -> 91380 bytes 06-build_abe-linux/console.log.xz | Bin 8908 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 236880 -> 237984 bytes 08-build_abe-stage2/console.log.xz | Bin 229236 -> 230488 bytes 09-build_abe-gdb/console.log.xz | Bin 38608 -> 39204 bytes 10-build_abe-qemu/console.log.xz | Bin 32128 -> 32044 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2672 -> 2696 bytes 13-check_regression/console.log.xz | Bin 5804 -> 5544 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 7 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 10 +- 13-check_regression/results.compare2 | 36 +- 13-check_regression/results.regressions | 27 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 - sumfiles/g++.log.xz | Bin 2672236 -> 2677324 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 2202476 -> 2211628 bytes sumfiles/gcc.sum | 2398 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 898476 -> 895252 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214544 -> 214436 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438060 -> 445088 bytes sumfiles/libstdc++.sum | 36 +- 41 files changed, 1386 insertions(+), 1432 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions