Closed
Bug 1628796
Opened 5 years ago
Closed 5 years ago
t-mojave-r7-060 g-w json parse failure
Categories
(Infrastructure & Operations :: RelOps: Posix OS, task)
Infrastructure & Operations
RelOps: Posix OS
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dhouse, Assigned: dhouse)
Details
The macos1014 worker 060 self-quarantined after:
2020/04/08 22:51:11 Initialising task feature Mounts/Caches...
2020/04/08 22:51:11 Could not load file file-caches.json into object *main.CacheMap - is it json?
2020/04/08 22:51:11 goroutine 1 [running]:
runtime/debug.Stack(0xc4202ab700, 0x144bebc, 0x1593489)
/home/travis/.gimme/versions/go1.10.3.src/src/runtime/debug/stack.go:24 +0xa7
main.HandleCrash(0x14e0d40, 0xc42000a040)
/home/travis/gopath/src/github.com/taskcluster/generic-worker/main.go:673 +0x26
main.RunWorker.func1(0xc4202abda0)
/home/travis/gopath/src/github.com/taskcluster/generic-worker/main.go:692 +0x52
panic(0x14e0d40, 0xc42000a040)
/home/travis/.gimme/versions/go1.10.3.src/src/runtime/panic.go:502 +0x229
main.(*CacheMap).LoadFromFile(0x18dae38, 0x158e826, 0x10, 0xc42046a4a0, 0x14)
/home/travis/gopath/src/github.com/taskcluster/generic-worker/mounts.go:144 +0x49e
main.(*MountsFeature).Initialise(0x18fae18, 0x1f, 0xc420497a80)
/home/travis/gopath/src/github.com/taskcluster/generic-worker/mounts.go:152 +0x5f
main.initialiseFeatures(0xc42040d900, 0xc4203792c0)
/home/travis/gopath/src/github.com/taskcluster/generic-worker/main.go:422 +0x409
main.RunWorker(0x0)
/home/travis/gopath/src/github.com/taskcluster/generic-worker/main.go:727 +0x315
main.main()
/home/travis/gopath/src/github.com/taskcluster/generic-worker/main.go:498 +0xb06
2020/04/08 22:51:11 *********** PANIC occurred! ***********
2020/04/08 22:51:11 invalid character 'a' looking for beginning of value
2020/04/08 22:51:12 Exiting worker with exit code 69
I removed the quarantined file and rebooted the machine and it failed parsing the json again.
This is an older version of g-w. So I won't open a bug for g-w for this.
I removed the file-caches.json and deleted the files and restarted and it is working fine again.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•