Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins build failure for names.rq #25

Open
DeniseSl22 opened this issue Aug 10, 2020 · 7 comments
Open

Jenkins build failure for names.rq #25

DeniseSl22 opened this issue Aug 10, 2020 · 7 comments
Assignees

Comments

@DeniseSl22
Copy link

DeniseSl22 commented Aug 10, 2020

image

I think the build "fails" due to this item in the build options:
image

(I've had a similar issue with the disease mapping db). I've removed the last build option for now, to check if the build will succeed (the .bridge file is being created).

@DeniseSl22
Copy link
Author

Mhh, now I'm getting the following failure:

curl: (18) transfer closed with outstanding read data remaining
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE

@DeniseSl22
Copy link
Author

Seems to be related to names.rq (either timing out due to wikidata endpoint timeout, or Jenkins not receiving data anymore....).

Suggestion: limit query....

@DeniseSl22 DeniseSl22 changed the title Jenkins build failure Jenkins build failure for names.rq Aug 10, 2020
@egonw
Copy link
Member

egonw commented Aug 22, 2020

It happens now and then. Next tun often works again.

@egonw egonw removed their assignment Aug 22, 2020
@egonw
Copy link
Member

egonw commented Oct 2, 2020

Can we conclude this just happens now and then and depends on the WDQS?

@DeniseSl22
Copy link
Author

I think so.... I ran the names.rq manually on the WD endpoint 2 hours ago, and also got a timeout
But tried half an hour later, and then it worked..... so when the traffic on the WD endpoint is high, most likely we will get a timeout, and manually need to restart the job at a later stage. Or we should split up the names.rq query in two sections, and combine the results later in groovy..... @egonw ?

@egonw
Copy link
Member

egonw commented Oct 2, 2020

We should start using the regular API for things like this, i think

@egonw
Copy link
Member

egonw commented Dec 11, 2021

I discussed this today in the Telegram Wikidata group. The problem is the download timing out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants