Closed Bug 1320998 Opened 8 years ago Closed 7 years ago

TC Linux 64 nightly verification

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: Callek)

References

Details

This bug is about making sure the new TC Linux 64 nightly is comparable to one generated by buildbot.

Some things to look for:
* size of tarball
* package naming
* updates work as expected
Depends on: 1321040
:glandium...

I'm having trouble with diffoscope as you suggested, with the linux64 comparison I'm getting .jsm files treated as binary, so incomprehensible diffs.

The binary .so's I can't tell are ok or not.

My command is:

diffoscope --new-file --text ./diff_linux64.txt --progress ./old.lin64.tar.bz2 ./new.lin64.tar.bz2 


Where the new.lin64.tar.bz2 is from the signing task on the date branch for linux64's nightly. And the old is the m-c nightly taken from archive.m.o

Can I get some insight here perhaps?
Flags: needinfo?(mh+mozilla)
Depends on: 1321380
All I can tell this was all fine.
Flags: needinfo?(mh+mozilla)
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.