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.
Prevent or notify broken master tests
See original GitHub issueWhat is the Problem Being Solved?
We recently had some build check failures for master:
https://github.com/Agoric/agoric-sdk/runs/5069159963?check_suite_focus=true
lerna ERR! EPUBLISHCONFLICT Cannot publish @agoric/cosmos@undefined over existing version.https://github.com/Agoric/agoric-sdk/runs/5069182650?check_suite_focus=true
error @typescript-eslint/parser@5.10.2: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "14.15.5" error Found incompatible module.
They persisted for some days because there was no notification. The checks that were failing were defined for some purpose, so we should know when they fail (or if it doesn’t matter then remove them).
Description of the Design
TBD, some way to prevent persistent failures of master checks.
Security Considerations
–
Test Plan
TBD
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (18 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
Gotcha. An alternative is to modify workflows that trigger on master to send a notification (email, keybase, etc) on failure.
@michaelfig might be able to take the first one.
I probably broke the second one.