Fix grammar verifcation by dns2utf8 · Pull Request #34994 · rust-lang/rust

dns2utf8 · 2016-07-23T13:04:40Z

I wanted to improve the grammar-section but I can not build it.

EDIT: I resolved some of the issues, removed the compiler output from the entry.

dns2utf8 · 2016-07-23T19:12:15Z

I was able to fix the errors, yay 😁 The API of libsyntax was changed (eg 24e7491) but the veryfy.rs is not getting build.

Should we include the antlr4-complete.jar or just build the verify.rs with the compiler? So further changes to the API will triger an error.

dbrgn · 2016-07-23T19:26:36Z

This should probably say "antlr", not "antler".

Ah, yes thank you 👍

dns2utf8 · 2016-07-23T19:35:51Z

I run the check-lexer target and the result was this:

test result: failed. 4764 passed; 125 failed; 2 skipped

I am curious, what are the next steps to fix the failed tests?

steveklabnik · 2016-07-25T18:30:19Z

hm, is this always going to be where this is? Feels system-specific

It is the place in Arch Linux, but not on Mac OS X. I have not tested other distros.

steveklabnik · 2016-07-25T18:30:46Z

@alexcrichton what do you think of this PR?

alexcrichton · 2016-07-25T18:42:18Z

It does seems system specific, perhaps that could be refactored? That being said I know very little about all of this, and we don't run it on the bots, so I don't mind merging basically whatever here.

brson · 2016-07-25T19:56:35Z

I'm cool with pushing these improvements through even with the hardcoded path. It's better than it was, and I'm glad somebody is looking at this stuff. Would be good to get this onto a bot #28592

dns2utf8 · 2016-07-28T07:55:10Z

The system specific path could be obmittet with an environement variable, so the javac can find the antlr4-complete.jar but this would require the user to set it manually or the configure script to search for it.

Another alternative would be to include the jar file and just ship it. Is this a good idea?

cc: @nikomatsakis

dns2utf8 · 2016-07-29T22:19:59Z

I add the target check-build-lexer-verifier to make tidy, so it will build the verifier with every build and catch future changes in the API.
This does not require javac or antlr.

I think this is a good state freeze/merge for now. I planed to add some documumentation about the process in the next weeks, but I am no sure whether it will be in a good shape before the 18. august or not.

steveklabnik · 2016-08-03T20:50:33Z

@bors: r+ rollup

now, we can make it better eventually 😄

bors · 2016-08-03T20:50:35Z

📌 Commit 76026d1 has been approved by steveklabnik

@steveklabnik

