Testing hell.

I'm working on a ticket that touches a lot of areas of the codebase, and impacts everything that creates a ... really common kind of object.

This means changes throughout the codebase and lots of failing specs. Ofc sometimes the code needs changing, and sometimes the specs do. it's tedious.

What makes this incredibly challenging is that different specs fail depend on how i run them. If I use Jenkins, i'm currently at 160 failing tests. If I run the same specs from the terminal, Iget 132. If I run them from RubyMine... well, I can't run them all at once because RubyMine sucks, but I'm guessing it's around 90 failures based on spot-checking some of the files.

But seriously, how can I determine what "fixed" even means if the issues arbitrarily pass or fail in different environments? I don't even know how cli and rubymine *can* differ, if I'm being honest.

I asked my boss about this and he said he's never seen the issue in the ten years he's worked there. so now i'm doubly confused.

Update: I used a copy of his db (the same one Jenkins is using), and now rspec reports 137 failures from the terminal, and a similar ~90 (again, a guess) from rubymine based on more spot-checking. I am so confused. The db dump has the same structure, and rspec clears the actual data between tests, so wtf is even going on? Maybe the encoding differs? but the failing specs are mostly testing logic?

none of this makes any sense.
i'm so confused.

It feels like i'm being asked to build a machine when the laws of physics change with locality. I can make it work here just fine, but it misbehaves a little at my neighbor's house, and outright explodes at the testing ground.

Damn it! today I learnt that GitHub has a tool called Hub - "an extension to command-line git that helps you do everyday GitHub tasks without ever leaving the terminal".

It's been around for 10 years.

And here I was clicking on the link that was sent by the remote after every push to open a pull request 🤦‍♂️
It even comes with vim syntax support for pull requests.

I'm never leaving the terminal to do things on the GitHub web interface anymore

I've been doing it wrong for 6 months! I've been building -> uploading my work manually to server using ssh.
Now I decided I write a script for that shit .-.

Though I'm still not able to make output take a different color in Ubuntu default terminal, tried many solutions but I still fail :\
Any suggestions?

Well well well.
Story time.

Since we are working from home for the past 4 months, I finally decided to install a Microsoft SQL server on my home server. (Mostly was using Azure)

My server is running Windows Server 2012 R2.
Tried installing SQL 2019 : fail, 2016 : Fail, 2012 : Fail. Some obscure message about some DLLs not being at right version. (And a warning that it is no recommended to install SQL server on domain controller, but I know, it is my home setup, not roduction)

“Ok fine, I’ll install it on my PC instead”. Windows 10 PC. NOPE. “Cannot install on a compressed drive”. Welp, wtf ? (Of course you cannot select destination install folder, I could’ve put it on another drive).

So here I am. Working 100% on Windows, installed Ubuntu server 20 LTS in Hyper-V, Installed Microsoft SQL server on it (BTW, install is very easy compared to windows). And that shit is working. And new “Terminal” app does support SSH out of box, no need to add Putty !

So as a Windows user, I needed Linux to make Microsoft SQL techno work.

Nothing will ever surprise me anymore. (BTW it’s fucking fast. I like SQL server on Linux)

I just rebooted my server by accident because I wanted to play Space Engineers.

Long story short, dual booting. Needed to boot into windows. Typed reboot into my terminal. My terminal was not local. When am I finally getting around to set up my terminal color as red when it is connected to another host?

But two things are good here. This was my own server.. Well, bunch of stuff is running on it, including for my bachelor's thesis. But if that was a server of my company, that would have been worse.

Second thing, my systems are fault tolerant. I reboot once per week at the latest and for systems with fail overs once per day. I know they are coming back up. I don't worry. My Gitlab will be back in 5 minutes at the latest. I am going to reboot and play Space Engineers now.

Reboot your servers guys. Only way to make sure they'll survive reboots!

Guess what I saw while channel surfing on tv. A Linux terminal Channel. There was no one doing anything to it, it was just there.

Linux, you never fail to amaze me!

Started using Arch based Manjaro with xfce de couple of months ago. Everything was mostly fine even though I've never used anything that was based on Arch but it had a learning curve.
Couple of weeks ago I couldn't update my packages, I thought it would fix it by itself but I was wrong as you already probably know.
So yesterday I tried to manually fix it. Famous last words. After a lot of googling, trying some terminal commands - and failing, I see a warning labek on some text on the arch wiki - sudo pacman -Syi --force. I said fuck it and did it. Let's see if it works, I try to install a package, I mistype the name, press backspace - it puts a space instead of deleting?!?!?
I tried restarting, googling - nothing...
Guess I'll switch back to Debian based OSes.

Fail on pay terminal at Place Massena, Nice yesterday. Plus, still using W XP!