syzkaller: make target failed: failed to run ["gmake" "target"]: exit status 2

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:
git tree: https://github.com/google/syzkaller.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14656ccc900000
dashboard link: https://syzkaller.appspot.com/bug?extid=64a741404918bdaa34d0
compiler: go version go1.15beta1 openbsd/amd64

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+64a741...@syzkaller.appspotmail.com



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[Anton Lindqvist]

Fixed by reverting the kcov remote changes.

#syz invalid

[Greg Steuck]

I'll get a fresh snapshot installed tomorrow.

On Sun, Aug 2, 2020, 04:04 Anton Lindqvist <an...@basename.se> wrote:

Fixed by reverting the kcov remote changes.

#syz invalid

--
You received this message because you are subscribed to the Google Groups "syzkaller-openbsd-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-openbsd...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-openbsd-bugs/20200802110447.GA80176%40lol.basename.se.

[Greg Steuck]

Come to think of it, given that clang10 just got committed and the
ports snapshots probably have not caught up, shall we wait a week?

--
nest.cx is Gmail hosted, use PGP: https://pgp.key-server.io/0x0B1542BD8DF5A1B0
Fingerprint: 5E2B 2D0E 1E03 2046 BEC3 4D50 0B15 42BD 8DF5 A1B0

[Anton Lindqvist]

On Tue, Aug 04, 2020 at 08:49:51AM -0700, Greg Steuck wrote:
> Come to think of it, given that clang10 just got committed and the
> ports snapshots probably have not caught up, shall we wait a week?

While upgrading you're doing a fresh install? If that's true, any
outdated port will have unsatisfiable library requirements as libc++ and
libc++abi got bumped. If you're doing a pure upgrade, it should be fine
as old libraries are kept around.

[Anton Lindqvist]

On Tue, Aug 04, 2020 at 08:49:51AM -0700, Greg Steuck wrote:

> Come to think of it, given that clang10 just got committed and the
> ports snapshots probably have not caught up, shall we wait a week?

BTW: execs says broken again, looks like syzkaller is failing to build
according to the dashboard. Any insights?

[Greg Steuck]

I rebooted the syzbot machine as it became unresponsive with nothing
on the console. Any suggestions about a monitoring setup I should
consider so we may catch any leading indicators? Maybe I should start
by trying to get ddb.console working?
https://github.com/google/syzkaller/blob/18397578713eeefc1cf3a687cca53594c1cfd49f/tools/create-openbsd-gce-ci.sh#L84

[Greg Steuck]

On Tue, Aug 4, 2020 at 9:47 AM Anton Lindqvist <an...@basename.se> wrote:
> While upgrading you're doing a fresh install? If that's true, any
> outdated port will have unsatisfiable library requirements as libc++ and
> libc++abi got bumped. If you're doing a pure upgrade, it should be fine
> as old libraries are kept around.

It's always a clean install with
https://github.com/google/syzkaller/blob/18397578713eeefc1cf3a687cca53594c1cfd49f/tools/create-openbsd-gce-ci.sh

I'll wait a bit for things to settle.

[Anton Lindqvist]

On Tue, Aug 04, 2020 at 11:26:57AM -0700, Greg Steuck wrote:
> I rebooted the syzbot machine as it became unresponsive with nothing
> on the console. Any suggestions about a monitoring setup I should
> consider so we may catch any leading indicators? Maybe I should start
> by trying to get ddb.console working?
> https://github.com/google/syzkaller/blob/18397578713eeefc1cf3a687cca53594c1cfd49f/tools/create-openbsd-gce-ci.sh#L84

Do you have serial console access? If you do, setting ddb.console like
you suggested and then sending a BREAK might get you in to ddb.