Skip to content

test:regress bogged down by regress-gen-instruction-appendix #707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
james-ball-qualcomm opened this issue Apr 30, 2025 · 5 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@james-ball-qualcomm
Copy link
Collaborator

The 2nd longest running regression test task is 7 minutes. Can we see about speeding up this one:

  • regress-gen-instruction-appendix

Does it need to be in the regression tests?

Image

@dhower-qc
Copy link
Collaborator

It spends the majority of its time running asciidoctor-pdf. I don't think we are going to get that sped up.

And, yes, it's important that this regression stays.

@dhower-qc
Copy link
Collaborator

Digging a bit deeper, asciidoctor-pdf spends a lot of its time waiting for wavedrom-cli to generate all the register diagrams.

@AFOliveira
Copy link
Collaborator

Maybe we could generate only a subset of this? The thing is that was not possible as it was before, but maybe the new method in #708 allows for us to config a smaller sub-set? This likely needs a feature addition to instruction appendix generationand I may have to dig the new method to make it work

@dhower-qc
Copy link
Collaborator

We could also just stop at adoc generation for the regression test.

@AFOliveira
Copy link
Collaborator

We could also just stop at adoc generation for the regression test.

Maybe we could stop at adoc just for this one. This way, the adoc build gets tested for all the other outputs, which should mean that nothing is broken either way, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants