Joseph Wright comments

Results 1009 comments of


                                            Joseph Wright

Ideas about splitting slow `l3build check/doc` into smaller even runs

@davidcarlisle Stlll comes down to what interface we want: thoughts?

Ideas about splitting slow `l3build check/doc` into smaller even runs

> [@josephwright](https://github.com/josephwright) I thought `l3build --pattern '^[a-m]' ` which would just insert an `if(name:match('^[a-m])` ooh more or less exactly where you have `excludetests` /`includetests hm maybe just need to be...

Ideas about splitting slow `l3build check/doc` into smaller even runs

That's something like `--next`?

Output normalization hook

I think before doing this we maybe should refactor the normalisation code anyway. We used to worry about long lines, but the 'plan' has changes so we run with a...

Output normalization hook

> > We used to worry about long lines, but the 'plan' has changes so we run with a very large line length and avoid that. > > But that's...

Output normalization hook

OK, do we want to provide extra normalization on a per-line basis or for the whole of the 'content'? I guess I favour for a single line: so we'd have...

Output normalization hook

I'm not sure about `hook` here as I _think_ we want to take the content (or line) as an argument.

Output normalization hook

@cfr42 Why would it need to come before? In the other issue, you give the example of the string `(SVN Rev: 10946)`, which we could search and replace with e.g....

Output normalization hook

> because pgf just puts e.g. `(3.8.1)` and that seems dangerously generic ... OK, `pgf` has something like ``` Package: pgfrcs 2023-01-15 v3.1.10 (3.1.10) ``` in the raw log, which...

Output normalization hook

I'm not seeing really how normalising before the standard run would help here - you still need to look for more-or-less the same stuff, and done at the end, you...