On Fri, Mar 26, 2021 at 11:35:02AM +0100, Andrea Bolognani wrote: > We should always pass --werror and display the contents of the > log file in case of failure. > > Signed-off-by: Andrea Bolognani <abologna(a)redhat.com&gt; > --- Reviewed-by: Erik Skultety <eskultet(a)redhat.com&gt;

On Fri, Mar 26, 2021 at 05:11:04PM +0100, Andrea Bolognani wrote: > Even though you didn't spell that out explicitly, I assume you're > okay with me pushing this series during the freeze? I know it's trivial and most likely will not affect the release at all but my understanding of freeze is that we try to stabilize the build by fixing bugs or any issues that would prevent us to deliver the final release. To me that sounds like reasonable definition that we should try to follow and in my mind creates a clear decision process if something should/can be pushed during freeze. Based on that definition I would say that these patches does not qualify and can easily wait once the release is done.

On Fri, 2021-03-26 at 17:00 +0100, Erik Skultety wrote: > On Fri, Mar 26, 2021 at 11:35:02AM +0100, Andrea Bolognani wrote: > > We should always pass --werror and display the contents of the > > log file in case of failure. > > > > Signed-off-by: Andrea Bolognani <abologna(a)redhat.com&gt; > > --- > Reviewed-by: Erik Skultety <eskultet(a)redhat.com&gt; Even though you didn't spell that out explicitly, I assume you're okay with me pushing this series during the freeze?

On Fri, Mar 26, 2021 at 11:35:02AM +0100, Andrea Bolognani wrote: > We should always pass --werror and display the contents of the > log file in case of failure. Any reason why the lines are not in one place? What I did in libnbd (first draft, still up for review) is that I just took all the lines of the script and put them inside `ci/build_script.sh` with only the most basic conditionals to accommodate various types of runs. That way common things are in one place. It could take a parameter (like what ninja target to run) and you can run things after that (like `website` and `potfiles` jobs do. Just an idea.

On Thu, Apr 01, 2021 at 03:43:11PM +0200, Andrea Bolognani wrote: > On Wed, 2021-03-31 at 23:31 +0200, Martin Kletzander wrote: > > On Fri, Mar 26, 2021 at 11:35:02AM +0100, Andrea Bolognani wrote: > > > We should always pass --werror and display the contents of the > > > log file in case of failure. > > > > Any reason why the lines are not in one place? What I did in libnbd > > (first draft, still up for review) is that I just took all the lines of > > the script and put them inside `ci/build_script.sh` with only the most > > basic conditionals to accommodate various types of runs. That way > > common things are in one place. It could take a parameter (like what > > ninja target to run) and you can run things after that (like `website` > > and `potfiles` jobs do. Just an idea. > > As is often the case, the raisins are mostly hysterical ;) > > I think the initial idea was to keep things as simple as possible, > but I agree with you that when you have seven (!) build recipes, most > of which are almost identical, it makes sense to think about > consolidating them to a single location. > So I took a look at the consolidation. I went through few iterations after which I ended with two scripts, one that does the meson part and one that does the ninja part. The first one does not need to take any parameters, the other one would be nice if it took one, that's enough. What's weird about it is the way I think of it. The most understandable way would be a `configure` that runs `meson ...` and then another one, which runs `ninja ...` with parameter(s). At that point you can make the second one a Makefile and just do: ./configure make most of the time. But because we can just put the configure part into the makefile we can also just have a makefile that does all of it. It might sound stupid, but it is the easiest way how to provide few targets without extra scripting and everything around it. On the other hand it feels weird just suggesting that, although I cannot pinpoint why that is. Maybe that it would be too controversial? At this point I honestly do not know whether I went too far or it actually makes sense and I am not capable of recognising the difference.

On Thu, Apr 08, 2021 at 11:39:55AM +0100, Daniel P. Berrangé wrote: > On Thu, Apr 08, 2021 at 12:32:10PM +0200, Martin Kletzander wrote: > > On Thu, Apr 01, 2021 at 03:43:11PM +0200, Andrea Bolognani wrote: > > > On Wed, 2021-03-31 at 23:31 +0200, Martin Kletzander wrote: > > > > On Fri, Mar 26, 2021 at 11:35:02AM +0100, Andrea Bolognani wrote: > > > > > We should always pass --werror and display the contents of the > > > > > log file in case of failure. > > > > > > > > Any reason why the lines are not in one place? What I did in libnbd > > > > (first draft, still up for review) is that I just took all the lines of > > > > the script and put them inside `ci/build_script.sh` with only the most > > > > basic conditionals to accommodate various types of runs. That way > > > > common things are in one place. It could take a parameter (like what > > > > ninja target to run) and you can run things after that (like `website` > > > > and `potfiles` jobs do. Just an idea. > > > > > > As is often the case, the raisins are mostly hysterical ;) > > > > > > I think the initial idea was to keep things as simple as possible, > > > but I agree with you that when you have seven (!) build recipes, most > > > of which are almost identical, it makes sense to think about > > > consolidating them to a single location. > > > > > > > So I took a look at the consolidation. I went through few iterations > > after which I ended with two scripts, one that does the meson part and > > one that does the ninja part. The first one does not need to take any > > parameters, the other one would be nice if it took one, that's enough. > > What's weird about it is the way I think of it. The most understandable > > way would be a `configure` that runs `meson ...` and then another one, > > which runs `ninja ...` with parameter(s). > > > > At that point you can make the second one a Makefile and just do: > > > > ./configure > > make > > > > most of the time. But because we can just put the configure part into > > the makefile we can also just have a makefile that does all of it. It > > might sound stupid, but it is the easiest way how to provide few targets > > without extra scripting and everything around it. On the other hand it > > feels weird just suggesting that, although I cannot pinpoint why that > > is. Maybe that it would be too controversial? > > > > At this point I honestly do not know whether I went too far or it > > actually makes sense and I am not capable of recognising the difference. > > I've not looked back at the full thread, but I'd say that if the answer > to any problem involves the words "configure" or "make", then we're > likely approaching the problem in the wrong way, because we're really > supposed to have removed use of make and autotools (or anything that > pretends to look like a configure script), > It's only the name that suggested this, it could've been a `ci/build_script.sh`, I just used the name because it, of course, reminded me of the old ways. Basically the whole point of this is to have the line: meson build --werror $MESON_OPTS || (cat build/meson-logs/meson-log.txt && exit 1) only written in one place, and possibly similarly with some ninja invocations. It would be almost exclusively used by the CI, although it could be also useful for some people.