Fix grammar verifcation I wanted to improve the [grammar-section](https://doc.rust-lang.org/grammar.html#items-and-attributes) but I can not build it. r? @steveklabnik @brson EDIT: I resolved some of the issues, removed the compiler output from the entry.

@steveklabnik

Fix grammar verifcation I wanted to improve the [grammar-section](https://doc.rust-lang.org/grammar.html#items-and-attributes) but I can not build it. r? @steveklabnik @brson EDIT: I resolved some of the issues, removed the compiler output from the entry.

sophiajt · 2016-08-04T22:13:31Z


+clean-grammar:
+	@$(call E, cleaning grammar verification)
+	$(Q)cd src/grammar && rm -Rf verify *.class *.java *.tokens


This does not handle an out-of-tree build directory, which our bots use.
cleaning grammar verification /bin/sh: 1: cd: can't cd to src/grammar /buildslave/rust-buildbot/slave/auto-linux-64-nopt-t/build/mk/clean.mk:51: recipe for target 'clean-grammar' failed make: *** [clean-grammar] Error 2 program finished with exit code 2 elapsedTime=0.958165

Interesting, looking on it.

sophiajt · 2016-08-04T22:13:41Z

@bors r-

* Use make check-lexer to verify the grammar. * Extend grammar/README * Add make clean-grammar rule * Add target check-build-lexer-verifier to make tidy, so it will build the verifier with every build and catch future errors

dns2utf8 · 2016-08-06T09:30:58Z

I moved the in-tree part to the README of the manual process, since it was just for convenience.

I was looking for the structure of the build bot, can I run one locally?

steveklabnik · 2016-08-15T14:55:12Z

@alexcrichton ping re last comment here, can @dns2utf8 do something to test this out?

alexcrichton · 2016-08-15T18:07:20Z

We've got a number of docker images which our bots are running, so running the tests inside those containers would perhaps be enough to test out?

dns2utf8 · 2016-08-15T20:39:42Z

I was able to start a container and access it with this command:

docker run --rm -it --entrypoint=/bin/bash alexcrichton/rust-slave-linux:2016-08-04

then inside clone my branch like the script:

git clone https://github.com/dns2utf8/rust.git --branch doc_grammar

I can then build my branch:

cd rust
./configure && make -j$(nproc) docs

but I am not sure this is the same as you do.
Am I doing it wrong? @jonathandturner

EDIT: I am doing this, because the setup-slave.sh uses some internal server which I can not reach so I am strongly guessing

alexcrichton · 2016-08-15T22:20:05Z

@dns2utf8 yeah that's basically the same as what we do, this'd just be testing for presence of the relevant tools.

Is this running by default on make check though? I thought you had a run a custom check target?

alexcrichton · 2016-09-09T23:03:07Z

Closing due to inactivity, but feel free to resubmit with a rebase!

dns2utf8 · 2016-09-17T09:36:15Z

Thanks for the reminder, I rebased it.

Can I reopen the issue just with a comment?

@steveklabnik

Fix grammar verification * Use make check-lexer to verify the grammar. * Extend grammar/README * Add make clean-grammar rule * Add target check-build-lexer-verifier to make tidy, so it will build the verifier with every build and catch future errors This is the continuation of #34994 r? @steveklabnik @jonathandturner @alexcrichton

rust-highfive assigned steveklabnik Jul 23, 2016

dns2utf8 changed the title ~~Enhance the spelling of the grammar~~Fix grammar verifcationJul 23, 2016

dbrgn reviewed Jul 23, 2016
View reviewed changes

dns2utf8 mentioned this pull request Jul 23, 2016
A disclaimer about keywords. #34370
Merged

dns2utf8 force-pushed the doc_grammar branch from a1c65dc to a2f27ecCompare July 24, 2016 09:18

steveklabnik reviewed Jul 25, 2016
View reviewed changes

dns2utf8 force-pushed the doc_grammar branch 6 times, most recently from 10f7384 to e8f4f4fCompare July 29, 2016 22:00

dns2utf8 force-pushed the doc_grammar branch from e8f4f4f to 76026d1Compare July 29, 2016 23:03

sophiajt mentioned this pull request Aug 4, 2016
Rollup of 25 pull requests #35320
Closed

steveklabnik mentioned this pull request Aug 4, 2016
Rollup of 25 pull requests #35321
Closed

GuillaumeGomez mentioned this pull request Aug 4, 2016
Rollup of 30 pull requests #35332
Closed

sophiajt reviewed Aug 4, 2016
View reviewed changes

dns2utf8 force-pushed the doc_grammar branch from 76026d1 to 4e9ea80Compare August 6, 2016 09:23

Fix grammar verification
7ce7dd1
* Use make check-lexer to verify the grammar. * Extend grammar/README * Add make clean-grammar rule * Add target check-build-lexer-verifier to make tidy, so it will build the verifier with every build and catch future errors

dns2utf8 force-pushed the doc_grammar branch from 4e9ea80 to 7ce7dd1Compare August 6, 2016 09:28

alexcrichton closed this Sep 9, 2016

dns2utf8 mentioned this pull request Nov 5, 2016
Fix grammar verification #37607
Merged

Uh oh!

Uh oh!

Conversation

dns2utf8 commented Jul 23, 2016• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dns2utf8 commented Jul 23, 2016

Uh oh!

dbrgnJul 23, 2016

Choose a reason for hiding this comment

Uh oh!

dns2utf8Jul 23, 2016

Choose a reason for hiding this comment

Uh oh!

dns2utf8 commented Jul 23, 2016• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

steveklabnikJul 25, 2016

Choose a reason for hiding this comment

Uh oh!

dns2utf8Jul 28, 2016

Choose a reason for hiding this comment

Uh oh!

steveklabnik commented Jul 25, 2016

Uh oh!

alexcrichton commented Jul 25, 2016

Uh oh!

brson commented Jul 25, 2016

Uh oh!

dns2utf8 commented Jul 28, 2016

Uh oh!

dns2utf8 commented Jul 29, 2016

Uh oh!

steveklabnik commented Aug 3, 2016

Uh oh!

bors commented Aug 3, 2016

Uh oh!

sophiajtAug 4, 2016

Choose a reason for hiding this comment

Uh oh!

dns2utf8Aug 6, 2016

Choose a reason for hiding this comment

Uh oh!

sophiajt commented Aug 4, 2016

Uh oh!

dns2utf8 commented Aug 6, 2016

Uh oh!

steveklabnik commented Aug 15, 2016

Uh oh!

alexcrichton commented Aug 15, 2016

Uh oh!

dns2utf8 commented Aug 15, 2016• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

alexcrichton commented Aug 15, 2016

Uh oh!

alexcrichton commented Sep 9, 2016

Uh oh!

dns2utf8 commented Sep 17, 2016• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

dns2utf8 commented Jul 23, 2016•
edited
Loading

dns2utf8 commented Jul 23, 2016•
edited
Loading

dns2utf8 commented Aug 15, 2016•
edited
Loading

dns2utf8 commented Sep 17, 2016•
edited
Loading