| [Coke] | 18% | 00:13 | |
| (I said 5 hours, but it's more like 8, oops) | 00:24 | ||
| ugexe | probably worth trying to figure out which ones take the most time to test at some point, although i imagine they are just things with a whole lot of tests | 00:27 | |
| [Coke] | can probably get that to be part of the status report at the end. | 00:30 | |
| 30% | 00:41 | ||
| 60% | 01:59 | ||
| (can't fudge on OS) guessing it just needs a fudge tweak | 02:01 | ||
|
02:21
spimmo joined
03:04
spimmo left
|
|||
| [Coke] | 85%. heading to sleep | 03:42 | |
| ugexe | as my going to bed thought i do wonder if we should wait another week given today seems to be one of the first times anyone has outside of the core has tried to test their stuff with rakuast and some of those things already have fixes available. on the other handle it'll probably just be the same situation next week, just different problems and fixes :) | 03:50 | |
|
03:51
spimmo joined
03:52
spimmo left
03:53
spimmo joined
|
|||
| ShimmerFairy | I don't think there's getting around some level of breakage as people get swapped over to rakuast for the first time, no matter how long you wait. About the only thing I could think of doing about it, if it was *truly* necessary, is a temporary modification to compiler errors to mention rakuast as a potential cause. | 03:53 | |
|
03:53
spimmo left
|
|||
| ShimmerFairy | But I think if the ecosystem tests say it's mostly fine, then people will have a mostly seamless experience themselves. | 03:54 | |
|
03:54
spimmo joined
03:55
spimmo left
06:01
kjp left
06:20
kjp joined
|
|||