/srv/irclogs.ubuntu.com/2019/07/30/#launchpad.txt

=== morphis9 is now known as morphis
b-radhi i have a strange build issue, where 32bit failed but 64bit completed. The 32bit failure was due to "stray ‘\1’ in program", but I don't see any such character in a hex editor16:51
cjwatsonHave you tried reproducing the bug locally in e.g. sbuild?16:53
cjwatsonIt's very unlikely to be a Launchpad-specific problem.16:53
b-radi'll look into setting up sbuild, i just do standard sanity builds for 64bit16:53
b-radjust weird that for the same code 32bit pukes, but not 64bit16:53
b-radand unfortunately where build log says there's a \1 there isn't16:54
cjwatsonCan't say any more without a link to the failure16:55
b-radhttps://launchpadlibrarian.net/435131782/buildlog_ubuntu-bionic-i386.linux_4.15.0-55201907291620.0+mediatree+hauppauge_BUILDING.txt.gz16:55
cjwatsonI suppose stray memory corruption is always a possibility (retrying would confirm whether it's just that), but would be surprising16:56
cjwatsonIf it persists beyond that then you probably need to consult a kernel developer for help16:56
b-radi guess i'll push rebuild and see, was hesitant to do that without inquiring if this had been seen before16:57
b-radas well as get a sbuild docker setup16:57
cjwatsonIt's not a familiar problem, no17:00
b-radcjwatson, must have been a stray cosmic ray collision, the rebuild succeeded17:57
b-radlcy01-amd64-024 was the machine17:57
cjwatsonb-rad: OK, I guess with enough builds going through small probabilities add up21:36
b-radi shall be that statistical anomaly21:38
cjwatson(The machines are ephemeral VMs, so there's unlikely to be much trace left)21:39
b-radi saved the build log in case it was desired, but i doubt it would be of any in sight besides the host machine21:39
cjwatsonNo, I don't think so, indeed21:43

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!