3000+ entries in 0.414s
mod6: I don't see any ref's in the makefile to src/obj/
test mod6: i guess src/obj-
test needs to stay because of the
test stubs & it's ref'd in the makefile. that's fine.
mod6: after an actual
test.
mod6: does anyone see a reason to keep src/obj-
test and src/obj/
test ?
ben_vulpes: pete_dushenski: you'd know better than i about the
test drive. that's just how i got my butt in one.
ben_vulpes: ;;later tell solrodar hey man i need a hand compiling boost in order to
test your callgraph visualizer
☟︎ mod6: <+ascii_modem>
http://log.bitcoin-assets.com/?date=18-07-2015#1205870 << wai wut - ?? - no one signed that he has read, tested - and straight to release? << I certainly did not mean to imply immediate release. Just that I'll build a
test plan surrounding what i've indicated. Process is already underway.
☝︎ mod6: i'm gonna need another box to
test on anyway.
mod6: one other thing I gotta do is update the gentoo-uclibc guide to a new guide for nomultilib glibc, should be fairly easy. then
test it on my pos box.
mod6: cool! thanks. yeah, we're gonna need as much help as we can get testing. and as soon as we have a solid
test plan developed, then we'll cut a release candidate for testing.
mod6: im workin on that
test matrix now.
mod6: i'm gonna throw in debug_sanity-part1-corrected to my next build/sync
test, and look at the output/impact of the patch. i should have some more meaningful comments after that.
ben_vulpes: ;;later tell pete_dushenski find someone who's a shareholder, they can do
test drives
mod6: especially if anyone is helping
test or whatever and they need debug_sanity they can just apply the patch to their local codebase.
mod6: punkman has his debug_sanity, but I hvane't had a chance to
test version two, and it's not a super high priority for me at this very moment.
mod6: One of my goals for this week (and I'm running a bit behind) was to create a
test matrix for everything that needs to be tested for this forthcoming release. I hope to at least get a start on that here today yet.
mod6: i'll give one a try as soon as it's built and ready to
test.
ascii_field: point is not only to
test pogo build and get musl in, but also it is useful to have a rom-able pc realbitcoinotron
gernika: mircea_popescu Aha no the Chinese thing was a
test of my appearance via a photo, which I passed.
assbot: Logged on 16-07-2015 00:23:05; gernika: Actually used to work at Micron, as an intern for a summer. Would have worked for them for a second summer but ... drug
test. They did email on a Vax of some sorts, but were otherwise a windows shop.
assbot: Logged on 15-07-2015 18:35:24; ascii_field: the current turd is not 'pogoable' and i'm surprised that danielpbarron bothered to
test it there
trinque: make rules -> try to break them -> if you can't,
test passes
gernika: AMD only did one drug
test, so just extended my internship there instead.
gernika: Actually used to work at Micron, as an intern for a summer. Would have worked for them for a second summer but ... drug
test. They did email on a Vax of some sorts, but were otherwise a windows shop.
☟︎ ascii_field: the current turd is not 'pogoable' and i'm surprised that danielpbarron bothered to
test it there
☟︎ trinque: they ought to have a
test for this in early childhood
mod6: So over the weekend and today, was working on building a new gentoo-amd64-nomultilib (glibc) instance to
test out application of patches with v0.5.3.1-RELEASE as the base. Was able to build static binaries with gentoo & glibc just fine with both a modified auto-static (auto.sh) and with a slightly modified stator.sh script.
trinque: lol how do they means-
test that?
trinque: the first
test is whether you notice
mod6: anyway, it might not be a bad time for me to stop it now anyway, and break off to try some other things. I wanna
test build stator on gentoo.
trinque: only asciilifeform's
test takers
funkenstein_: meanwhile litecoin users enjoying "stress
test" popcorn
trinque: stress
test seems to prove the system works from where I sit
ben_vulpes: now on one hand that this thing doesn't give programmers any handles to alter
test data is fine, in that it forces one to either work in a js repl or you know /actually write tests/
assbot: Logged on 07-07-2015 21:02:02; trinque: I have no idea what they think the 'stress
test' is meant to demonstrate
danielpbarron: i have not noticed the "network
test" except that my actual full nodes sometimes differ by (sometimes rarely) as much as a few dozen blocks before eventually settling in on the true height. My transaction sending has been uneffected.
BingoBoingo: stress
test demonstrates 1MB is plenty big to allow for periodic spam attacks, and bigger blocks would make bloat attacks still cheaper
trinque: I have no idea what they think the 'stress
test' is meant to demonstrate
☟︎ ascii_field: not a bad
test of how 'bulletproof' mircea_popescu's new fleet of boxes is ?
assbot: Logged on 07-07-2015 04:01:47; decimation: find predictions for the time they are to occur and compare with your clock under
test decimation: find predictions for the time they are to occur and compare with your clock under
test ☟︎ ascii_field: in other nyooz, my portable
test node is synced.
mod6: mp, you're right, should
test the new dump/eat tools with the orphan blocks
mircea_popescu: just some nodes have trouble unsticking, which as i said above, great place to
test our new block manip tools etc.
mircea_popescu: ascii_modem this is incidentally an exceptional opportunity to
test our recent toolset.
assbot: Successfully added a rating of 1 for shinohai with note: Helping to
test the bitcoin Reference Implementation
mod6: !rate shinohai 1 Helping to
test the bitcoin Reference Implementation
mod6: but pre-milestone release, it does get hard to follow. and since I do believe it'll still be some time before we get the next milestone cut, I should prepare some sort of document so individuals can help
test. (we very much appreciate the enthusiasm and the help!)
mod6: But as I get through more of these and
test more of these, I'll put something together to make this process easier.
mats: dignork: i'm looking forward to a
test drive
shinohai: I can't get electrum right for shit. I did a
test tx using pywallet to import a privkey
funkenstein_: ;;later tell copypaste please
test coin-vote.com again, improved
decimation: I don't see any graphs on that doxygen/
test page
mod6: i think maybe they should go the other direction tho? so anyway, I'm gonna put up a temp/
test dir so you guys can take a look
mircea_popescu: much like tests in school select for and breed
test takers.
mircea_popescu: atm the entry level thing for coders is, "follow the pogo thing, build along,
test cases etc". for non-coders is, qntra.
punkman: I'd definitely want better debug/
test instrumentation before such experiments
mod6: im currenty building a new AMI for gentoo so I/we can
test wtf is going on in there with gcc/uclibc. I should be done with that in a few hours.
mircea_popescu: well, again, gpg has a probabilistic
test for primality baked in.
mircea_popescu: you could run a probabilistic
test on your own machine for your own modulus. if you have a good rng this usually woirks,
assbot: Logged on 10-06-2015 17:00:45; ascii_field: it is the ultimate 'iq
test'
pete_dushenski: ^heh i was thinking about this eulora question, time to
test my answers against the back page !
mod6: So this is interesting: I was able to use my gcc patch successfully against my AWS instance which has an AMI that utilizes a stage3-uclibc-hardened from 20150510. And meanwhile, trinque was helping me
test to ensure I'm not doing something totally retarded, and on his side he was using the Physical hardware steps where it says to pull the latest (which should be 20150610) stage3-uclibc-hardened.
mod6: The patch we got from that mailing list was from a different version for sure than 4.8.4 -- so i've had to hack it in by hand. gentoo is now applying the patch properly. and it's compiling as we speak. there is one caviat that I need to get over before I can
test it though.
assbot: Logged on 22-06-2015 03:35:14; asciilifeform: (it is possible to break up cement, but not without anyone noticing. this is the basic principle for the nuke
test-ban compliance gadget used on both sides of the ocean)