Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Apr 2021 16:48:31 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   https://artifact.ci.freebsd.org/snapshot/stable-13/?C=M&O=D messed up dates and HASHID-only use make things extremely hard to find "in time order"
Message-ID:  <8040795F-79D5-41D3-8BFF-206C67B76CD2@yahoo.com>
References:  <8040795F-79D5-41D3-8BFF-206C67B76CD2.ref@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Using an example to illustrate problems finding artifacts,
the problems not being limited to the example's specifics.

I have historically used https://artifact.ci.freebsd.org/snapshot/
to do build-less approximate bisecting (and other things). Such
use is very messed up since the git-related URL conventions
chosen were put in place. The below illustrates an example
of the mess for how things are currently presented.

https://artifact.ci.freebsd.org/snapshot/stable-13/?C=3DM&O=3DD

lists ac845558f7b626d9a31b8f6dab686c45d39dc5a0/ as having
date/time 2021-Apr-10 18:43 .

But:

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/?C=3DM&O=3DD
lists:

powerpc/ and arm/ as having date/times 2021-Apr-10 18:54 and 2021-Apr-10 =
18:50
yet lists...
i386/ and arm64/ as having date/times 2021-Feb-19 19:00 and 2021-Feb-19 =
18:50 .

But it gets worse:

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/powerpc/?C=3DM&O=3DD

shows an empty directory. Same for:

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/arm/?C=3DM&O=3DD

By contrast,

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/i386/?C=3DM&O=3DD

shows i386/ with date/time 2021-Apr-10 18:43 but

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/i386/i386/?C=3DM&O=3DD

shows all the file dates as 2021-Feb-19 19:00 .

Going back to arm64/ I find a similar 2021-Feb-19 dating,
although 21021-Feb does show up in more places:

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/arm64/?C=3DM&O=3DD

shows aarch64/ with date/time 2021-Feb-19 18:50 and

=
https://artifact.ci.freebsd.org/snapshot/stable-13/ac845558f7b626d9a31b8f6=
dab686c45d39dc5a0/arm64/aarch64/?C=3DM&O=3DD

shows the files also having the date/time 2021-Feb-19 18:50 .


In my view the choice to only use the hash-id for the commit
in the url is a usability mistake and the url prefix should
be of a form more like (for this example context):

https://artifact.ci.freebsd.org/snapshot/stable-13/n??????-HASHID/

where the ?????? is from:

git rev-list --first-parent --count

(as used elsewhere by FreeBSD).

(The HASHID might be just the 12 character prefix instead of the
whole hash-id as well.)

Such a convention would be more independent of dates possibly
being touched on the file server and would make time ordered
finding of things (such as for build-less approximate bisecting)
far more reasonable.



=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8040795F-79D5-41D3-8BFF-206C67B76CD2>