[ERROR] HTTP 000 in OTHERS.lst, url: ''

What happens

This week I’ve had the same type of error multiple times in the /test/others/urls_status_code job:

[INFO] HTTP 200 in OTHERS.lst, url: 'https://blog.csdn.net/m0_43424471/article/details/109052482'[ERROR] HTTP 000 in OTHERS.lst, url: ''

It’s weird because yesterday I did the commit and job was successful

Today I made some changes to the Gherkins file (I didn’t touch the OTHERS.lst files). And when I push commit now that error appears

And under normal conditions I just delete the url that fails, but when I did that today, then [another of the urls that was successful before now fails](https://gitlab.com/autonomicjump/challenges/-/pipelines/756346760 /failures)

What do you understand or find about that problem

In the forum I found some threads about OTHERS.lst file but I didn’t find any with this problem, because the log first says that there is a status code [INFO] HTTP 200... but in the same line at the end it says ’ [ERROR] HTTP 000 in OTHERS.lst

And the strangest thing is that I only modified the Gherkins file, the OTHERS.lst files were the same as when the commit passed all the tests.

You make any workaround? What did you do?

Normally I just replace the url or remove it, but today every commit I’ve tried to push fails at a different link in the OTHER.lst file

I have also done the validations with:

  1. Convert the OTHERS.lst files with the dos2unix command
  2. Validate the ‘200’ status code with curl -s -o /dev/null -w "%{http_code}" <URL>
  3. Validate the ‘200’ status code with https://httpstatus.io/
  4. Reset the job ``/test/others/urls_status_code` multiple times
  5. Delete the failing URL and replace it with another one (today I did it 6 times and in each new pipeline another URL from the OTHERS.lst file fails)


Image from yesterday that was successful https://blog.csdn.net/m0_43424471/article/details/109052482:

today’s image failing https://blog.csdn.net/m0_43424471/article/details/109052482

link to the pipelines starting with the old pipeline up to the new one:

I need help with

I don’t know why the pipeline fails and I try to make workarounds but didn’t work, what I should do to fix this.


Always remember to check that your OTHERS.lst has no empty fields. As marked in the image.


1 Like

Thanks @deep-detective!!!
I really appreciate your observation, when I saw those empty spaces, I could only laugh. Now the error message with the empty URL '' makes sense.

To avoid that from now on, I now added the following sed command in my commit script to remove all empty lines:

sed -i '/^\s*$/d' <PATH-TO-OTHERS.lst>

I made the change and now the pipeline was successful.