Bug 18440 – bugzilla should show an issue template saying: paste output of `dmd -main -Xf=- -Xi=buildInfo -Xi=compilerInfo`

Status
NEW
Severity
enhancement
Priority
P4
Component
dlang.org
Product
D
Version
D2
Platform
x86
OS
Mac OS X
Creation time
2018-02-15T06:43:41Z
Last change time
2024-12-15T15:24:46Z
Assigned to
No Owner
Creator
Timothee Cour
Moved to GitHub: dlang.org#3972 →

Comments

Comment #0 by timothee.cour2 — 2018-02-15T06:43:41Z
bugzilla should show an issue template saying: ``` paste output of `dmd -main -Xf=- -Xi=buildInfo -Xi=compilerInfo` ``` so we have all the context needed (cf https://github.com/Homebrew/brew/issues/new but simpler for user and better) maybe we could simply add `-Xi=bugreport` which shows all info potentially useful for getting context for a bug report (git hashes of dmd/druntime/phobos, more detailed environment etc)
Comment #1 by timothee.cour2 — 2018-02-15T06:47:49Z
Comment #2 by greensunny12 — 2018-02-15T06:55:34Z
Brad [1] (the maintainer of Bugzilla) doesn't monitor the issue tracker. You need to contact him directly for any changes though we are currently evaluating other options (GH issues or upgrading to a newer Bugzilla version like [2]). [1] https://github.com/braddr [2] https://bugzilla.mozilla.org/
Comment #3 by dlang-bugzilla — 2018-03-27T00:33:52Z
(In reply to Timothee Cour from comment #0) > bugzilla should show an issue template saying: > > ``` > paste output of `dmd -main -Xf=- -Xi=buildInfo -Xi=compilerInfo` > ``` > > so we have all the context needed (cf > https://github.com/Homebrew/brew/issues/new but simpler for user and better) There's really nothing there that's interesting other than the version number. Except for very specific circumstances, everything else is just noise.
Comment #4 by timothee.cour2 — 2018-03-27T00:56:04Z
(In reply to Vladimir Panteleev from comment #3) > (In reply to Timothee Cour from comment #0) > > bugzilla should show an issue template saying: > > > > ``` > > paste output of `dmd -main -Xf=- -Xi=buildInfo -Xi=compilerInfo` > > ``` > > > > so we have all the context needed (cf > > https://github.com/Homebrew/brew/issues/new but simpler for user and better) > > There's really nothing there that's interesting other than the version > number. Except for very specific circumstances, everything else is just > noise. environment is also useful (eg freebsd etc); i know there's a hardware tag in bugzilla but having it generated by the command has its use too. FWIW lots of issue trackers require users to post an analog command (eg: brew, tmux)
Comment #5 by dlang-bugzilla — 2018-03-27T01:18:31Z
(In reply to Timothee Cour from comment #4) > environment is also useful (eg freebsd etc); i know there's a hardware tag > in bugzilla but having it generated by the command has its use too. FreeBSD is an OS, not hardware, and we have an OS field. Most bugs we have are not specific to the OS, and when they are, the OS is pretty obvious when it's not mentioned (e.g. OPTLINK's errors are pretty recognizable). I can't remember there ever being a situation like "wait a second, I wish I knew this bug was on <insert-OS-here> N comments ago". > FWIW lots of issue trackers require users to post an analog command (eg: > brew, tmux) This is of no significance to this discussion.
Comment #6 by robert.schadek — 2024-12-15T15:24:46Z
THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dlang.org/issues/3972 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB