Closed Bug 557382 Opened 14 years ago Closed 9 days ago

ensure that 32/64 bit results end up in different buckets in the graph server db

Categories

(Webtools Graveyard :: Graph Server, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: anodelman, Unassigned)

References

Details

I'm worried that testing both 32bit and 64bit browsers for the same branch on the same machines will result in all the data getting smushed together on the graph server.

32bit and 64bit results should be separate.
Blocks: 556125
Blocks: 556118
No longer blocks: 556125
Assignee: nobody → bear
Blocks: 557569
We're still going to need support having a particular os_id associated with a given build - instead of just tracking the os_id of the tester.
anode: is this still a concern on the graph db side of things?
Yes, this is still an issue as we never implemented the necessary schema changes to make this work.

At this point there is only one bucket and everything goes into it - we get around it by sending only 32on32 and only 64on64 tests.  We can't support testing 32on64 till this is fixed.
Assignee: bear → catlee
Priority: -- → P4
Rob, is this something you can take on?

The problem is that the current db schema enforces a 1:1 association between build architecture and test platform architecture. We'd like to be able to test both 32-bit and 64-bit builds on a 64-bit machine.
Assignee: catlee → rhelmer
(In reply to comment #4)
> Rob, is this something you can take on?
> 
> The problem is that the current db schema enforces a 1:1 association between
> build architecture and test platform architecture. We'd like to be able to test
> both 32-bit and 64-bit builds on a 64-bit machine.

Sure, sounds like the right thing to do.
Status: NEW → ASSIGNED
I don't see ourselves doing this for a little while (Test 32-bit/64-bit Windows builds on Windows 7 64-bit).

Should we close and reopen if the plan changes?
I think it's still a good thing to do...we've had to work around this limitation on many occasions in the past, and imagine will have to do so in the future.

that said, this doesn't belong in releng!
Component: Release Engineering → Graph Server
Product: mozilla.org → Webtools
QA Contact: release → graph.server
Assignee: rhelmer → nobody
Product: Webtools → Webtools Graveyard
No assignee, updating the status.
Status: ASSIGNED → NEW
No assignee, updating the status.
No assignee, updating the status.
Status: NEW → RESOLVED
Closed: 9 days ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.