Re: CFT for vendor openzfs - week 5 reminder + memdisk images

On Sat, 15 Aug 2020 at 21:30, Matthew Macy <mmacy_at_freebsd.org> wrote:
>
> >
> > Hi. I have some problems downloading the amd64 image:
> >
> > baymax /home/djn > fetch -a
> > https://people.freebsd.org/~freqlabs/freebsd-openzfs/latest/freebsd-openzfs-amd64-2020081100-memstick.img.xz
> > freebsd-openzfs-amd64-2020081100-memstick.img. 19% of  655 MB 2179 kBps 04m07s
> > fetch: freebsd-openzfs-amd64-2020081100-memstick.img.xz appears to be
> > truncated: 134152192/687158140 bytes
> > baymax /home/djn > fetch -ar
> > https://people.freebsd.org/~freqlabs/freebsd-openzfs/latest/freebsd-openzfs-amd64-2020081100-memstick.img.xz
> > freebsd-openzfs-amd64-2020081100-memstick.img. 20% of  655 MB  882 kBps 09m10s
> > fetch: freebsd-openzfs-amd64-2020081100-memstick.img.xz appears to be
> > truncated: 139132928/687158140 bytes
> > baymax /home/djn > fetch -ar
> > https://people.freebsd.org/~freqlabs/freebsd-openzfs/latest/freebsd-openzfs-amd64-2020081100-memstick.img.xz
> > freebsd-openzfs-amd64-2020081100-memstick.img. 20% of  655 MB  647 kBps 12m23s
> > fetch: freebsd-openzfs-amd64-2020081100-memstick.img.xz appears to be
> > truncated: 142065664/687158140 bytes
> > baymax /home/djn >
> >
> > It also fails using Firefox on windows on a different machine. (It's
> > also much slower from that machine, about 200 kB/sec. I have no idea
> > if that's relevant.)
>
> Yes, this appears to have been going on for at least the last week.
> The FreeBSD infrastructure directly available to developers appears to
> be unreliable for serving large files. Individuals with accounts on
> freefall have been able to scp the files. It's possible that we may
> just end up sharing images more widely by way of releng generated
> images after commit. I'll see if there's an alternative for the last
> week of the CFT.
>
> Cheers.
> -M

The instructions for building it myself seem easy enough, so it's not
a problem for *me* -  but I'm sure it can't hurt. :)

Thanks,
-- 
Daniel Nebdal