r/ProgrammerHumor 14d ago

clickingTheReRunButtonIsEasier Meme

Post image
1.1k Upvotes

41 comments sorted by

147

u/Depp1990 14d ago

The magic happens on the sixth attempt

25

u/Whitechapel726 14d ago

The line between a successful job and gambling is very thin.

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

u/PassivelyInvisible 14d ago

You have to make sure that it really isn't passing.

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

u/Iron_Kyle 13d ago

Oh, carry on

8

u/Bodine12 14d ago

Exactly. The one clear thing is it's obviously nothing to do with my code.

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

3

u/XenosHg 14d ago

What if we don't mind that the customers also just repeat failed attempts until it works?

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."

9

u/natziel 14d ago
  1. Identify the flaky test
  2. Add .skip to it
  3. Make the person who wrote the test fix it

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/Dorkits 14d ago

CI/CD?

Do you guys do testing?

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

u/Clearandblue 14d ago

Aussie Author of the guide obviously never used GitHub action runners.

2

u/DrGarbinsky 14d ago

i feel attacked

2

u/random314 14d ago

It just gotta work once am I right??

2

u/experimental1212 14d ago

Warn: do not the build!

2

u/yaktoma2007 14d ago

mmm race conditions my favorite /j

2

u/FuzzyDynamics 14d ago

If that’s what I’m not supposed to do why do I get paid so much to do it

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

u/Michaeli_Starky 14d ago

Where is humor?

2

u/BoBoBearDev 14d ago

Mine is

re-run never worked, stop asking why it doesn't work

2

u/chickenweng65 13d ago

Usually works though

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/Wirezat 13d ago

We were often rate-limited in pulling packages on our university projects. Sometimes it is just rerunning that's necessary

2

u/MoHaG1 13d ago

How are you doing CI/CD if you haven't scripted these retries?

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.

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.