-
Notifications
You must be signed in to change notification settings - Fork 68
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
Issue #3870, #3873: Fix windows CI target and swap out uhdm-dump #3874
Conversation
uhdm-dump run during regression aren't of much help - for small tests, the dump results are in the log itself. For large tests, generated files are too big to be useful. Replace udhm-dump with uhdm-lint to report any linting issues. The linting output is merged with the test log.
I have massive failures after this PR in my local run. python3 scripts/regression.py run | YosysSmall | FAIL | 0 | 0 | 0 (-1) | 0 (-6) | 0 (-9) | 0 (-4) | 0.00 | 0 | 0 | 0/0 | Summary: |
PR Build here reported a few failures that were to do with need with log update. Surelog code wasn't even changed in this PR so no reason for Surelog to report any failures. CI is not reporting any failure (except for some logs needing update after the last commit to fix the null reference in uhdm-lint binary) it's something local to your machine. To be CI build which reported only a handful of test log comparison failures (because of the new uhdm-lint output in the log which wasn't there before because of the uhdm-lint crashing on null reference). |
That's what I wanted to do, update the logs.I can't run any test. I reverted the PR and everything worked again.There is a change in the python script that does not work on my machine (first time ever)
Sent from Yahoo Mail on Android
On Sat, Sep 23, 2023 at 11:14, ***@***.***> wrote:
PR Build here reported a few failures that were to do with need with log update. Surelog code wasn't even changed in this PR so no reason for Surelog to report any failures. CI is not reporting any failure (except for some logs needing update after the last commit to fix the null reference in uhdm-lint binary) it's something local to your machine.
To be CI build which reported only a handful of test log comparison failures (because of the new uhdm-lint output in the log which wasn't there before because of the uhdm-lint crashing on null reference).
https://github.com/chipsalliance/Surelog/actions/runs/6282989999
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Please add some debugging mechanism to your python script, like showing the output of surelog invokation
Sent from Yahoo Mail on Android
On Sat, Sep 23, 2023 at 12:33, ***@***.******@***.***> wrote: That's what I wanted to do, update the logs.I can't run any test. I reverted the PR and everything worked again.There is a change in the python script that does not work on my machine (first time ever)
Sent from Yahoo Mail on Android
On Sat, Sep 23, 2023 at 11:14, ***@***.***> wrote:
PR Build here reported a few failures that were to do with need with log update. Surelog code wasn't even changed in this PR so no reason for Surelog to report any failures. CI is not reporting any failure (except for some logs needing update after the last commit to fix the null reference in uhdm-lint binary) it's something local to your machine.
To be CI build which reported only a handful of test log comparison failures (because of the new uhdm-lint output in the log which wasn't there before because of the uhdm-lint crashing on null reference).
https://github.com/chipsalliance/Surelog/actions/runs/6282989999
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Regression script edits do not include any new dependency. The changes in there are minimal because uhdm-dump and uhdm-lint take the same arguments. The big change was to add another column to the output and merge the logs. Can you provide me with a regression.log file from one of the failed runs. It should have enough output to provide some hint as to what went wrong. |
FileNotFoundError: [Errno 2] No such file or directory: '/home/alain/Surelog/out/build/x64-Debug/bin/surelog' cat ./out/build/x64-Debug/regression/WireUnpacked/regression.log Environment: Snapshot ... Running Surelog ... Surelog threw an exception Normalizing surelog log file /home/alain/Surelog/out/build/x64-Debug/regression/WireUnpacked/WireUnpacked.log Restoring pristine state ... {'result': {'CPU-TIME': 0, end-time: 2023-09-23 16:52:48.003839 0:00:00.006949 |
PR #3876 should be good. I accidentally left local debugging toggle turned ON in scripts/regression.py:40 |
Issue #3873: Fix windows clang target
Issue #3870: Swap out uhdm-dump in favor of uhdm-lint
uhdm-dump run during regression aren't of much help - for small tests,
the dump results are in the log itself. For large tests, generated
files are too big to be useful.
Replace udhm-dump with uhdm-lint to report any linting issues.
The linting output is merged with the test log.
Also, add a test for struct_net with union_typespec