[CI] Added System Verilog Regression Tests to GitHub Runners #2885

AlexandreSinger · 2025-02-07T16:07:16Z

The system verilog regression tests were put into the currently not-working nightly tests. Since they are so small, putting them in the GitHub runners tests instead so they do not regress.

The strong parmys test also has system verilog tests (I think); however, that test may be too large for the GitHub runners. We may consider moving that test to the SAVI workflows in the future.

AlexandreSinger · 2025-02-07T20:14:00Z

@amirarjmand93 The System Verilog regression tests do not appear to be working. There seems to be a build error with the -DYOSYS_F4PGA_PLUGINS=ON CMAKE option:

Have you seen this error before and know how to fix it?

amirarjmand93 · 2025-02-07T20:55:37Z

#2841 (comment)

I ran this test locally and the result was okay.

have you tried "-DYOSYS_F4PGA_PLUGINS=ON" ? I had changed to "-DSYNLIG_SYSTEMVERILOG=ON" in nightly_testl

AlexandreSinger · 2025-02-07T21:03:44Z

#2841 (comment)

I ran this test locally and the result was okay.

have you tried "-DYOSYS_F4PGA_PLUGINS=ON" ? I had changed to "-DSYNLIG_SYSTEMVERILOG=ON" in nightly_testl

What is the difference between -DYOSYS_F4PGA_PLUGINS=ON and -DSYNLIG_SYSTEMVERILOG=ON? Currently I am matching what is written in the NightlyTests:

But the NightlyTests are never being run; so I am moving it to our GitHub runners. Which of the two arguments should I give to this test? Both?

amirarjmand93 · 2025-02-07T21:10:08Z

Before Synlig , we had used F4PGA pluggin and -DYOSYS_F4PGA_PLUGINS=ON was the command to make vtr with system verilog.
in Synlig, i changed -DYOSYS_F4PGA_PLUGINS=ON to -DSYNLIG_SYSTEMVERILOG=ON. so just this new cmake command should work and make vtr + synlig.

AlexandreSinger · 2025-02-07T21:18:55Z

Before Synlig , we had used F4PGA pluggin and -DYOSYS_F4PGA_PLUGINS=ON was the command to make vtr with system verilog. in Synlig, i changed -DYOSYS_F4PGA_PLUGINS=ON to -DSYNLIG_SYSTEMVERILOG=ON. so just this new cmake command should work and make vtr + synlig.

The test I added is using -DSYNLIG_SYSTEMVERILOG=ON, everything else is using the default libraries and build commands for Ubuntu 24.04. Is it possible that you have something locally that is not in this test?

amirarjmand93 · 2025-02-07T21:30:22Z

git submodule init
git submodule update --recursive

I think adding this to the YML might solve the problem. I usually have tried them before making and testing a VTR with Synlig.

AlexandreSinger · 2025-02-07T21:44:51Z

git submodule init
git submodule update --recursive
I think adding this to the YML might solve the problem. I usually have tried them before making and testing a VTR with Synlig.

The --recursive is interesting. We do not do that by default in the CI, we normally just do a regular submodule update. I have pushed a revision which does the submodule update recursively. Hopefully that fixes it!

amirarjmand93 · 2025-02-07T22:36:32Z

let's add commands under run:

run: |
       git submodule sync --recursive  # Sync submodules
       git submodule update --init --recursive  # Ensure they are initialized & updated'
.
.
.

do you think it might help?

The system verilog regression tests were put into the currently not-working nightly tests. Since they are so small, putting them in the GitHub runners tests instead so they do not regress. The strong parmys test also has system verilog tests (I think); however, that test may be too large for the GitHub runners. We may consider moving that test to the SAVI workflows in the future.

AlexandreSinger · 2025-02-07T22:45:32Z

git submodule update --init --recursive # Ensure they are initialized & updated'

Lets give it a shot, but why is this necessary?

amirarjmand93 · 2025-02-08T16:05:24Z

