First make sure you are familar with the design of fiddle by reading the DESIGN doc.
You may need for force a build on the server, say if you accidentally wiped the mounted drive, or say fiddle is broken and you need to force it to build at HEAD and not wait for that commit to make it into a DEPS rolls.
SSH into skia-fiddle and run:
fiddle_build --force --head --alsologtostderr \ --fiddle_root=/mnt/pd0/fiddle
After that finishes restart fiddle:
sudo systemctl restart fiddle.service
Or restart Fiddle from the push dashboard.
You can add the --preserveTemp flag to fiddle.system and that will cause the temp directories created to store the code and final fiddle executable to be preserved which may make debugging easier.
Highly unlikely to be needed, but if font handling changes, for example, then Skia applications may start trying to read new directories or make exciting new system calls.
If that happens then uncomment the line:
TRACE_ALL,
in fiddle_secwrap.cpp, then compile and run fiddle_secwrap locally and then run it over the offending exe to determine which calls it is making and then add those to the whitelist.
Items below here should include target links from alerts.
Fiddle is failing to build.
This usually isn‘t a critical error since Fiddle will only start using a build of Skia if it was successfully built, but this should be addressed so Fiddle doesn’t get too far removed from Skia HEAD.
Search logs for “Failed to build LKGR:” and “Successfully built:”.
Fiddle is failing to sync.
This sync is for Fiddle updating a local copy of Skia that's used to look up git hashes. The repo is located at /mnt/pd0/fiddle/skia.
Search logs for “Failed to update skia repo”.
One easy fix is to SSH into the machine and delete the directory and then restart Fiddle, which will rebuild the checkout.
There are named fiddles that fail to build.
This isn‘t a critical error since the images for named fiddles will still be served from previous successful builds, but if the fiddle is named it means it’s probably used in documentation and won't compile and run unless changed.
See https://fiddle.skia.org/f/ for the list of failing named fiddles.
Depending on the failure mode either fix the code, fix fiddle_secwrap.cpp if it is a sandbox issue, or contact the person that created the fiddle.
To delete a named fiddle remove the associated file from gs://skia-fiddle/named. I.e. visit:
Each named fiddle is represented by a single file. To delete the named fiddle just delete the associated file in that directory. The alert will eventually go away when fiddle does a new build, which will happen about an hour after the next DEPS roll into Chrome.