Valid. You need to know if it’s a sometimes bug or an always bug.
The truly terrifying outcome is that it works after changing nothing. Sometimes bugs are the most fun to squash.
We seemingly have a different opinion, what we regard as ‘fun’ ;-)
Stuff that can’t be reproduced and “only” comes up because of some timing issue/race condition is often the most shit to hunt for
I’m currently in such an adventure - and I thought I had it…but the statistics show, that it only got better, but didn’t catch all of the occurrences…
Stuff that can’t be reproduced and “only” comes up because of some timing issue/race condition is often the most shit to hunt for
Ah, but if you can’t reproduce it, you can just put in an entry of ‘could not reproduce’ and close the bug report. Case closed. Go home and enjoy a nice beverage.
Due to the non zero ammount of times this happened to me… this is like pressing ctrl+c multiple times to make sure you copied the thing. And then pressing shift+ctrl+c cause you aren’t sure if that works in this terminal emulator.
Happy debugging if it works on the second try… 😬
Best things are, when you throw in some debug output and that changes the timings just as much to not make the bug happen anymore
I’ve lost more hair to that, than my age…
Well, better than the other way around:
Code works perfectly on your test device but breaks down when deployed to field devices with slightly different timing characteristics or whatever.Bonus points if it only occurs every few weeks, preferably at night shift and crashes a whole production line… 🫣
(Incident totally fictitious, definitely no people out of this thread involved, just move on, really nothing to see here!)
True that…
Happens too fucking often as wellI’m currently hunting a bug that happens like every 1000 iteration of the thing happening.
Like, I’m telling the hardware to do something and it works pretty much all the time, but over the day, the errors add up
I have no clue why it happens, but can’t really turn up the debug logs that much, because with so many things happening, I’d produce like a shitload of data.
But I can’t really narrow it down otherwiseAnd it seems we’re in the same kind of shit business ;-)
Real time processes and automation, with customers having problems at night shift, because the maintenance guys during that shift are usually not as good - or it’s just bad luckAt one of my last business trips I was already at the airport on my happily way home, when I’ve got call.
Needed to get my luggage back, new rental car and get a place at the hotel.
Just to discover, that after 15 years the hardware acted up in a way it never did before.
At least I could now include a warning message, if this weird situation ever happens again, but that was a tough one to swallow…
Or the code you are working on is calling a system that is currently unreliable which you cannot be responsible for.
Fuck test automation, it’s a fucking trap get out of it as soon as you can
EDIT : that is to say, test automation as in automation that a tester does, instead of unit tests. If you have started a career as a software tester , get out ASAP.
Very true, especially when working with recursion. (Debugging recursion sucks)
The first time, I just saw it’s not working; the second time, I was paying attention to the details to see what specific parts aren’t working and clues as to how/why.
Sometimes, this actually works simply because of your compiler lagged the previous time.
tilts tin foil hat to the left…
Works now 👍
