Open Bug 1400505 Opened 7 years ago Updated 7 years ago

mach try fuzzy spews a bunch of hg status noise to the terminal

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

People

(Reporter: bzbarsky, Unassigned)

References

Details

Apparently mach try (at least when I just tried it as "mach try --preset=something") spews the output of "hg status" to the terminal. In my case that's over 100 lines of .rej/.orig files and whatnot, plus various other noise from things that like to dump files in the srcdir. It would be really nice to not have this noise there.
Looks like this only happens for mach try fuzzy, not mach try syntax?
Summary: mach try spews a bunch of hg status noise to the terminal → mach try fuzzy spews a bunch of hg status noise to the terminal
I think we should fix this by converting `mach try` to use the mozversioncontrol Python package for doing VCS interaction. I /think/ there's an open bug on that somewhere...
This comes from the `push-to-try` extension, so this is a bug in version-control-tools. Personally I like this behaviour because once in awhile I notice I forgot to add a file and it saves me a wasted try run. However I didn't realize .orig and .rej files weren't added to topsrcdir/.hgignore. Is there a reason we don't have those added? Looks like I never noticed this because I have them listed in my ~/.hgignore. As a workaround, you can create ~/.hgignore and add: syntax:glob *.rej *.orig
Component: Task Configuration → General
Product: Taskcluster → Developer Services
You need to log in before you can comment on or make changes to this bug.