-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Some grammars needed formatting fixes #3871
Conversation
The formatter had a few bugs that have been fixed now.
The formatter had a few bugs that have been fixed now. Closes antlr#3863 additional issue with formatting
@kaby76 Looks like the TS tests on macOS hang (since more than an hour). Is that something which happens frequently? |
Hey Mike @mike-lischke Sorry for this mess. This seems to be happening more often nowadays. It was not like this a year or two ago. The latest Action is hung in macos/TypeScript except for one job. The raw log says this:
@teverett or @KvanTTT Please kill this github action https://github.com/antlr/grammars-v4/actions/runs/7101621210 . I think you can also just merge it in. Mike's change looks fine. I've suggested it before, and I think it's time to try some things to avoid the problem. First, I'll remove the Bash testing from the matrix because it's really just duplicate of the Powershell test. If that seems ok, I'll stop there. Otherwise, we might need to drop some of the macos tests. Maybe just do a smaller subset. |
I'm a little suspicious of the raw log detail that Github is giving on this hung job. Let's get this Action canceled, then peek at the full/complete raw log it generated. But, the log so far seems to be saying that Github Actions lost track of the queued job. Some related posts: |
It hung during the testing of the PromQL parser.
That's surprising because I'm pretty sure I had a watchdog on the parser. It looks like I may need to put a watchdog on the test script. Nothing seems reliable on Github Actions. |
@mike-lischke thanks! |
The formatter had a few bugs that have been fixed now.
Closes #3863 additional issue with formatting