Re: amdgpu panics

[Grzegorz Junka]

On 06/04/2020 22:08, Tatsuki Makino wrote:

Sorry, I derail from this topic.

I have cloned the host to poudriere with the following command.

poudriere jail -c -j src -m 'src=/usr/src' -v `make -C /usr/src/release/
-V VERSION VERSION=\$\{REVISION:Q\}-\$\{BRANCH:Q\}`

Since the name of this jail is src, create src.conf as follows.

ln -s /etc/src.conf /usr/local/etc/poudriere.d/src-src.conf

Probably, this reproduces the same environment as the host... maybe :)



Just trying this now. Poudriere's help says that -v only makes sense for 
method ftp and svn. For other methods, especially for src that you are 
using, the value is only for display.


Also, I don't think specifying src.conf for jail created with method src 
makes sense? It assumes that the world and kernel is already build. I 
would expect this to only take any effect when creating with -b or with 
method svn?


GrzegorzJ


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

Summing up the time cost for a clean svn co and make buildkernel
buildworld release is around 75minutes while the chroot build with
release(7) is around 100minutes for my hardware setup. Builds using
make are more reasonable for driver fixes because then I can only
rebuild small part of the code which will result in much shorter build
times. Very nice to experience :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

On Wed, Apr 8, 2020 at 8:19 PM Ruslan Garipov wrote:
> > I need to see how it works with `make release` :-)
> This is what I meant when saying "you can build the source tree for
> 13.0-CURRENT on 12.1-RELEASE"; sorry if I've confused you.

No worries, my little confusion came from `make release` being a bit picky:
1. I need to buildworld first (can use -j switch, make release will
not call it).
2. I need to buildkernel first (can use -j switch, make release will
not call it).
3. Only then I can run `make release` (cannot use -j switch).

I get as good result as I need with memstick and iso images in around
19 minutes plus I can build CURRENT that way.. now I may be ready to
cross-compile :-)

3858.923u 331.683s 19:19.24 361.4%  171+561k 499674+1215072io 131833pf+0w


> Check ``Building with release.sh on -STABLE'' thread[1] on the forum.
> May be it can help you.

Thank you for the reference! :-)


> "2h looks really cool" because release(7) may build chrooted build
> environment, where it then may build port(s) and builds the target.  My
> Xeons usually spends 1.5 hours on clean release(7) (with 16 make(1)
> jobs).

A bit better but very similar result, thanks for reference.. and the
SSD hint :-)

With this power I can compile a clean firmware for my projects based
on ARM mbedOS  in 2 minutes instead 12 minutes (as compared to laptop
build) and connect the build to a git hook.. then speeding up a bit
could return a binary right away as a result of git push :-) :-)

In a free moment it would be fun to play with FreeBSD on ARM.. I have
tried that several times before but with no luck.. and I really have
different boards around to test :-)

Again GREAT THANK YOU Ruslan for your time support and all hints!! :-)

Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: amdgpu panics

[Hans Petter Selasky]

Hi,

drm-fbsd12.0-kmod

--HPS
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Porting of Smallstep CA

[Markus Wipp]

