Local shuttle precheck fails in step 10 after 14 h...
# shuttle-precheck
j
Local shuttle precheck fails in step 10 after 14 hours, with
Copy code
{{XOR CHECK PASSED}} The GDS file has no XOR violations.
{{STEP UPDATE}} Executing Check 8 of 14: Magic DRC
Found 0 violations
0 DRC violations
{{MAGIC DRC CHECK PASSED}} The GDS file, user_project_wrapper.gds, has no DRC violations.
{{STEP UPDATE}} Executing Check 9 of 14: Klayout FEOL
No DRC Violations found
{{Klayout FEOL CHECK PASSED}} The GDS file, user_project_wrapper.gds, has no DRC violations.
{{STEP UPDATE}} Executing Check 10 of 14: Klayout BEOL
Traceback (most recent call last):
  File "mpw_precheck.py", line 132, in <module>
    default_content='_default_content')
  File "mpw_precheck.py", line 99, in main
    run_precheck_sequence(precheck_config=precheck_config, project_config=project_config)
  File "mpw_precheck.py", line 57, in run_precheck_sequence
    results[check.__surname__] = check.run()
  File "/opt/check_manager/__init__.py", line 139, in run
    self.klayout_cmd_extra_args)
  File "/opt/checks/drc_checks/klayout/klayout_gds_drc_check.py", line 20, in klayout_gds_drc_check
    with open(report_file_path) as klayout_xml_report:
FileNotFoundError: [Errno 2] No such file or directory: '/home/jcyr/caravel-sha3-miner-mpw3/precheck_results/30_OCT_2021___01_04_37/outputs/reports/klayout_beol_check.xml'
bash-4.2$
Not sure what to do about it??? @User Is there anything I can provide to help resolve this issue. It has now been reproduced both locally and at efabless.
m
@User There have been reports of out of memory errors at this stage. If you were running on a 16GB machine, try a machine with more memory. efabless uses a 16GB machine by default, I heard. See https://skywater-pdk.slack.com/archives/C017HPHCMEY/p1635219667041800 and https://skywater-pdk.slack.com/archives/C017HPHCMEY/p1635236821046000 and https://skywater-pdk.slack.com/archives/C017HPHCMEY/p1635271301050300
j
I don't it;s lack of memory. I'm running on a 32GB box.
m
@User Well, we probably don't need to worry about the memory then. Can you check to see if the
klayout BEOL
log looks like it finished successfully? I'm thinking that it might not have and may contain a clue as to why it didn't.