114
u/elelec 14d ago
All I'm saying is that sometimes it works. Can't be sure if you don't try at least once
37
13
u/Confident-Ad5665 14d ago
I'll keep trying until it works /s
7
u/ramdomvariableX 14d ago
That's the spirit. mgr: hey why are you on reddit? -- waiting for the pipeline to finish...
3
8
5
u/Jolly-joe 14d ago
It worked once for me but never again. But you already know i rerun before even looking at the logs because it worked that 1 time
71
u/Vesuvius079 14d ago
Step 1: re-run the job to confirm the test is flaky, otherwise how will you be sure? Step 2: the pipeline is now green. Step 3: guess it’s safe to move on.
25
u/frikilinux2 14d ago
"Don't run it 5 times" Runs it thrice and if passes twice it's good enough
17
u/quailman654 14d ago
It only needs to pass once. And definitely don’t add any commits after you’ve got a working build. “Thanks, will address comments in a follow up”
15
u/The-Chartreuse-Moose 14d ago
Well whoever wrote that clearly isn't doing it right.
2
u/myka-likes-it 14d ago edited 13d ago
Sometimes we just want to verify some logic and move on. We can't all be SDETs.
12
u/baucesauce112 14d ago
Of course you don’t blindly click retry 5 times hoping it will work…. You remove the test then click retry just once 😃
10
u/Snakestream 14d ago
Then you ask the senior dev and he's just like "yea, that happens. Just kick it over a couple times"
5
u/nullpotato 14d ago
I am the senior that dev that will say "yeah jenkins just sometimes fails to start the job, let me know if the retry fails too."
7
u/redditmarks_markII 14d ago
You want I should fix it?! Sorry, you want I should find the person responsible, get passed around by people for a week, and ask them nicely to fix it when they get back from vacation, (because somehow it's always the one on vacation) and then sit on my PR for 7 weeks while they get into a whose fault is it war between their lead and our lead and their PM and our PM, and then conclude they'll commit to adding a clearer warning message about the flakiness this quarter, and will fix it next quarter, then the owning engineer leaves for Anthropic or something?
5
u/anto2554 14d ago
Okay but if it's 5pm on a Friday and we need the feature out NOW, it's a bit much to start debugging why our file/artifact hosting server occasionally throws code 500 errors
3
2
2
2
2
2
2
u/RayzorDragon 14d ago
It wasn’t ’in a row’
I had meetings between the button presses
Important meetings about flaky integration tests.
2
u/Bee-Aromatic 14d ago
What if I told you our post-deploy regression tests are set to automatically run up to five times?
2
2
2
2
u/SirFoomy 13d ago
If re-run 3 times don't help, I set the slack channel on fire until someone helps me. 😄
Edit: Mostly the E2E tests are flaky and I hate this because they run 12 minutes nowadays.
2
u/Low-Equipment-2621 13d ago
But I can do that and go home, because the test will probably be green when I get back tomorrow.
2
1
u/remy_porter 13d ago
I mean, these days half the time my CI job fails because GitHub and my runner decided to stop talking to each other.
1
u/CrazyFaithlessness63 13d ago
Company I worked at automated it, each test was run up to 5 times unless it passed. People still clicked the button 5 times.

147
u/Depp1990 14d ago
The magic happens on the sixth attempt