> On 8. Apr 2020, at 03:34, Adam Weinberger  wrote:
> 
> On Tue, Apr 7, 2020 at 2:08 PM Markus Wipp  > wrote:
>> 
>> Hi all,
>> 
>> I would like to create a port of the CA tool (basically two ports: cli and 
>> certificates) found on
>> https://github.com/smallstep
>> https://smallstep.com/
>> 
>> What I tried so far was:
>> 1) make it on my machine without the ports infrastructure. This basically 
>> works fine and without any errors and modifications needed ( I just do a 
>> gmake bootstrap and then a gmake build )
>> 2) tried to create a port using the guide at 
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html
>> 3) tried Slow porting, but I think I’m not really understanding how and 
>> where to begin
>> 
>> The main issue is, that I don’t really know what I have to do here, to 
>> achieve what’s required to correctly build the port.
>> It is the very first time I’m trying to create a port.
> 
> Hi Markus,
> 
> You're on the right track here. The next step is that none of the
> stuff where go fetches a remote module can happen. All packages on the
> cluster (and the vast majority of end-user-built sets) are built using
> poudriere (ports-mgmt/poudriere), which shuts down all external
> traffic during builds.
> 
> The port needs to specify all dependent modules. Take a look at
> another go port, like www/gohugo for an idea of how this works.
> net/geoipupdate is similar to what you're doing, where it needs go
> modules, but is built with gmake.
> 
> You're misusing a couple constructs, but if you copy the framework in
> geoipupdate and gohugo you'll resolve most of them (also, define
> NO_WRKSUBDIR instead of setting WRKSRC=WRKDIR).
> 
> I'm not sure where golint is entering in, but it needs to not be
> there. Linting is for upstream developers, and has no purpose for
> end-user builds.
> 
> Does that help to get you started?
> 
> # Adam

Hi Adam,
Hi all others,

First go all a big thank you for all your tips and helpful suggestions so far!

I think I’m a top closer, but still have some issues. Would be great if you 
could have a look again and give me some hints about what I’m doing wrong.

This is my reworked makefile:

# $FreeBSD $

PORTNAME=   smallstep-cli
DISTVERSIONPREFIX=  v
DISTVERSION=0.14.0-rc.5
DISTNAME=   cli
CATEGORIES= security
DIST_SUBDIR=${PORTNAME}

MAINTAINER= mw@wipp.bayern
COMMENT=Smallstep step-ca command line client

LICENSE=APACHE20
LICENSE_FILE_APACHE20=  ${WRKSRC}/LICENSE

USES=   go

USE_GITHUB= yes
GH_ACCOUNT= smallstep
GH_PROJECT= cli
#GH_SUBDIR= cli-0.14.0-rc.5


MAKE_ENV+=  GOPATH=${WRKDIR}

BUILD_DEPENDS=  go>1:lang/go \
bash>5:shells/bash \
curl>7:ftp/curl


GH_TUPLE=   \

AndreasBriese:bbloom:e2d15f34fcf9:andreasbriese_bbloom/vendor/github.com/AndreasBriese/bbloom
 \

BurntSushi:toml:v0.3.1:burntsushi_toml/vendor/github.com/BurntSushi/toml \

Masterminds:goutils:v1.1.0:masterminds_goutils/vendor/github.com/Masterminds/goutils
 \

Masterminds:semver:v3.0.1:masterminds_semver/vendor/github.com/Masterminds/semver/v3
 \

Masterminds:sprig:v3.0.0:masterminds_sprig/vendor/github.com/Masterminds/sprig/v3
 \

Microsoft:go-winio:v0.4.14:microsoft_go_winio/vendor/github.com/Microsoft/go-winio
 \

OpenPeeDeeP:depguard:v1.0.1:openpeedeep_depguard/vendor/github.com/OpenPeeDeeP/depguard
 \

ThomasRooney:gexpect:5482f0350944:thomasrooney_gexpect/vendor/github.com/ThomasRooney/gexpect
 \

asaskevich:govalidator:475eaeb16496:asaskevich_govalidator/vendor/github.com/asaskevich/govalidator
 \
beorn7:perks:v1.0.1:beorn7_perks/vendor/github.com/beorn7/perks 
\

bgentry:speakeasy:v0.1.0:bgentry_speakeasy/vendor/github.com/bgentry/speakeasy \

bombsimon:wsl:v2.0.0:bombsimon_wsl/vendor/github.com/bombsimon/wsl/v2 \

boombuler:barcode:v1.0.0:boombuler_barcode/vendor/github.com/boombuler/barcode \

cespare:xxhash:v2.1.1:cespare_xxhash/vendor/github.com/cespare/xxhash/v2 \
cheggaaa:pb:v1.0.28:cheggaaa_pb/vendor/gopkg.in/cheggaaa/pb.v1 \

