On Tuesday 2016-09-27 20:18 +0100, James Graham wrote: > I think this argument is backwards. Today we don't run a recent copy of the > CSS tests because there are technical issues preventing it from working with > the reftest harness. It is not clear to me why this reorganisation would > suddenly cause us to fix those issues when we could have done at any > previous time with similar effort.
Because you were doing the work on the approach that uses your test harness, and we didn't have anybody assigned to do the other work? > On the other hand the change will allow > us to run a copy of the CSS tests in wptrunner immediately for "free". > Running more tests in wptrunner inevitably increases the chance of fixing > issues with that harness both because it will be easier to prioritise the > work and more people will be motivated to fix the issues. I think running a large number of reftests in wptrunner will be an unacceptable load on our CI infrastructure due to https://bugzil.la/1265586 . > Apologies for missing the bugs you pointed to at the time; I believe one of > them has a solution and I will need to investigate the second issue (with > debugger-related bugs I find it very helpful to get a set of steps to > reproduce the problem). I think those bugs are the very tip of an iceberg that involves many person-months of work. -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
signature.asc
Description: PGP signature
_______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
