Closed
Bug 566870
Opened 16 years ago
Closed 15 years ago
Make green arrows add more data to the page instead of replacing it
Categories
(Tree Management Graveyard :: TBPL, enhancement)
Tree Management Graveyard
TBPL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jorendorff, Assigned: Swatinem)
References
Details
Attachments
(8 files, 4 obsolete files)
|
8.44 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
4.17 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
9.14 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
9.97 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
7.53 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
8.10 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
17.01 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
|
6.66 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
I love TBPL, *looove* it, but I think the "pagination" is unhelpful.
Loading is slow enough that my mind wanders and I start doing other work. When I come back, sometimes I'm a little confused about what exactly I'm seeing. Is my Try Server build before this stuff or after? Did I click once or twice?
Or suppose I'm looking for a transition, say, from orange to green. What I really want to do is (a) find the transition; (b) click the before and after previews just to be sure. The pagination makes part b unnecessarily slow.
So I propose that the down arrow be changed from "Go back 12 hours" to "Add 12 more hours of data".
| Reporter | ||
Updated•16 years ago
|
Severity: normal → enhancement
OS: Mac OS X → All
Hardware: x86 → All
Comment 1•16 years ago
|
||
Markus, is there a reason for the way things are right now? I always thought this has had something to do with the large data chunk that we need to load...
Comment 2•16 years ago
|
||
No reason, it's just the way Arpad initially implemented it. I'd love this bug to get fixed.
Comment 3•16 years ago
|
||
The suckiness of our build automation data is endless.
Here's the patch to make this possible. I couldn't get it to work completely, because loading the non-cached json data just times out, but I'm fairly confident in the correctness of this patch. The same problem happens when trying to go back on the tests.themasta.com instance.
Comment 4•16 years ago
|
||
Comment on attachment 450522 [details] [diff] [review]
Patch (v1)
Yeah, this should do it.
It would probably also be good if TBPL could combine data from smaller ranges, which might load a little faster individually, so when going back in time you wouldn't have to load data that you already have.
Attachment #450522 -
Flags: feedback?(mstange) → feedback+
Comment 5•16 years ago
|
||
Not that I think my crappy connections should entirely drive tbpl design, but, I tried downloading m-c's &hours=48&json=1 over my second-best connection earlier today, and that 15MB took something like 17 minutes, so this would probably mean that I could never use back at all. I'd expect that after the first couple of weeks after a repo reset, probably nobody at all would be able to go back in MozillaTry, either.
Comment 6•16 years ago
|
||
This clearly depends on the work in bug 553549, even though that bug might make this issue obsolete.
Depends on: tbpl-server
| Assignee | ||
Updated•15 years ago
|
Assignee: ehsan → arpad.borsos
| Assignee | ||
Comment 7•15 years ago
|
||
Attachment #450522 -
Attachment is obsolete: true
Attachment #477564 -
Flags: review?(mstange)
| Assignee | ||
Comment 8•15 years ago
|
||
Attachment #477564 -
Attachment is obsolete: true
Attachment #477565 -
Flags: review?(mstange)
Attachment #477564 -
Flags: review?(mstange)
| Assignee | ||
Updated•15 years ago
|
Attachment #477564 -
Attachment is obsolete: false
Attachment #477564 -
Flags: review?(mstange)
| Assignee | ||
Updated•15 years ago
|
Attachment #477565 -
Attachment is patch: true
Attachment #477565 -
Attachment mime type: application/octet-stream → text/plain
| Assignee | ||
Comment 9•15 years ago
|
||
Attachment #477566 -
Flags: review?(mstange)
| Assignee | ||
Comment 10•15 years ago
|
||
As far as my testing goes, every part is in itself stable.
I need maybe 2-3 more patches to get this done, finally.
Attachment #477567 -
Flags: review?(mstange)
| Assignee | ||
Comment 11•15 years ago
|
||
--- a/js/TinderboxJSONUser.js
+++ b/js/TinderboxJSONUser.js- try {
- if (!tinderbox_data) throw "tinderbox_data is invalid";
+ if (!tinderbox_data)
+ failCallback("tinderbox_data is invalid");
+ else
loadCallback(self.parseTinderbox(tree, tinderbox_data));
- } catch (e) {
- window.tinderboxException = e;
- failCallback(e);
- }
Its just annoying that exceptions from Data._combineResults are caught and not displayed in the error console with file and line number.
Attachment #477892 -
Flags: review?(mstange)
| Assignee | ||
Comment 12•15 years ago
|
||
Attachment #477893 -
Flags: review?(mstange)
| Assignee | ||
Comment 13•15 years ago
|
||
Thats it for now, finally :)
This makes it straightforward to use pending/running.json later.
Also loads less tinderbox data so adding history should fail less often and be faster :)
Attachment #477895 -
Flags: review?(mstange)
| Assignee | ||
Comment 14•15 years ago
|
||
Only successful runs contribute to the averagetime, as it was before.
Attachment #477893 -
Attachment is obsolete: true
Attachment #477897 -
Flags: review?(mstange)
Attachment #477893 -
Flags: review?(mstange)
| Assignee | ||
Comment 15•15 years ago
|
||
running builds that are finished are correctly cleared on refreshes.
Attachment #477895 -
Attachment is obsolete: true
Attachment #477898 -
Flags: review?(mstange)
Attachment #477895 -
Flags: review?(mstange)
| Assignee | ||
Comment 16•15 years ago
|
||
Now we add new comments to already finished runs on update.
Sorry for the bugspam :P
Attachment #477898 -
Attachment is obsolete: true
Attachment #477928 -
Flags: review?(mstange)
Attachment #477898 -
Flags: review?(mstange)
Updated•15 years ago
|
Attachment #477564 -
Flags: review?(mstange) → review+
Comment 17•15 years ago
|
||
Comment on attachment 477565 [details] [diff] [review]
2: don’t regenerate the whole dom when changing timezone
>diff --git a/js/UserInterface.js b/js/UserInterface.js
>+ var from = timeOffset ? new Date((timeOffset - 12 * 3600) * 1000) :
>+ var and = timeOffset ? new Date(timeOffset * 1000) : new Date();
Please call the startDate and endDate.
Attachment #477565 -
Flags: review?(mstange) → review+
Updated•15 years ago
|
Attachment #477566 -
Flags: review?(mstange) → review+
| Assignee | ||
Comment 18•15 years ago
|
||
(In reply to comment #17)
> Comment on attachment 477565 [details] [diff] [review]
> 2: don’t regenerate the whole dom when changing timezone
>
> >diff --git a/js/UserInterface.js b/js/UserInterface.js
>
> >+ var from = timeOffset ? new Date((timeOffset - 12 * 3600) * 1000) :
>
> >+ var and = timeOffset ? new Date(timeOffset * 1000) : new Date();
>
> Please call the startDate and endDate.
These are being dropped completely in patch 7. So if you don’t mind I would like to not need any unnecessary rebases here.
Each patch is self contained to ease the review burden, bud I’d like to land them all together.
Comment 19•15 years ago
|
||
Oh I see. I haven't gotten that far yet (need to apply them so my tired eyes can benefit from syntax highlighting... :) )
Updated•15 years ago
|
Attachment #477567 -
Flags: review?(mstange) → review+
Updated•15 years ago
|
Attachment #477892 -
Flags: review?(mstange) → review+
Updated•15 years ago
|
Attachment #477897 -
Flags: review?(mstange) → review+
Updated•15 years ago
|
Attachment #477928 -
Flags: review?(mstange) → review+
Comment 20•15 years ago
|
||
Some final comments:
- CSS styles for the Up arrow can be removed
- if (~["building", "pending"].indexOf(result.state)) is too demanding on
the reader
- this._orphanResults = {}; needs a comment like // results that can't be
associated to any push
Comment 21•15 years ago
|
||
Oh, another thing: I think the message "There are no pushes to be displayed" shouldn't be visible at the beginning. It should only be added after the first pushlog load, if there are no pushes.
| Assignee | ||
Comment 22•15 years ago
|
||
Attachment #478279 -
Flags: review?(mstange)
Comment 23•15 years ago
|
||
Comment on attachment 478279 [details] [diff] [review]
8: adress review comments
r=me except for the typos ;)
Attachment #478279 -
Flags: review?(mstange) → review+
| Assignee | ||
Comment 24•15 years ago
|
||
http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/pushloghtml?changeset=90b45cf65dda
Whee :)
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: Webtools → Tree Management
Updated•11 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•