chzyer:readline:2972be24d48e:chzyer_readline/vendor/github.com/chzyer/readline \
coreos:bbolt:v1.3.3:coreos_bbolt/vendor/github.com/coreos/bbolt 
\
coreos:etcd:v3.3.18:coreos_etcd/vendor/github.com/coreos/etcd \

coreos:go-semver:v0.3.0:coreos_go_semver/vendor/github.com/coreos/go-semver \

coreos:go-systemd:95778dfbb74e:coreos_go_systemd/vendor/github.com/coreos/go-systemd
 

Re: amdgpu panics

[Grzegorz Junka]

On 07/04/2020 11:18, Hans Petter Selasky wrote:

On 2020-04-07 12:09, Grzegorz Junka wrote:

Is it expected that drm doesn't work on 12.1-RELEASE


Yes, for now.

You can diff:

/usr/src/sys/compat/linuxkpi

Between the two to see the differences.


Once I install kernel/world from stable-12 branch should I compile and 
install drm-fbsd12.0-kmod or drm-devel-kmod?


GrzegorzJ

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Ruslan Garipov]

On 4/8/2020 9:05 PM, Tomasz CEDRO wrote:
> On Sun, Apr 5, 2020 at 7:53 PM Ruslan Garipov wrote:
>>> I wrongly assumed that release will simply update this svn repo that I
>>> am working on.. but it fetches HEAD.. so I was trying to build
>>> 13/HEAD/CURRENT on 12/STABLE/RELEASE that have different ABI thus bad
>>> syscall.. and I need CURRENT to build CURRENT, right? :-)
>> I believe in order to build the source tree you just need a compatible
>> toolchain.  So you can build the source tree for 13.0-CURRENT on
>> 12.1-RELEASE system.  But you need CURRENT to **run** userland with ABI
>> from the CURRENT.
> 
> Long story short I need 13-CURRENT to create a 13-CURRENT release with
> release(7) because on 12-STABLE/RELEASE chroot with 13-CURRENT does
> not work.
Of course, because release(7) runs built userland; in your case it runs
userland with FreeBSD 13 ABI on FreeBSD 12.x host.

> I need to see how it works with `make release` :-)
This is what I meant when saying "you can build the source tree for
13.0-CURRENT on 12.1-RELEASE"; sorry if I've confused you.

Check ``Building with release.sh on -STABLE'' thread[1] on the forum.
May be it can help you.

> 
> 
>> Once again: for native build `make release` may be quite easy and fast.
>> release(7) guarantees "absolutely clean build environment".
> 
> Will try that `make release` as well, also for 13-CURRENT on
> 12-STABLE, thank you! Also will compare the time cost with the one
> presented below :-)
> 
> 
> Creating a "release" also has this advantage that I have memstick
> images that I can boot from directly, test what I need, even no need
> to install :-)
> 
> Here are my build times, for a release for AMD64/12-STABLE, I did not
> select DOC nor PORTS to build, only Kernel and Base :-)
> 
> BUILD HOST (~$500): HP PROLIANT DL380G7X (HDD 1TB, 128GB RAM, 24vCPU =
> 2 x Intel Xeon X5660 @2.8GHz = 2 PACKAGES x 6 CORES x 2 HW THREADS )
> INTERNET: 600/60MBit
> 
> time make clean buildkernel (16x speedup with SMP):
> 2472.027u 291.657s 46:34.54 98.8%   38592+3123k
> 195123+3315182io 80167pf+0w
> -j122355.140u 282.807s 3:40.12 1198.4%  38509+3121k
> 190142+3361605io 71356pf+0w
> -j243672.641u 382.254s 2:54.85 2319.0%  39837+3149k
> 218567+3361605io 64857pf+0w
> -j483722.707u 352.940s 3:07.10 2178.3%  40328+3169k
> 214359+3361607io 66526pf+0w
> 
> time make clean buildworld (12.5x speedup with SMP):
> 32223.598u 1940.942s 9:28:07.59 100.2% 46920+3430k
> 563493+3074126io 234706pf+0w
> -j1233644.438u 1818.147s 54:46.68 1078.9% 47324+3449k
> 485257+3255853io 236896pf+0w
> -j2450728.732u 2556.953s 45:06.66 1968.6% 47556+3455k
> 560905+3255862io 229433pf+0w
> -j4851129.166u 2454.564s 44:38.12 2000.7% 47630+3458k
> 525602+3255854io 210237pf+0w
> 
> release.sh (seems to auto-adjust -j optimization and below 2h looks
> really cool):
Yes, release(7) sets number of make(1) jobs to the number of available
CPUs (hw.ncpu) for buildworld target, and half of that number for
buildkernel one.

