forked from nim-lang/Nim
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
187: debug: clean up formatting for the vmgen debugging r=saem a=haxscramper - Improve formatting for the vmgen code listing reports - Split VM debuggint defines in two - `nimVMDebugExecute` to trace actually executed vm opcodes, and `nimVMDebugGenerate` to see generated code. - Allow filtering out generated code by proc name, using `--define:expandVmListing=vmTarget` ```nim type Obj = object charField: char intField: int proc vmTarget(arg: Obj) = echo arg.charField.int + arg.intField static: vmTarget(Obj()) ``` ``` nim c --filenames:canonical --define:expandVmListing=vmTarget file.nim ``` ``` Code listing for vmTarget LdConst r3 $ 1279 system.nim(2005, 30) LdObj r6 r1 r0 file.nim(7, 11) NodeToReg r5 r6 r0 file.nim(7, 11) Conv r6 r5 int char file.nim(7, 21) LdObj r7 r1 r1 file.nim(7, 31) NodeToReg r5 r7 r0 file.nim(7, 31) AddInt r4 r6 r5 file.nim(7, 26) IndCallAsgn r2 r3 nim-lang#2 file.nim(7, 26) Echo r2 r1 r0 file.nim(7, 26) Ret r0 r0 r0 file.nim(7, 8) Eof r0 r0 r0 file.nim(7, 8) ``` 188: separate documentation publishing from building r=saem a=alaviss Since docs were published as a part of the main CI run, we were forced to re-run CI on devel even though bors has performed the check and built the documentation. This wastes resources especially since our test matrix is expanding. This commit implemented a separate publisher that publishes artifacts built during staging (currently docs). The publisher uses a pull architecture, that is, to query producers and obtain necessary artifacts from them. Main CI will now always build and upload generated documentation, which has a nice bonus of allowing us to review docgen changes more throughly in PRs. An another adjustment made is that the "Edit" link will now be hard-coded to the `devel` branch instead of being inferred from the branch being built on. This lets us reuse docs built during the time spent in staging branch. Closes nim-lang#182 Co-authored-by: haxscramper <haxscramper@gmail.com> Co-authored-by: Leorize <leorize+oss@disroot.org>
- Loading branch information
Showing
7 changed files
with
245 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
name: Publish built artifacts | ||
on: | ||
push: | ||
branches: | ||
- devel | ||
|
||
# Run every script actions in bash | ||
defaults: | ||
run: | ||
shell: bash | ||
|
||
# Since we will be pushing, make sure that only one instance can run at a time. | ||
concurrency: publisher | ||
|
||
jobs: | ||
publisher: | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
# Publish action needs a checkout | ||
- uses: actions/checkout@v2.4.0 | ||
|
||
# Download the latest instance of generated documentation from the build | ||
# during bors staging. | ||
- name: Download generated docs | ||
uses: dawidd6/action-download-artifact@v2.16.0 | ||
with: | ||
workflow: ci.yml | ||
workflow_conclusion: completed | ||
commit: ${{ github.event.after }} | ||
# Keep up-to-date with ci.yml | ||
name: Generated docs | ||
path: doc/html | ||
|
||
- name: Publish docs | ||
uses: JamesIves/github-pages-deploy-action@v4.2.2 | ||
with: | ||
branch: gh-pages | ||
folder: doc/html |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters