Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Script tests in dotnet-helix-machine broken
See original GitHub issueThe helix-client script integration tests in the ScriptTests and ServiceMockTests projects of dotnet-helix-machines have not been running in CI. Running them ScriptTests to be broken (perhaps from simply being out of date as the client has evolved?).
Build 20220714.04 is a typical passing main-branch CI build. Notice that the test report does not include any test from ScriptTests or ServiceMockTests.
Build 20220715.14 is a build with two projects renamed to match Arcade’s .Tests naming convention, causing these tests to get noticed and run. The test fails in Script.Tests are clear, and match what I see locally. The tests in ServiceMock.Tests pass and are listed in the test summary as expected.
These… should be fixed. Or, deleted if they’re actually not providing value.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
These tests do provide value and I’m interested in taking this on, I’ll do at least an initial investigation this week and see if I can unblock them.
I haven’t seen this fail since last week, so closing.