"2h looks really cool" because release(7) may build chrooted build
environment, where it then may build port(s) and builds the target.  My
Xeons usually spends 1.5 hours on clean release(7) (with 16 make(1)
jobs).

> 94556.462u 5583.273s 1:43:14.24 1616.6% 50234+3336k
> 1457023+16921354io 615421pf+0w
> -j12   94477.001u 5577.692s 1:42:59.60 1619.1% 50251+3337k
> 1463964+16932952io 617689pf+0w
> -j24   94480.274u 5574.117s 1:43:38.89 1608.8% 50213+3336k
> 1468685+16931170io 617425pf+0w
> -j48   94588.653u 5569.909s 1:43:10.62 1617.9% 50211+3336k
> 1460546+16925145io 611229pf+0w
> 
> These times may be even smaller when SSD is used instead of HDD.
For me it almost changed nothing, only CPU resources counted.

> Also
> I wonder how to utilize all RAM to speed up the compilation because I
> can see 8..34GB utilization while the rest of 128GB remains unused.
By installing additional CPU(s) which will allow you to run more make(1)
jobs in parallel.  My -j16 builds consume about 16-18 GB (at peaks).

> I
> saw some ramdisk tricks I need to try that as well :-)
> 
> Best regards :-)
> Tomek
> 

[1]
https://forums.freebsd.org/threads/building-with-release-sh-on-stable.70889/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /usr/src/release/release.sh -> ports -> fetch pkg -> Bad system call (core dumped)

[Tomasz CEDRO]

On Sun, Apr 5, 2020 at 7:53 PM Ruslan Garipov wrote:
> > I wrongly assumed that release will simply update this svn repo that I
> > am working on.. but it fetches HEAD.. so I was trying to build
> > 13/HEAD/CURRENT on 12/STABLE/RELEASE that have different ABI thus bad
> > syscall.. and I need CURRENT to build CURRENT, right? :-)
> I believe in order to build the source tree you just need a compatible
> toolchain.  So you can build the source tree for 13.0-CURRENT on
> 12.1-RELEASE system.  But you need CURRENT to **run** userland with ABI
> from the CURRENT.

Long story short I need 13-CURRENT to create a 13-CURRENT release with
release(7) because on 12-STABLE/RELEASE chroot with 13-CURRENT does
not work. I need to see how it works with `make release` :-)


> Once again: for native build `make release` may be quite easy and fast.
> release(7) guarantees "absolutely clean build environment".

Will try that `make release` as well, also for 13-CURRENT on
12-STABLE, thank you! Also will compare the time cost with the one
presented below :-)


Creating a "release" also has this advantage that I have memstick
images that I can boot from directly, test what I need, even no need
to install :-)

Here are my build times, for a release for AMD64/12-STABLE, I did not
select DOC nor PORTS to build, only Kernel and Base :-)

BUILD HOST (~$500): HP PROLIANT DL380G7X (HDD 1TB, 128GB RAM, 24vCPU =
2 x Intel Xeon X5660 @2.8GHz = 2 PACKAGES x 6 CORES x 2 HW THREADS )
INTERNET: 600/60MBit

time make clean buildkernel (16x speedup with SMP):
2472.027u 291.657s 46:34.54 98.8%   38592+3123k
195123+3315182io 80167pf+0w
-j122355.140u 282.807s 3:40.12 1198.4%  38509+3121k
190142+3361605io 71356pf+0w
-j243672.641u 382.254s 2:54.85 2319.0%  39837+3149k
218567+3361605io 64857pf+0w
-j483722.707u 352.940s 3:07.10 2178.3%  40328+3169k
214359+3361607io 66526pf+0w

time make clean buildworld (12.5x speedup with SMP):
32223.598u 1940.942s 9:28:07.59 100.2% 46920+3430k
563493+3074126io 234706pf+0w
-j1233644.438u 1818.147s 54:46.68 1078.9% 47324+3449k
485257+3255853io 236896pf+0w
-j2450728.732u 2556.953s 45:06.66 1968.6% 47556+3455k
560905+3255862io 229433pf+0w
-j4851129.166u 2454.564s 44:38.12 2000.7% 47630+3458k
525602+3255854io 210237pf+0w

release.sh (seems to auto-adjust -j optimization and below 2h looks
really cool):
94556.462u 5583.273s 1:43:14.24 1616.6% 50234+3336k
1457023+16921354io 615421pf+0w
-j12   94477.001u 5577.692s 1:42:59.60 1619.1% 50251+3337k
1463964+16932952io 617689pf+0w
-j24   94480.274u 5574.117s 1:43:38.89 1608.8% 50213+3336k
1468685+16931170io 617425pf+0w
-j48   94588.653u 5569.909s 1:43:10.62 1617.9% 50211+3336k
1460546+16925145io 611229pf+0w

These times may be even smaller when SSD is used instead of HDD. Also
I wonder how to utilize all RAM to speed up the compilation because I
can see 8..34GB utilization while the rest of 128GB remains unused. I
saw some ramdisk tricks I need to try that as well :-)

Best regards :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Query on installing v6eval to FreeBSD 12.1

[radhika somaiya]

Hi team,

I am very new to this FreeBSD world. Currently have set up my system having
dual booting of FreeBSD 12.1 release with preinstalled windows 10.

After booting into FreeBSD, I want to set up the Tahi self test tool where
I am facing the complication error while compiling the v6eval package. I
have downloaded v6eval latest package 3.3.5 version.

Please any one help me to narrow down the issue that I am facing. The error
comes as: error: unknown type name 'des_key_schedule': did you mean
'DES_key_scedule'?

I searched from the net and trying to downgrade the openssl version from
1.1.1d to 1.0. But it is not happening.

Any help would be appreciated highly.

Below is the snap of the error:

Thank you,
Radhika
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

RE: Porting of Smallstep CA

[driesm.michiels]

