Skip to content

Conversation

ChinYikMing
Copy link
Collaborator

After merging #487, the elf_list.js file is generated dynamically, and the wasm service requires this file to run. However, during CI deployment, the file is not pushed to the rv32emu-demo repo, causing the GitHub Pages to malfunction. To resolve this, pushing the file to the rv32emu-demo repo is the solution.

The 'demo' directory is only created when the WASM service runs locally. To address this, the elf_list.js file should be placed in the 'build' directory instead, as the CI deployment does not invoke the Makefile's start-web target, so the 'demo' directory will not be generated.

After merging sysprog21#487, the elf_list.js file is generated dynamically, and
the wasm service requires this file to run. However, during CI deployment,
the file is not pushed to the rv32emu-demo repo, causing the GitHub Pages
to malfunction. To resolve this, pushing the file to the rv32emu-demo repo
is the solution.

The 'demo' directory is only created when the WASM service runs locally.
To address this, the elf_list.js file should be placed in the 'build'
directory instead, as the CI deployment does not invoke the Makefile's
start-web target, so the 'demo' directory will not be generated.
@jserv jserv added this to the release-2024.1 milestone Sep 2, 2024
@jserv jserv merged commit 10bc401 into sysprog21:master Sep 2, 2024
@ChinYikMing ChinYikMing deleted the fix-wasm-service branch September 2, 2024 06:02
@ChinYikMing
Copy link
Collaborator Author

The WebAssembly CI needs to be triggered on our own.

vestata pushed a commit to vestata/rv32emu that referenced this pull request Jan 24, 2025
CI: Fix missing file in WebAssembly deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants