Quoting Santiago Vila (2018-11-29 16:55:53) > > > I'd like those three logs to have the same timestamp. > > Okay. Why? > Because that way I can use the timestamp as an "id" for everything which > happened in the build. For example, when I "expire" a build log because the > package used to ftbfs but not anymore, I would also expire the log storing > memory usage.
[see below]
> > > Also, because some packages FTBFS randomly and in those cases I want to
> > > know how randomly they fail, sometimes I tell my autobuilders to build
> > > the same package over and over again.
> > >
> > > Because of this I'd also like to use sub-second precision, to avoid
> > > several build logs to have the same filename.
> >
> > I think I don't understand something here. How would two build logs have
> > the same file name with second-precision but not the same file name with
> > sub-second-precision?
> Good question :-)
>
> I have a "poor's man" client-server setup where autobuilders ask for build
> jobs and they receive a tuple containing package, version, distribution and
> "build mode" (A or B) as a result.
>
> I have recently changed the setup so that they also receive the timestamp to
> be used from the central server. Currently I have an ugly "sleep 1.5" in the
> coordination server (between succesive jobs) which I would like to either
> reduce or remove.
[see below]
> > > So, what I would really need is a way to provide the timestamp
> > > externally.
> > Do you? Why not just put the build logs into two distinct directories?
> In my setup all the build logs are sent to the central server to be stored
> there in a single directory for every distribution and build mode. For
> example, In ~/logs/A/buster have around 80000 build logs for build logs of
> type "dpkg-buildpackage -A" in buster.
>
> I could perhaps add the hostname as a suffix, but the filename is already
> long enough and I would prefer not to make it even longer.
As far as I now understand it, you are requesting this change in sbuild because
you have your tools and scripts which you want to work in a certain way
("abuse" timestamps as an id, ugly sleep, single directory) and as a result of
these design choices of your tools, you need sbuild to change.
What you have to convince me of now is:
Why does sbuild need to change because of design choices that you made in your
scripts and why should not your scripts change to accommodate for the sbuild
behaviour?
As I see it, you could simply put all build logs with the same "id" in the same
directory and thus have one directory per "id". Then you could drop your "ugly
sleep", sbuild could keep its build log filenames and no special suffix would
be needed.
Thanks!
cheers, josch
signature.asc
Description: signature
