search

Quuxplusone / LLVMBugzillaTest

0 stars 0 forks source link

Chris Is Buggy #1000

Closed Quuxplusone closed 13 years ago

Quuxplusone commented 17 years ago
Bugzilla Link PR1000
Status RESOLVED WONTFIX
Importance P normal
Reported by Reid Spencer (rspencer@reidspencer.com)
Reported on 2006-11-10 18:40:08 -0800
Last modified on 2011-05-24 11:55:13 -0700
Version trunk
Hardware All All
CC brukman+bugs@uiuc.edu, clattner@nondot.org, isanbard@gmail.com, llvm-bugs@lists.llvm.org, stuart@apple.com
Fixed by commit(s)
Attachments
Blocks
Blocked by PR10000
See also

There's no known fix for this bug.

Quuxplusone commented 17 years ago

I could have sworn he worked at one point.

Quuxplusone commented 17 years ago 
Our internal bug tracking software requires submitter to classify bug.
Available options are : Security,
Performance, Serious Bug, Data loss, new feature.

Pick one!
Quuxplusone commented 17 years ago

Is there an option for "All of the above" ?

Quuxplusone commented 17 years ago 
If there's no such option, Serious Bug seems to be the most fitting for the
levity of this PR.
Quuxplusone commented 17 years ago

If bug 100 couldn't be fixed, what do you think the chances of fixing this one are?

-Chris

Quuxplusone commented 17 years ago

I don't know, but not fixing it is not an option!

Quuxplusone commented 17 years ago 
We really should categorize these correctly. Marking this as a tool. Also,
because Chris is a Common Code
Generator, it's believed that the problem's in his internal code.
Quuxplusone commented 17 years ago

This definitely happens on ALL Platforms and All Operating Systems.

Quuxplusone commented 17 years ago 
I know some people (actually 3) who might be able to fix him. He can be turned
into the proper open source compiler guru:
http://www.webweavertech.com/ovidiu/weblog/gallery/richard-stallman/richard-stallman-Images/1.jpg

But this is Tonya's call since she has to live with him. I suspect this will be
a p4later, err, I mean WONTFIX.
Quuxplusone commented 17 years ago 
Based on the foregoing, fixing this is looking to be hard. I suggest we start
with containment. While we may not be able to get to the root cause of the
problem quickly, perhaps we can diminish or eliminate the viral effects it has
on the project. So, here's some suggestions to get started:

1. Everyone stop talking to Chris immediately.
2. With Tanya's help, perhaps we can unplug Chris during off hours.
3. Everything Chris does needs to be code reviewed by everybody (except Chris).
4. Definitely no more Lattners on the project.

Any other impact reducing ideas?

:)
Quuxplusone commented 17 years ago

Ah, there's nothing buggy with Chris that a couple of beers couldn't fix!

Quuxplusone commented 17 years ago

So, you think the fix to this is free? As in free beer?

Quuxplusone commented 17 years ago
  1. We could revert all of Chris' code?
Quuxplusone commented 17 years ago

I don't think this is fixable.

Quuxplusone commented 17 years ago

It may not be fixable, but WORKSFORME? I don't think so, mister.

Quuxplusone commented 17 years ago

This is much more appropriate.

Quuxplusone commented 14 years ago

Dale asked me to test Bugzilla, and picked this one (?). Ergo, this is a test comment.

Quuxplusone commented 14 years ago

Why are you testing bugzilla?

Quuxplusone commented 14 years ago

Dale said that Bugzilla wasn't working for him, and he asked me to add a comment to some bug, and when I insisted on a number, he chose this one.

Quuxplusone commented 14 years ago

Ok, well, let me know if its still a problem. I've had one other person say they couldnt respond to certain bugs, so just wanted to know if it was a trend or not.