xk6 build with influxdb fails after k6 version v0.38.0

[ketan55patil]

OS: Windows

Most likely caused by:
grafana/k6#2433

ERROR:

C:\repo>k6 version
k6 v0.38.0 ((devel), go1.18.1, windows/amd64)

C:\repo>xk6 build --with github.com/grafana/xk6-output-influxdb
2022/05/10 17:10:51 [INFO] Temporary folder: C:\Users\###\AppData\Local\Temp\2\buildenv_2022-05-10-1710.586738848
2022/05/10 17:10:51 [INFO] Writing main module: C:\Users\###\AppData\Local\Temp\2\buildenv_2022-05-10-1710.586738848\main.go
2022/05/10 17:10:51 [INFO] Initializing Go module
2022/05/10 17:10:51 [INFO] exec (timeout=10s): C:\Program Files\Go\bin\go.exe mod init k6
go: creating new go.mod: module k6
go: to add module requirements and sums:
        go mod tidy
2022/05/10 17:10:51 [INFO] Pinning versions
2022/05/10 17:10:51 [INFO] exec (timeout=0s): C:\Program Files\Go\bin\go.exe mod edit -require go.k6.io/k6@latest
2022/05/10 17:10:51 [INFO] exec (timeout=0s): C:\Program Files\Go\bin\go.exe mod tidy -compat=1.17
go: finding module for package github.com/nxadm/tail
go: found github.com/nxadm/tail in github.com/nxadm/tail v1.4.8
2022/05/10 17:10:52 [INFO] exec (timeout=0s): C:\Program Files\Go\bin\go.exe mod edit -require github.com/grafana/xk6-output-influxdb@latest
2022/05/10 17:10:52 [INFO] exec (timeout=0s): C:\Program Files\Go\bin\go.exe mod tidy -compat=1.17
go: finding module for package go.k6.io/k6/stats
k6 imports
        github.com/grafana/xk6-output-influxdb imports
        github.com/grafana/xk6-output-influxdb/pkg/influxdb imports
        go.k6.io/k6/stats: module go.k6.io/k6@latest found (v0.38.1), but does not contain package go.k6.io/k6/stats
2022/05/10 17:10:54 [INFO] Cleaning up temporary folder: C:\Users\###\AppData\Local\Temp\2\buildenv_2022-05-10-1710.586738848
2022/05/10 17:10:54 [FATAL] exit status 1

[jwcastillo]

the tag was missing, but you can use the commit directly as follows:
xk6 build --with github.com/grafana/xk6-output-influxdb@d7ce7024ba43050e73b8e9bcf23553d2ddeb29c0

[mstoykov]

Thanks for reporting and for the fix @jwcastillo 🙇 . I have now released a new version/tagged it, this should fix the problem entirely.

It might take a few minutes to an hour for that tag to propagate through the golang infrastructure so be patient or replace the commit above with @v0.2.0 ;)