I think this Building discrepancy might arise from some library dependency, a path conflicting with CI or a race condition between Cloning and Updating modules. but I checked and it seems no new system or Python packages are required for Synlig. (you can also check https://github.com/chipsalliance/synlig)
Also, I rebuilt on local env and no errors appeared.
make CMAKE_PARAMS="-DCMAKE_BUILD_TYPE=Release -G 'Unix Makefiles' -Werror=dev -DSYNLIG_SYSTEMVERILOG=ON" -j16

Can I manipulate this branch and run some tests?

AlexandreSinger · 2025-02-08T16:37:12Z

@amirarjmand93 Feel free to modify the branch anyway you like! I recommend just deleting the other tests so that just the SystemVerilog test is active if you will use the CI to test (just to save yourself time waiting for the other known working tests).

If you think it is a race condition in the build script (which honestly could be the problem!), you can make the build script single threaded by setting the NUM_PROC to 1 here:

amirarjmand93 · 2025-02-08T17:13:40Z

Thank you,
Yes usually I disable nightly tests but in this test, I think working tests should be removed from this list, right?

AlexandreSinger · 2025-02-08T17:24:21Z

Thank you, Yes usually I disable nightly tests but in this test, I think working tests should be removed from this list, right?

No, thats a different list just for the coverity scan test. To turn off the other jobs you should be able to just delete the jobs from the workflow:

vtr-verilog-to-routing/.github/workflows/test.yml

Lines 36 to 581 in f41ea8c

	jobs:
	Build:
	name: 'B: Building VtR'
	runs-on: ubuntu-24.04
	strategy:
	fail-fast: false
	matrix:
	include:
	- { build_type: 'release', verbose: '0' }
	- { build_type: 'debug', verbose: '0' }
	- { build_type: 'debug', verbose: '1' }
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	BUILD_TYPE: ${{ matrix.build_type }}
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh VERBOSE=${{ matrix.verbose }}


	Format:
	runs-on: ubuntu-24.04
	strategy:
	fail-fast: false
	matrix:
	include:
	- { name: 'C/C++', script: 'check-format.sh' }
	- { name: 'Python', script: 'check-format-py.sh' }
	- { name: 'Python Lint', script: 'pylint_check.py' }
	name: 'F: ${{ matrix.name }}'
	steps:

	# TODO: This should be on the same version of Python as would be found on
	# Ubuntu 24.04 (3.12.3); however that version has some linting errors.
	- uses: actions/setup-python@v5
	with:
	python-version: 3.10.10
	- uses: actions/checkout@v4

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- name: Test
	run: ./dev/${{ matrix.script }}


	UnitTests:
	name: 'U: C++ Unit Tests'
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- name: Test
	env:
	CMAKE_PARAMS: "-DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on"
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: ./.github/scripts/unittest.sh


	Warnings:
	name: 'W: Check Compilation Warnings'
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	#In order to get compilation warnings produced per source file, we must do a non-IPO build
	#We also turn warnings into errors for this target by doing a strict compile
	CMAKE_PARAMS: "-DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DVTR_ENABLE_STRICT_COMPILE=on -DVTR_IPO_BUILD=off"
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh


	Regression:
	runs-on: ubuntu-24.04
	strategy:
	fail-fast: false
	matrix:
	include: [
	{
	name: 'Basic',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on',
	suite: 'vtr_reg_basic',
	extra_pkgs: ""
	},
	{
	name: 'Basic with highest assertion level',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=4 -DWITH_BLIFEXPLORER=on',
	suite: 'vtr_reg_basic',
	extra_pkgs: ""
	},
	{
	name: 'Basic_odin',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DWITH_PARMYS=OFF -DWITH_ODIN=on',
	suite: 'vtr_reg_basic_odin',
	extra_pkgs: ""
	},
	{
	name: 'Basic with NO_GRAPHICS',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DVPR_USE_EZGL=off',
	suite: 'vtr_reg_basic',
	extra_pkgs: ""
	},
	{
	name: 'Basic with NO_SERVER',
	params: '-DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DVPR_USE_EZGL=on -DVPR_USE_SERVER=off',
	suite: 'vtr_reg_basic',
	extra_pkgs: ""
	},
	{
	name: 'Basic with CAPNPROTO disabled',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DVTR_ENABLE_CAPNPROTO=off',
	suite: 'vtr_reg_basic',
	extra_pkgs: ""
	},
	{
	name: 'Basic with VTR_ENABLE_DEBUG_LOGGING',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DVTR_ENABLE_DEBUG_LOGGING=on',
	suite: 'vtr_reg_basic',
	extra_pkgs: ""
	},
	{
	name: 'Basic_odin with VTR_ENABLE_DEBUG_LOGGING',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DVTR_ENABLE_DEBUG_LOGGING=on -DWITH_PARMYS=OFF -DWITH_ODIN=on',
	suite: 'vtr_reg_basic_odin',
	extra_pkgs: ""
	},
	{
	name: 'Strong',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on',
	suite: 'vtr_reg_strong',
	extra_pkgs: "libeigen3-dev"
	},
	{
	name: 'Strong_odin',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DWITH_PARMYS=OFF -DWITH_ODIN=on',
	suite: 'vtr_reg_strong_odin',
	extra_pkgs: ""
	},
	{
	name: 'Valgrind Memory',
	params: '-DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off -DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DWITH_ODIN=on',
	suite: 'vtr_reg_valgrind_small',
	extra_pkgs: ""
	}
	]
	name: 'R: ${{ matrix.name }}'
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3

	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- name: Install external libraries
	run: sudo apt install -y ${{ matrix.extra_pkgs }}
	if: ${{ matrix.extra_pkgs }}

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: ${{ matrix.params }}
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh
	./run_reg_test.py ${{ matrix.suite }} -show_failures -j${{ steps.cpu-cores.outputs.count}}

	- name: Upload regression run files
	if: ${{ !cancelled() }}
	uses: actions/upload-artifact@v4
	with:
	name: ${{matrix.name}}_run_files
	path: \|
	vtr_flow/*/.out
	# vtr_flow/*/.blif # Removed since it was taking too much space and was hardly used.
	vtr_flow/*/.p
	vtr_flow/*/.net
	vtr_flow/*/.r

	- name: Upload regression results
	if: ${{ !cancelled() }}
	uses: actions/upload-artifact@v4
	with:
	name: ${{matrix.name}}_results
	path: \|
	vtr_flow/*/.log
	vtr_flow/*/parse_results.txt

	Sanitized:
	runs-on: ubuntu-24.04
	strategy:
	fail-fast: false
	matrix:
	include: [
	{
	name: 'Basic',
	params: '-DVTR_ASSERT_LEVEL=3 -DVTR_ENABLE_SANITIZE=on -DVTR_IPO_BUILD=off -DWITH_BLIFEXPLORER=on -DWITH_PARMYS=OFF -DWITH_ODIN=on',
	suite: 'vtr_reg_basic_odin'
	}
	#- { name: 'Strong', suite: 'vtr_reg_strong' } # SKIP Too long to run on GitHub Actions (max 6h)
	]


	name: 'S: ${{ matrix.name }}'
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: ${{ matrix.params }}
	BUILD_TYPE: debug
	LSAN_OPTIONS: 'exitcode=42' #Use a non-standard exit code to ensure LSAN errors are detected
	# In Ubuntu 20240310.1.0, the entropy of ASLR has increased (28 -> 32). LLVM 14 in this
	# image is not compatible with this increased ASLR entropy. Apparently, memory sanitizer
	# depends on LLVM and all CI tests where VTR_ENABLE_SANITIZE is enabled fail. For a temporary
	# fix, we manually reduce the entropy. This quick fix should be removed in the future
	# when github deploys a more stable Ubuntu image.
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	sudo sysctl -w vm.mmap_rnd_bits=28
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh
	# We skip QoR since we are only checking for errors in sanitizer runs
	./run_reg_test.py ${{ matrix.suite }} -show_failures -j${{ steps.cpu-cores.outputs.count }} -skip_qor


	Parmys:
	name: 'Parmys Basic Test'
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: '-DVTR_IPO_BUILD=off'
	BUILD_TYPE: debug
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh
	./run_reg_test.py parmys_reg_basic -show_failures -j${{ steps.cpu-cores.outputs.count }}

	SystemVerilog:
	name: 'System Verilog Regression'
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3

	# NOTE: This is using recursive on purpose. In order to use the System
	# Verilog feature, need submodules inside of a submodule.
	- uses: actions/checkout@v4
	with:
	submodules: 'recursive'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: '-DSYNLIG_SYSTEMVERILOG=ON'
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	git submodule sync --recursive # Sync submodules
	git submodule update --init --recursive # Ensure they are initialized & updated'
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh
	./run_reg_test.py vtr_reg_system_verilog -show_failures -j${{ steps.cpu-cores.outputs.count}}

	ODINII:
	name: 'ODIN-II Basic Test'
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: '-DVTR_ASSERT_LEVEL=3 -DVTR_ENABLE_SANITIZE=on -DVTR_IPO_BUILD=off -DWITH_BLIFEXPLORER=on -DWITH_PARMYS=OFF -DWITH_ODIN=on'
	BUILD_TYPE: debug
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	sudo sysctl -w vm.mmap_rnd_bits=28
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh
	./run_reg_test.py odin_reg_basic -show_failures -j${{ steps.cpu-cores.outputs.count }}


	VQM2BLIF:
	name: 'VQM2BLIF Basic Tests'
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	BUILD_TYPE: release
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh
	./utils/vqm2blif/test/scripts/test_vqm2blif.sh

	Compatibility:
	runs-on: ubuntu-24.04
	strategy:
	fail-fast: false
	matrix:
	include:
	- { name: 'GCC 11 (Ubuntu Noble - 24.04)', eval: 'CC=gcc-11 && CXX=g++-11', }
	- { name: 'GCC 12 (Ubuntu Noble - 24.04)', eval: 'CC=gcc-12 && CXX=g++-12', }
	- { name: 'GCC 14 (Ubuntu Noble - 24.04)', eval: 'CC=gcc-14 && CXX=g++-14', }
	- { name: 'Clang 16 (Ubuntu Noble - 24.04)', eval: 'CC=clang-16 && CXX=clang++-16', }
	- { name: 'Clang 17 (Ubuntu Noble - 24.04)', eval: 'CC=clang-17 && CXX=clang++-17', }
	- { name: 'Clang 18 (Ubuntu Noble - 24.04)', eval: 'CC=clang-18 && CXX=clang++-18', }
	# Note: We do not include GCC-13 since it is the default and is already tested.
	name: 'B: ${{ matrix.name }}'
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: "-DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on -DWITH_ODIN=on"
	MATRIX_EVAL: ${{ matrix.eval }}
	BUILD_TYPE: release
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh

	JammyCompatibility:
	name: 'Ubuntu Jammy - 22.04 Compatibility Test'
	runs-on: ubuntu-22.04
	steps:
	- uses: actions/setup-python@v5
	with:
	python-version: 3.10.10

	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install Dependencies
	run: ./.github/scripts/install_jammy_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: "-DVTR_ASSERT_LEVEL=3 -DCMAKE_COMPILE_WARNING_AS_ERROR=on -DVTR_IPO_BUILD=off"
	MATRIX_EVAL: 'CC=gcc-11 && CXX=g++-11'
	BUILD_TYPE: release
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh

	Coverity:
	name: 'Coverity Scan'
	needs:
	- Build
	- Format
	- UnitTests
	- Warnings
	- Regression
	- Sanitized
	- Parmys
	- SystemVerilog
	- ODINII
	- VQM2BLIF
	- Compatibility
	runs-on: ubuntu-24.04
	steps:

	- uses: actions/setup-python@v5
	with:
	python-version: 3.12.3
	- uses: actions/checkout@v4
	with:
	submodules: 'true'

	- name: Get number of CPU cores
	uses: SimenB/github-actions-cpu-cores@v2
	id: cpu-cores

	- name: Install dependencies
	run: ./.github/scripts/install_dependencies.sh

	- uses: hendrikmuhs/[email protected]

	- name: Test
	env:
	CMAKE_PARAMS: '-DVTR_ASSERT_LEVEL=3 -DWITH_BLIFEXPLORER=on'
	NUM_PROC: ${{ steps.cpu-cores.outputs.count }}
	_COVERITY_URL: 'https://scan.coverity.com/download/linux64'
	_COVERITY_MD5: 'd0d7d7df9d6609e578f85096a755fb8f'
	run: \|
	export PATH="/usr/lib/ccache:/usr/local/opt/ccache/libexec:$PATH"
	./.github/scripts/build.sh

So basically just delete everything under "Build:", "Format:", "UnitTests:", etc. Leaving behind just the "SystemVerilog:" job.

The regular tests work slightly different from the Nightly Tests.

Change install path

paths corrected

check synlig path

update CPU core

amirarjmand93 · 2025-02-09T15:18:15Z

The previous error during Build time was resolved.
Currently, we have error on the Test. <ERROR: TCL interpreter returned an error: couldn't execute "/home/runner/work/vtr-verilog-to-routing/vtr-verilog-to-routing/build/bin/synlig_install/usr/local/bin/synlig": no such file or directory
probably Synlig has not been installed!
How can I get access to working files for this test(working VTR folder)? I tried Action pathway but I couldn't find it.
Also there is no problem with Building, Test and QOR on the local server for this test(SystemVerilog):

Run the default cmake --build

reduce build proc

github-actions bot added the infra Project Infrastructure label Feb 7, 2025

AlexandreSinger force-pushed the feature-ci-system-verilog branch from d5249ad to 56e0afe Compare February 7, 2025 21:43

AlexandreSinger force-pushed the feature-ci-system-verilog branch from 56e0afe to f41ea8c Compare February 7, 2025 22:44

Update CMakeLists.txt

b2c2052

github-actions bot added lang-make CMake/Make code external_libs labels Feb 8, 2025

Update CMakeLists.txt

5d8eb3a

Change install path

amirarjmand93 force-pushed the feature-ci-system-verilog branch 2 times, most recently from 4cadfba to 5d8eb3a Compare February 8, 2025 22:54

amirarjmand93 and others added 6 commits February 8, 2025 19:12

Update golden results and CMakeLists

4a48f33

Update CMakeLists.txt

00595e2

Update CMakeLists.txt

385b981

Update CMakeLists.txt

dcc3258

paths corrected

Update test.yml

8a9125a

check synlig path

Update CMakeLists.txt

f45e2cd

update CPU core

amirarjmand93 added 2 commits February 9, 2025 19:10

Update CMakeLists.txt

ecd77cd

Run the default cmake --build

Update CMakeLists.txt

2033ae8

reduce build proc

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CI] Added System Verilog Regression Tests to GitHub Runners #2885

[CI] Added System Verilog Regression Tests to GitHub Runners #2885

AlexandreSinger commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025 •

edited

Loading

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 8, 2025 •

edited

Loading

AlexandreSinger commented Feb 8, 2025

amirarjmand93 commented Feb 8, 2025

AlexandreSinger commented Feb 8, 2025

amirarjmand93 commented Feb 9, 2025

[CI] Added System Verilog Regression Tests to GitHub Runners #2885

Are you sure you want to change the base?

[CI] Added System Verilog Regression Tests to GitHub Runners #2885

Conversation

AlexandreSinger commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025 • edited Loading

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 7, 2025

AlexandreSinger commented Feb 7, 2025

amirarjmand93 commented Feb 8, 2025 • edited Loading

AlexandreSinger commented Feb 8, 2025

amirarjmand93 commented Feb 8, 2025

AlexandreSinger commented Feb 8, 2025

amirarjmand93 commented Feb 9, 2025

amirarjmand93 commented Feb 7, 2025 •

edited

Loading

amirarjmand93 commented Feb 8, 2025 •

edited

Loading