Make ./x.py errors more machine-grep-able #51385

Activity

1. Mark-Simulacrum commented on Jun 6, 2018

   

   Mark-Simulacrum

   on Jun 6, 2018

   Member

   More actions

   Could you be more specific? What do you mean by "errors emitted by x.py"? Most of these are test failures and compiler failures... which are already quite good, generally speaking, I'd imagine.
2. mark-i-m commented on Jun 6, 2018

   

   mark-i-m

   on Jun 6, 2018

   ContributorAuthor

   More actions

   Yes, I mostly mean compile and test failures -- anything that would fail a Travis build. Surprisingly, these are not as easy to find as one might expect, since TimNNBot often gives not-very-helpful snippets (e.g. too much or too little, such as #51335 (comment)).

   Instead we should print something like "[ERROR START]" and "[ERROR END]" around the portions we want bots to pick up.
3. Mark-Simulacrum commented on Jun 6, 2018

   

   Mark-Simulacrum

   on Jun 6, 2018

   Member

   More actions

   The bot isn't based on start/stop lines iirc, so I'm not sure that's the right approach. @TimNN probably knows better than me, though.
4. hellow554 commented on Jun 6, 2018

   

   hellow554

   on Jun 6, 2018

   Contributor

   More actions

   One way could be --output-format=json|xml|....
   I mean, the effort to do this is quite high, but you have to decide if it's worth it.
5. memoryruins

   added

   T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

   C-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.

   on Sep 15, 2018
6. mark-i-m commented on Apr 3, 2019

   

   mark-i-m

   on Apr 3, 2019

   ContributorAuthor

   More actions

   There doesn't seem to be high demand for this. Shall I close the issue?
7. mark-i-m

   closed this as completedon May 24, 2019