HI everyone, my tapeout jobs are failing with FOM density errors. Unlike some prior threads here, the issue in my case seems to be fatal because I do not see any density figures in the log file--that I can fix by adjusting the filler/decap cells as some people have tried. On the portal, I see the following message:

[06/06/22 10:33:06 PDT] FAILED
STDOUT: {{Project Local Info}} caravel_user_project
STDOUT: {{Extracting Files}} Extracting compressed files
STDOUT: {{Step Update}} Generating Final Layout: Step 1 of 7
STDOUT: {{Step Update}} Generating Final Layout: Step 2 of 7
STDOUT: {{Step Update}} Generating Final Layout: Step 3 of 7
STDOUT: {{Step Update}} Generating Final Layout: Step 4 of 7
STDOUT: {{Step Update}} Generating Final Layout: Step 5 of 7
STDOUT: {{Step Update}} Generating Final Layout: Step 6 of 7
STDOUT: {{Step Update}} Generating Final Layout: Step 7 of 7
STDOUT: GDSII File [caravel_2204c3e6.gds] sha1sum: 5553d31beedd026215f2f2a279ca63d62028dc11
STDOUT: {{Step Update}} Converting Final Layout: GDSII -> OASIS
STDOUT: OASIS File [caravel_2204c3e6.oas] sha1sum: a5a735313d2c34627b4dfa7c70c00f31bd519032
STDOUT: {{Step Update}} Executing Check 1 of 5: Klayout Missing Cells on [caravel_2204c3e6.oas]
STDOUT: {{Step Update}} Executing Check 2 of 5: Klayout Front End Of Line on [caravel_2204c3e6.oas]
STDERR: [ WARN ] FEOL Check Result: 'caravel_2204c3e6.oas' has 0 DRC violations.
STDOUT: {{Step Update}} Executing Check 3 of 5: Klayout Back End Of Line on [caravel_2204c3e6.oas]
STDERR: [ WARN ] BEOL Check Result: 'caravel_2204c3e6.oas' has 0 DRC violations.
STDOUT: {{Step Update}} Executing Check 4 of 5: Klayout Metal Minimum Clear Area Density on [caravel_2204c3e6.oas]
STDERR: [ WARN ] MET Density Check Result: 'caravel_2204c3e6.oas' has 0 DRC violations.
STDOUT: {{Step Update}} Executing Check 5 of 5: Klayout Field Oxide Mask Density on [caravel_2204c3e6.oas]
STDOUT: {{FINISH}} Executing Finished, the full logs can be found in u7053_aanujdu/design/modulonet/jobs/tapeout/fbfd3aeb-18ed-41d3-9db5-4ba40ad7e3ec/logs

I also see a very weird gds when I open it in the opengalaxy portal (image attached).

Hello @Anuj Dubey , we're looking into it, hopefully we'll have an answer for you soon

Thank you for the update @omla. I've resubmitted the job and will let you know if I hit another issue. On a related note, I got to know from Greg on the help ticket that it was an issue with the tarball processing. Thus, I wanted to know if there's a way to somehow git pull from a private repo on the portal? If you pull at a specific repo, maybe I can add that repo in the collaborators? If not, what exactly do I need to include in the tarball; unfortunately I couldn't find any guidelines on the tarball based submissions? Currently I am using the following exclusions

tar -c --exclude=final --exclude=.git --exclude=runs --exclude=*.vcd --exclude=*.mag --exclude=*.spice --exclude=*.def --exclude=*.vvp caravel_user_project/

, which got me past the initial exceptions I saw when I submitted a ~1GB tarball; these exclusions bring down the size to ~300MB.

@Anuj Dubey that's great, I am glad you got through and apologize for the inconvenience. Regarding private repo pulling, we definitely are aware of it and understand the need for it but as of now we have no way of doing that. We are not the biggest fans of the

tarball

process ourselves and we are hoping to replace it eventually. We don't have any guidelines on compression but I will bring it up with the appropriate people to maybe publish something, what you did is completely fine and should not cause problems in the future. Congrats on your tapeout and thanks for reaching out 🙏