> -Original Message-
> From: owner-freebsd-po...@freebsd.org 
> On Behalf Of Markus Wipp
> Sent: dinsdag 7 april 2020 22:08
> To: freebsd-ports@freebsd.org
> Subject: Porting of Smallstep CA
> 
> Hi all,
> 
> I would like to create a port of the CA tool (basically two ports: cli and
> certificates) found on https://github.com/smallstep https://smallstep.com/
> 
> What I tried so far was:
> 1) make it on my machine without the ports infrastructure. This basically
> works fine and without any errors and modifications needed ( I just do a
> gmake bootstrap and then a gmake build )
> 2) tried to create a port using the guide at
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-
> handbook/quick-porting.html
> 3) tried Slow porting, but I think I’m not really understanding how and where
> to begin
> 
> The main issue is, that I don’t really know what I have to do here, to achieve
> what’s required to correctly build the port.
> It is the very first time I’m trying to create a port.
> 
> My Makefile looks like this:
> 
> # $FreeBSD $
> 
> PORTNAME= step-cli
> DISTVERSIONPREFIX=v
> DISTVERSION=  0.14.0-rc.4
> CATEGORIES=   security
> MASTER_SITES=
>   https://github.com/smallstep/cli/releases/download/v${DISTVERSION
> }/
> #PKGNAMESUFFIX=   0.14.0-rc.4
> DISTNAME= ${PORTNAME}_${DISTVERSION}
> MAINTAINER=   mw@wipp.bayern
> COMMENT=  Smallstep step-ca command line client
> LICENSE=  APACHE20
> 
> #WRKSRC=  ${WRKDIR}/step-cli
> WRKSRC=   ${WRKDIR}/
> NO_WRKSUBDIR= yes
> 
> BUILD_DEPENDS=go>1:lang/go \
>   bash>5:shells/bash \
>   curl>7:ftp/curl \
>   golint:devel/golint
> 
> USES= gmake
> MAKE_ARGS=build
> 
> 
> .include 
> 
> 
> When I try to run make stage on this I get:
> root@pkgbuild:/usr/ports/security/step-cli # make stage ===>  Building for
> step-cli-0.14.0.r.4
> gmake[1]: Entering directory '/usr/ports/security/step-cli/work'
> /bin/sh: golangci-lint: not found
> gmake[1]: *** [make/common.mk:101: lint] Error 127
> gmake[1]: *** Waiting for unfinished jobs
> go: finding module for package github.com/envoyproxy/protoc-gen-
> validate/tests/harness/cases/go
> go: finding module for package
> github.com/shurcooL/github_flavored_markdown
> go: finding module for package github.com/samuel/go-zookeeper/zk
> go: finding module for package github.com/mozilla/scribe
> go: finding module for package golang.org/x/mobile/event/lifecycle
> go: finding module for package github.com/lyft/protoc-gen-star
> go: finding module for package github.com/ethereum/go-ethereum/ethclient
> go: finding module for package github.com/BurntSushi/xgb
> go: finding module for package github.com/ethereum/go-ethereum/rlp
> go: finding module for package github.com/oklog/oklog/pkg/group
> go: finding module for package github.com/influxdata/influxdb1-client/v2
> go: finding module for package gopkg.in/yaml.v1
> go: finding module for package github.com/hashicorp/consul/api
> go: finding module for package github.com/openzipkin/zipkin-go
> go: finding module for package github.com/iancoleman/strcase
> go: finding module for package github.com/BurntSushi/xgb/shm
> go: finding module for package golang.org/x/mobile/event/key
> go: finding module for package golang.org/x/image/math/fixed
> go: finding module for package github.com/gorilla/mux
> go: finding module for package github.com/ianlancetaylor/demangle
> go: finding module for package github.com/openzipkin-contrib/zipkin-go-
> opentracing
> go: finding module for package go.mozilla.org/mozlog
> go: finding module for package github.com/nats-io/nats.go
> go: finding module for package github.com/envoyproxy/protoc-gen-
> validate/tests/harness/go
> go: finding module for package github.com/Sirupsen/logrus
> go: finding module for package bitbucket.org/creachadair/shell
> go: finding module for package github.com/envoyproxy/protoc-gen-
> validate/tests/harness/gogo
> go: finding module for package
> sourcegraph.com/sourcegraph/appdash/opentracing
> go: finding module for package github.com/remyoudompheng/go-misc/zipfs
> go: finding module for package github.com/benlaurie/gds-registers/register
> go: finding module for package github.com/BurntSushi/xgb/render
> go: finding module for package github.com/shurcooL/gopherjslib
> go: finding module for package github.com/openzipkin/zipkin-
> go/reporter/http
> go: finding module for package golang.org/x/mobile/event/paint
> go: finding module for package sourcegraph.com/sourcegraph/appdash
> go: finding module for package github.com/VividCortex/gohistogram
> go: finding module for package github.com/shurcooL/httpfs/vfsutil
> go: finding module for package